https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227404
--- Comment #3 from Andriy Gapon <a...@freebsd.org> --- (In reply to Dexuan Cui from comment #0) I have observed a similar (perhaps the same issue) on real multi-core hardware but with the SMP kernel (GENERIC) when all APs were disabled via hints (hint.lapic.%d.disabled=1). The reboot got stuck and a thread doing it was in this state: db> bt Tracing pid 1 tid 100002 td 0xfffff80003230560 sched_switch() at sched_switch+0x95c/frame 0xfffffe00213b9880 mi_switch() at mi_switch+0x188/frame 0xfffffe00213b98b0 sleepq_switch() at sleepq_switch+0x10d/frame 0xfffffe00213b98f0 sleepq_timedwait() at sleepq_timedwait+0x50/frame 0xfffffe00213b9930 _sleep() at _sleep+0x2fa/frame 0xfffffe00213b99d0 kproc_suspend() at kproc_suspend+0x9a/frame 0xfffffe00213b9a00 kproc_shutdown() at kproc_shutdown+0x4e/frame 0xfffffe00213b9a20 kern_reboot() at kern_reboot+0x19e/frame 0xfffffe00213b9a60 sys_reboot() at sys_reboot+0x3ab/frame 0xfffffe00213b9ac0 amd64_syscall() at amd64_syscall+0x79b/frame 0xfffffe00213b9bf0 fast_syscall_common() at fast_syscall_common+0x105/frame 0xfffffe00213b9bf0 I didn't examine other threads much. -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
