sebastianbiallas/analyze-oops
.claude/skills/analyze-oops/SKILL.md
Analyze a kernel Oops from the printk buffer in a PearPC memory dump
$ install --global
skillsauthnpx skillsauth add sebastianbiallas/pearpc analyze-oopsInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 16, 2026, 3:41 PM57.9s1 file scanned
SKILL.md
- name:
- analyze-oops
- description:
- Analyze a kernel Oops from the printk buffer in a PearPC memory dump
- allowed-tools:
- Bash, Read, Grep
- argument-hint:
- [dump-file]
Analyze Kernel Oops
Use scripts/debug/memdump.py to extract and analyze the Oops.
Steps
-
Extract the Oops:
python3 scripts/debug/memdump.py oops ${ARGUMENTS:-memdump_jit.bin} -
Decode pt_regs (use the REGS address from the Oops output):
python3 scripts/debug/memdump.py regs DUMP_FILE REGS_ADDRESS -
Disassemble around NIP and LR (convert VA to PA: PA = VA - 0xC0000000):
python3 scripts/debug/disasm_ppc.py DUMP_FILE PA_OF_NIP 16 python3 scripts/debug/disasm_ppc.py DUMP_FILE PA_OF_LR 16 -
Search for the NIP value in both dumps:
python3 scripts/debug/memdump.py find memdump_generic.bin NIP_VALUE python3 scripts/debug/memdump.py find memdump_jit.bin NIP_VALUE -
Check if NIP is a valid address:
- 0xC0xxxxxx = kernel code
- 0xBFxxxxxx = PROM virtual address (prom_mem_phys_to_virt)
- 0xFDxxxxxx = PCI I/O space (not executable)
Report: exception type, faulting address, caller, what the code was trying to do.
Related Skills
sebastianbiallas/.claude/skills/dump-printk
tools
VerifiedTrustedCommunity
--- name: dump-printk description: Extract and display the Linux kernel printk ring buffer from a PearPC memory dump allowed-tools: Bash, Read argument-hint: [dump-file] [search-term] --- # Extract Kernel Printk Buffer Use `scripts/debug/memdump.py printk` to extract the printk ring buffer. ``` python3 scripts/debug/memdump.py printk $ARGUMENTS ``` If no arguments, use `memdump_jit.bin`. Report the last printk message, any Oops, and what boot stage was reached.
434SKILL.mdUpdated Apr 16, 2026
sebastianbiallas/.claude/skills/compare-dumps
tools
VerifiedTrustedCommunity
--- name: compare-dumps description: Compare memory regions between generic and JIT memory dumps to find divergences allowed-tools: Bash, Read argument-hint: [subcommand] [args...] --- # Compare Memory Dumps Use `scripts/debug/memdump.py` subcommands: ``` # Read words at a PA (accepts kernel VA, auto-converts): python3 scripts/debug/memdump.py read memdump_jit.bin PA [count] # Diff two dumps at a PA: python3 scripts/debug/memdump.py diff memdump_generic.bin memdump_jit.bin PA [count] # Sear
434SKILL.mdUpdated Apr 16, 2026
sebastianbiallas/check-trace
testing
VerifiedTrustedCommunity
Analyze the JIT dispatch trace to diagnose boot stalls or crashes
434SKILL.mdUpdated Apr 16, 2026
sebastianbiallas/check-parity
testing
VerifiedTrustedCommunity
Check that aarch64 JIT interpreter functions match generic CPU behavior
434SKILL.mdUpdated Apr 16, 2026