diff options
| author | jhb <jhb@FreeBSD.org> | 2015-04-06 17:39:36 +0000 |
|---|---|---|
| committer | jhb <jhb@FreeBSD.org> | 2015-04-06 17:39:36 +0000 |
| commit | 5157da51af8f43fc7cb1272192f47049ac259fce (patch) | |
| tree | 6af92c4ad907dec54feebbe622e177c89dd80fec /sys/dev/acpica/acpi.c | |
| parent | 99c6fb03e5a5b99d0108cce2793a94df379713df (diff) | |
| download | FreeBSD-src-5157da51af8f43fc7cb1272192f47049ac259fce.zip FreeBSD-src-5157da51af8f43fc7cb1272192f47049ac259fce.tar.gz | |
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.
MFC after: 1 week
Diffstat (limited to 'sys/dev/acpica/acpi.c')
| -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 b331fb8..a597b6d 100644 --- a/sys/dev/acpica/acpi.c +++ b/sys/dev/acpica/acpi.c @@ -1151,7 +1151,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); } |
