Diagnose Linux kernel panics, oopses, lockups, and memory corruption.
npx skills add https://github.com/gitcomit8/agent-skills --skill kernel-debug-helper
Please help me install this Agent Skill. Skill: kernel-debug-helper Source: https://github.com/gitcomit8/agent-skills/tree/main/kernel-debug-helper Command: npx skills add https://github.com/gitcomit8/agent-skills --skill kernel-debug-helper
This Skill helps intermediate Linux kernel developers systematically diagnose and resolve complex kernel issues like panics, oopses, lockups, and memory corruption, providing actionable reports and precise debugging commands.
objdump, ftrace, kprobe, kgdb, and dynamic debug.NULL pointer dereference and a stack trace, this Skill will analyze the provided logs, identify the likely cause within the igb driver, suggest using objdump to pinpoint the exact source line, and provide commands to set up kprobe for further investigation.Use the kernel-debug-helper skill to analyze the provided kernel panic log and suggest debugging steps.
High-intent search queries and answers about installing and using this skill.
To debug a Linux kernel panic, you analyze the stack trace to classify the failure type, collect artifacts like logs, and use tools such as objdump to pinpoint the exact source line causing the issue.
The best way to diagnose a Linux kernel oops or lockup is following a structured workflow that identifies the crash context, determines the failure type, and applies dynamic debugging tools like ftrace or kprobe to isolate the root cause.
Ftrace works for debugging memory corruption by tracing kernel functions to monitor execution flow and identify unauthorized memory writes, helping developers determine the root cause of the corruption through systematic artifact collection.
Yes, you can use kgdb and kprobe to troubleshoot Linux kernel driver issues. These tools allow you to set dynamic breakpoints and trace specific driver functions to investigate failures like NULL pointer dereferences.
Yes, you need to understand kernel internals and debugging methodologies to use Linux kernel debugging tools effectively, as interpreting artifacts and applying tools like objdump requires knowledge of kernel architecture.
Linux kernel debugging fails to find the root cause of a NULL pointer dereference when necessary artifacts are missing or the failure type is misclassified, preventing accurate application of tools like objdump to pinpoint the source line.
thimsluggaCoordinate multi-agent workflows to analyze Linux kernel crashes and produce debug reports.
Binh230199Diagnose embedded Linux kernel crashes, hangs, and driver faults on automotive targets.
kzahediConfigure and build YARS with debug symbols for debugging sessions.
openeuler-mirrorAnalyze Linux kernel VMcore crash dumps via memory reverse-engineering and source forward-tracing.