Linux Kernel Debugging: Going Beyond Printk Messages
Talkat Open Source Summit Europe + Embedded Linux Conference Europe 2019 · on Monday, 2019-10-28· at 15:15· Forum 1·
summary
Demonstrations show concrete steps: use addr2line to map a panic PC to linux source lines, capture oops across reboots with pstore reserves 2MB to save kernel logs on soft reboot, collect a vmcore via crashkernel=64M + kexec/kdump and analyze with gdb/crash, and attach kgdb over serial (proxy created with TCP ports e.g. 5550) to step through kernel code. ftrace function_graph traces revealed a deadlock in the CPUfreq governor caused by nested mutex acquisition. Some demos need minor target-specific setup but all techniques work end-to-end.
AI-written summary · about
chapters (16)
- 0:00Start
- 1:04THIS TALK IS NOT ABOUT
- 2:40DEBUGGING STEP-BY-STEP
- 3:30TYPES OF PROBLEMS
- 4:32TOOLS AND TECHNIQUES
- 6:09PROBLEMS VS TECHNIQUES
- 10:41KERNEL PANIC
- 18:57CONFIGURING PSTORE
- 29:30KERNEL DEBUGGING WITH GDB
- 39:00TRACE EVENTS
- 39:15KPROBE
- 39:37FRAMEWORKS AND TOOLS
- 40:44ENABLING FTRACE
- 41:19FUNCTION TRACER
- 51:01DEBUGGING LOCKUPS
- 51:20CONCLUSION
related talks
37mPracticing Linux Crash/Panic Issue on Production and Cloud Server: Using Kdump + Crash
55mLinux Kernel Debug And Profiling Tools
34mPostmortem Debugging with Coresight
37mBreaking and Fixing the Kernel: Crashes, Debugging & Performance Tun...
58m“Debugging Linux C++”
35mLinux Tracing updates
28mExtreme OS Kernel Testing
31mFantastic tracepoints and where to find them