After applying the latest errata patches for 6.1 yesterday (logged
on via ssh), I rebooted our apu2 acting as a gateway. The machine
stopped responding (the ssh session hung) and this morning I logged
on via serial console to learn it was stuck at the ddb{3} prompt.

I ran a 'trace' and copied the output, as well as a 'mach ddbcpu 0'.

--8<--

ddb{3}> trace
Debugger() at Debugger+0x9
panic() at panic+0xfe
__assert() at __assert+0x25
pf_state_key_unref() at pf_state_key_unref+0xc6
pf_pkt_unlink_state_key() at pf_pkt_unlink_state_key+0x15
m_free() at m_free+0xc0
sbdrop() at sbdrop+0x80
sbflush() at sbflush+0x1f
sbrelease() at sbrelease+0x11
sorflush() at sorflush+0x158
sofree() at sofree+0xa7
soclose() at soclose+0x8d
soo_close() at soo_close+0x1c
fdrop() at fdrop+0x2c
closef() at closef+0xcb
fdfree() at fdfree+0x60
exit1() at exit1+0x2e3
sys_exit() at sys_exit+0x17
syscall() at syscall+0x27b
--- syscall (number 1) ---
end trace frame: 0x0, count: -19
0x1ef09408d58a:
ddb{3}> mach ddbcpu 0
Stopped at      Debugger+0x9:   leave
Debugger() at Debugger+0x9
x86_ipi_handler() at x86_ipi_handler+0x76
Xresume_lapic_ipi() at Xresume_lapic_ipi+0x1c
--- interrupt ---
__mp_lock() at __mp_lock+0x42
softintr_dispatch() at softintr_dispatch+0x43
Xsoftclock() at Xsoftclock+0x1f
--- interrupt ---
acpi_s3_vector_real() at 0x8
end() at 0xffffffffffffffff

-->8--

The 'mach ddbcpu 0' never finished and the machine stopped responding
altogether. Had to kill the power and reboot it.

The output from above and things like dmesg and such can be found at
https://ifconfig.se/panic/

I'm not sure if this is of any use but I thought I'd report it anyway.
Sorry if I'm wasting anyones time.

Reply via email to