Kernel Debugging

Not started yet — reading an oops, oops vs. panic, and the debug methodology for "my driver crashes the board — walk through what I'd do." 7 bytes.

Reading an oops — the PC/LR, the call trace, and finding the actual faulting line.
Oops vs. panic — recoverable vs. a full halt.
printk debugging discipline — rate limiting and the pr_* helpers.
/proc and /sys as windows into live kernel state.
ftrace and git bisect, at an awareness level, for a kernel regression.
The debug methodology itself — reproduce, dmesg, narrow, instrument, fix, verify — as a rehearsed answer, not just a tool list.

Not yet catalogued — check back once this topic is underway.

Notes from readers

Comments — via GitHub