If (oops) { Do_not_panic(); }
Talkat Embedded Linux Conference @ Open Source Summit North America 2022 · on Thursday, 2022-06-23· at 11:10· Griffin Hall (Level 2), JW Marriott Austin, 110 E 2nd Street Austin, TX 78701·
summary
Shows how to trigger a kernel oops by inserting a module that performs a null pointer dereference, captures the oops dump (instruction pointer at offsets like 0x08/0x80 and CPU core number), and then locates the offending C line using addr2line, objdump and GDB with the vmlinux image. Demonstrates configuring kexec + kdump and using crash to read the saved vmcore, and explains KDB/KGDB workflows and serial/TCP parameters; the kdump roundtrip successfully produces a post‑mortem dump for analysis.
AI-written summary · about
chapters (15)
- 0:00Start
- 0:27Introduction to Linux Kernel
- 1:05The Kernel
- 1:54Five Major Subsystems of any Linux Kernel
- 2:17Memory Management Unit
- 2:51Networking
- 4:42Kernel Panic
- 5:03Causes of an Oops or a Kernel Panic
- 8:45Print Key Function
- 10:16Obj Dump
- 11:59Kx and K Dump Utilities
- 17:20Kdb and Kgdv
- 20:52Kernel Debugger Boot Arguments
- 26:48Steps To Use Kgdb
- 28:50Switch between Kgdp and Kdb during Runtime
related talks
46mTools and Techniques to Debug an Embedded Linux System
42mUsing Yocto to Debug Embedded Device Crashes- 42mUsing Yocto to Debug Embedded Device Crashes
39mHow to Investigate Issues on Linux Embedded System?
28mMinidump to debug end user device crashes
38mEfficient On-Device Core Dump Processing for IoT: A Rusty Implementation
37mDebugging & Tracing and More Between Linux and RTOS on Heterogeneous ARM SoC
48mCapturing 0Day Exploits With Perfectly Placed Hardware Traps