[Bug 234676] Boot hangs after upgrade to 12.0-RELEASE (acpi?)

bugzilla-noreply at freebsd.org bugzilla-noreply at freebsd.org
Sat Jan 19 22:21:32 UTC 2019


https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234676

--- Comment #8 from johan van Zanten <johanvz816 at giantfoo.org> ---
Per the ACPI debugging docs:
https://docs.freebsd.org/doc/5.5-RELEASE/usr/share/doc/handbook/acpi-debug.html

I tried adding this to loader.conf:

hint.apic.0.disabled="1" 

...and the system panics with 12.0 as well as 11.2 kernels.  (The latter boots
without that line in loader.conf.)

The traceback from the panic in the 12.0 kernel (i think it was the same in
11.2):

cryptosoft0: <software crypto> on motherboard
acpi0: <060410 RSDT1553> on motherboard
acpi0: could not allocate interrupt
ACPI Error: AE_ALREADY_EXISTS, Unable to install System Control Interrupt
handler (20181003/evevent-260)
acpi0: Could not enable ACPI: AE_ALREADY_EXISTS
device_attach: acpi0 attach returned 6
panic: No usable event timer found!
cpuid = 0
time = 1
KDB: stack backtrace:
db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xffffffff82665b30
vpanic() at vpanic+0x1a3/frame 0xffffffff82665b90
panic() at panic+0x43/frame 0xffffffff82665bf0
cpu_initclocks_bsp() at cpu_initclocks_bsp+0x3dd/frame 0xffffffff82665c20
cpu_initclocks() at cpu_initclocks+0x15/frame 0xffffffff82665c40
initclocks() at initclocks+0x20/frame 0xffffffff82665c50
mi_startup() at mi_startup+0x118/frame 0xffffffff82665c70
btext() at btext+0x2c
KDB: enter: panic
[ thread pid 0 tid 100000 ]
Stopped at      kdb_enter+0x3b: movq    $0,kdb_why

-- 
You are receiving this mail because:
You are the assignee for the bug.


More information about the freebsd-bugs mailing list