dump-printk

Extract kernel printk messages from a PearPC memory dump.

438|75|Updated Jan 11, 2015
One-click install
npx skills add https://github.com/sebastianbiallas/pearpc --skill dump-printk
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dump-printk
Source: https://github.com/sebastianbiallas/pearpc/tree/main/.claude/skills/dump-printk
Command: npx skills add https://github.com/sebastianbiallas/pearpc --skill dump-printk

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Extract and display the Linux kernel printk ring buffer from a PearPC memory dump.

Core Features & Use Cases

  • Extracts the printk buffer from a PearPC memory dump and reports the last message, any Oops, and boot stage reached.
  • Simple, script-driven extraction to aid debugging of kernel logs in emulated PPC environments.

Quick Start

Use python3 scripts/debug/memdump.py printk <dump-file> to extract the kernel printk buffer from a PearPC memory dump.

Frequently Asked Questions about dump-printk

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I extract kernel printk messages from a PearPC memory dump?

Extract kernel printk messages from a PearPC memory dump by running python3 scripts/debug/memdump.py printk <dump-file>. This script reads the memory dump and reports the last printk entry, any Oops messages, and the boot stage reached.

What is the best way to debug a kernel panic in a PearPC virtual machine?

Debugging a kernel panic in a PearPC virtual machine is best done by extracting the kernel printk ring buffer from the memory dump. This reveals the last messages and boot stage reached before the crash occurred.

Do I need to specify a dump file when extracting printk data?

You do not need to specify a dump file when extracting printk data. The script defaults to reading a file named memdump_jit.bin if no arguments are provided to the command.

What information can I get from a Linux kernel memory dump during boot issues?

From a Linux kernel memory dump during boot issues, you can extract the printk ring buffer to retrieve the last kernel message, identify any Oops errors, and determine the exact boot stage reached before failure.

Can I use this script to read memory dumps from other virtual machines?

This script is specifically applicable for debugging kernel boot issues, panics, and Oops in PearPC virtual machines by extracting the printk buffer from its memory dumps.

Why is my Linux kernel not booting in PearPC and how can I check the logs?

To check why a Linux kernel is not booting in PearPC, extract the kernel printk messages from the memory dump. This reports the last printk entry and boot stage reached to help pinpoint the failure.