offline-memory-fault-diagnosis

Correlate iBMC, kernel, and system logs to diagnose Linux memory faults.

3|2|Updated Apr 24, 2026
One-click install
npx skills add https://github.com/openeuler-mirror/witty-diagnosis-agent --skill offline-memory-fault-diagnosis-openeuler-mirror
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: offline-memory-fault-diagnosis
Source: https://github.com/openeuler-mirror/witty-diagnosis-agent/tree/main/skills/offline-memory-fault-diagnosis
Command: npx skills add https://github.com/openeuler-mirror/witty-diagnosis-agent --skill offline-memory-fault-diagnosis-openeuler-mirror

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill solves the complexity of manual server memory troubleshooting by automating the correlation of disparate hardware and OS logs to pinpoint physical or logical memory faults.

Core Features & Use Cases

  • Multi-Source Correlation: Automatically aligns iBMC hardware events, kernel MCE logs, and system messages to reconstruct a precise fault timeline.
  • Root Cause Analysis: Identifies specific DIMM slots or software-induced memory leaks (OOM) with high confidence.
  • Use Case: When a server experiences a sudden crash, use this Skill to analyze the collected log bundle to determine if the root cause was a failing DIMM module or a kernel-level memory leak.

Quick Start

Use the offline-memory-fault-diagnosis skill to analyze the server logs located in the /tmp/logs directory and generate a root cause report.

Frequently Asked Questions about offline-memory-fault-diagnosis

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

FAQPage Schema
How do I diagnose Linux server memory faults from kernel and system logs?

You can diagnose Linux server memory faults by using automated scripts to correlate iBMC hardware events, kernel MCE logs, and system messages, pinpointing specific DIMM slots or software-induced leaks.

What is the best way to correlate iBMC and kernel logs for ECC error troubleshooting?

Correlating iBMC and kernel logs for ECC error troubleshooting is best handled by automating multi-source log alignment to reconstruct a precise fault timeline and validate physical memory hardware failures.

Can I identify a specific failing DIMM slot from an offline server crash log bundle?

Yes, you can identify a specific failing DIMM slot by parsing the collected offline server log bundle to align hardware events and kernel MCE logs for root cause validation.

Does offline memory fault diagnosis require Python 3 to run the diagnostic scripts?

Yes, offline memory fault diagnosis requires Python 3 to execute the diagnostic scripts necessary for parsing logs and validating evidence of MCE events or OOM kills.

Why do I need to correlate iBMC hardware events with kernel MCE logs for root cause analysis?

Correlating iBMC hardware events with kernel MCE logs is needed to distinguish between physical DIMM module failures and kernel-level memory leaks during sudden server crash troubleshooting.

What is automated multi-source memory diagnostics for Linux servers?

Automated multi-source memory diagnostics for Linux servers is the process of parsing and aligning disparate hardware and OS logs to pinpoint physical or logical memory faults without manual correlation.