linux-kernel-crash-debug
Debug Linux kernel crashes using the crash utility. Use when users mention kernel crash, kernel panic, vmcore analysis, kernel dump debugging, crash utility, kernel oops debugging, analyzing kernel crash dump files, using crash commands, or locating root causes of kernel issues.
Why use this skill?
Analyze Linux kernel crashes and panics efficiently with the OpenClaw linux-kernel-crash-debug skill. Master vmcore analysis.
Install via CLI (Recommended)
clawhub install openclaw/skills/skills/crazyss/linux-kernel-crash-debugWhat This Skill Does
The linux-kernel-crash-debug skill is a comprehensive diagnostic toolkit for OpenClaw that automates the analysis of Linux kernel crash dumps. By interfacing with the standard crash utility, this skill allows the AI agent to interpret vmcore files, examine memory corruption, investigate kernel panics, and perform deep-dive stack traces. It bridges the gap between raw binary output and actionable engineering insights, providing a structured approach to debugging complex kernel space issues that are otherwise notoriously difficult to isolate.
Installation
To integrate this skill, use the ClawHub package manager or manual deployment:
Using ClawHub
clawhub install openclaw/skills/skills/crazyss/linux-kernel-crash-debug
Manual Installation
- Clone the repository into
~/.openclaw/workspace/skills/linux-kernel-crash-debug. - Ensure the
crashutility andkernel-debuginfopackages are installed on your host system to allow the skill to inspect symbols correctly.
Use Cases
This skill is essential for System Administrators, DevOps Engineers, and Kernel Developers who face unpredictable system instability. Specific scenarios include: identifying the specific process or thread that triggered a kernel panic, analyzing memory leaks in the kernel slab allocator, verifying hardware-related memory corruption via RAM dumps, and ensuring that post-mortem analysis aligns with source code definitions for kernel structures.
Example Prompts
- "The system crashed with a kernel panic yesterday. I have the vmcore and vmlinux files; please analyze the stack trace to find the root cause."
- "My server is showing intermittent kernel oops errors. Can you help me use the crash utility to inspect the task_struct for the process causing the hang?"
- "I'm seeing memory pressure warnings. Use the kmem command in crash to examine the kernel slab cache and identify potential leaks."
Tips & Limitations
- Symbol Versioning: The most critical limitation is that the
vmlinuxdebug symbols must match the running kernel version precisely. If the versions mismatch, the crash utility will fail to map addresses to function names. - Debug Symbols: Ensure
CONFIG_DEBUG_INFOis enabled. Without these symbols, stack traces will be incomplete. - Performance: For large memory dumps, analysis can be resource-intensive. Run these commands on a machine with sufficient RAM relative to the dump size.
- Permissions: Analysis typically requires read access to sensitive kernel dump files, which may necessitate sudo privileges depending on your environment security policy.
Metadata
Not sure this is the right skill?
Describe what you want to build — we'll match you to the best skill from 16,000+ options.
Find the right skillPaste this into your clawhub.json to enable this plugin.
{
"plugins": {
"official-crazyss-linux-kernel-crash-debug": {
"enabled": true,
"auto_update": true
}
}
}Tags(AI)
Flags: file-read, code-execution