diff options
| author | jhb <jhb@FreeBSD.org> | 2015-04-23 22:39:32 +0000 |
|---|---|---|
| committer | jhb <jhb@FreeBSD.org> | 2015-04-23 22:39:32 +0000 |
| commit | 82e55ed42b7b4172ff259339ad3ebdd0498067a0 (patch) | |
| tree | a929930ebdd4998292a1f6c3195201ad33ec17c6 | |
| parent | 69cb38204284b5c07588090431719cfee1152ff3 (diff) | |
| download | FreeBSD-src-82e55ed42b7b4172ff259339ad3ebdd0498067a0.zip FreeBSD-src-82e55ed42b7b4172ff259339ad3ebdd0498067a0.tar.gz | |
MFC 281159:
Move the message complaining about failed system resource allocations
under bootverbose. Every example I've seen to date has been due to
an ACPI system resource device reserving a range that overlaps with
system memory (which ram0 attempts to reserve) or a local or I/O APIC
(which apic0 attempts to reserve). These are always harmless but look
scary to users.
| -rw-r--r-- | sys/dev/acpica/acpi.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/sys/dev/acpica/acpi.c b/sys/dev/acpica/acpi.c index 65ade62..00d2252 100644 --- a/sys/dev/acpica/acpi.c +++ b/sys/dev/acpica/acpi.c @@ -1148,7 +1148,7 @@ acpi_sysres_alloc(device_t dev) if (res != NULL) { rman_manage_region(rm, rman_get_start(res), rman_get_end(res)); rle->res = res; - } else + } else if (bootverbose) device_printf(dev, "reservation of %lx, %lx (%d) failed\n", rle->start, rle->count, rle->type); } |
