linux-debugging

Diagnose embedded Linux kernel crashes, hangs, and driver faults on automotive targets.

1|Updated Feb 28, 2026
One-click install
npx skills add https://github.com/Binh230199/ai --skill linux-debugging
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: linux-debugging
Source: https://github.com/Binh230199/ai/tree/main/.github/skills/linux-debugging
Command: npx skills add https://github.com/Binh230199/ai --skill linux-debugging

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps diagnose and fix hard-to-trace failures on embedded Linux targets used in automotive IVI, HUD, and RSE systems. It is designed for kernel crashes, hangs, driver problems, and performance regressions where serial access, logs, and low-level system inspection are essential.

Core Features & Use Cases

  • Kernel crash analysis: Interpret oops, panic, BUG, and stack trace output to identify the failing code path.
  • Live diagnostics: Inspect dmesg, dynamic debug, /proc, /sys, ftrace, and perf data to understand system state.
  • Remote and hardware debugging: Use gdbserver, KGDB, and OpenOCD for process, kernel, and JTAG-based investigation.
  • Use case: A device boots but randomly hangs under load; this Skill guides serial log capture, tracing, symbol decoding, and root-cause isolation.

Quick Start

Ask for help debugging your embedded Linux issue by describing the symptom, target hardware, and whether you need crash, hang, perf, or driver analysis.

Frequently Asked Questions about linux-debugging

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

FAQPage Schema
How do I debug embedded Linux kernel crashes and analyze oops or panic traces?

Embedded Linux kernel crash debugging requires interpreting oops, panic, and stack trace output to identify the failing code path. You can inspect dmesg, dynamic debug, /proc, and /sys data to understand the system state and decode the fault.

What's the best way to diagnose random hangs on automotive IVI and RSE targets under load?

Diagnosing random hangs on automotive IVI targets involves guiding serial log capture, tracing, symbol decoding, and root-cause isolation. You use ftrace and perf tooling to profile system behavior and inspect system state to validate fixes for the hang.

Can I use gdbserver and OpenOCD for remote process and JTAG bring-up on embedded Linux?

Yes, remote process debugging and JTAG bring-up on embedded Linux use gdbserver, KGDB, and OpenOCD. These tools allow you to connect to the target hardware, investigate kernel issues remotely, and decode faults directly from the automotive target.

How do I trace and profile driver faults using ftrace and perf on embedded Linux?

Tracing and profiling driver faults on embedded Linux uses ftrace and perf tooling to capture system state. You inspect /proc, /sys, and dmesg output to understand the driver behavior, decode the faults, and validate applied fixes.

Do I need serial console access to debug embedded Linux failures on automotive hardware?

Yes, serial console access is required to debug embedded Linux failures on automotive hardware. Kernel log analysis, system-state inspection, and capturing oops or panic output depend on direct serial access to the IVI, HUD, or RSE target.

Does this Skill support diagnosing performance regressions and analyzing system-state on HUD targets?

Yes, diagnosing performance regressions and analyzing system-state on HUD targets is fully supported. The Skill applies perf and ftrace profiling, alongside /proc and /sys inspection, to decode faults and validate fixes for performance issues.