You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
kernel/core/core_crash.c + the exception path in
arch_exceptions.c.
The panic sequence
The exception stub builds the frame (vector, RIP, registers,
CR2/CR3 where relevant).
The dumper prints it to serial - the exact lines you need for a
report.
A crashlog record goes to /etc - survives the reboot.
The machine halts (or the hardware watchdog resets it if one was
armed - see Internals-Watchdog-EN).
After reboot
oc> crashlog (the record list)
oc> dumpinfo (the decoded dump: vector, fault address, registers)
Why IST matters here
#DF (double fault) and #MC run on IST1 - their own stack - so a
fault during a fault handler still reaches the dumper. The
exception-exit path never context-switches on IST2 (BUG-0139): a
context switch on an IST would corrupt the exception frame of the
next nested fault.
Testing it
crashtest = deliberate panic, then dumpinfo proves the round
trip. The regression battery checks crashlog on every run.