Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top


  • 2.6+ Kernel
  • Or older 2.4


  • Generic suggested guidelines with regards to Linux kernel crash dump analysis
    • Skills required, i.e. Kernel compilation skills etc


share|improve this question this supposed to be suggestions as to how to perform a crash dump analysis? The format, while structured nicely, isn't very clear at first glance. Written slightly different, it would almost sound like you're gathering a skills requirements checklist for a position you're going to fill... – Avery Payne Jun 28 '09 at 0:21
@Avery: I'm sorry if the format of my question isn't structured in a coherent manner. Actually, I'm solely interested in learning... – Aaron Jun 28 '09 at 2:31
I would appreciate any pointers... – Aaron Jun 28 '09 at 9:52
up vote 6 down vote accepted

For basic crash dump analysis no particular skills are needed. If you can follow the instructions and open a dump with crash then you can do some basic diagnostics without any in depth knowledge of the kernel. However, for anything beyond the basics you're going to need to know how to debug code using gdb, develop a good knowledge of kernel structure and code aswell as learning how x86 and x86_64 actually work. There are plenty of resources you can google for to help with that. RedHat also run a kernel internals course which is well worth it (if someone else pays)

Once you have the dump open you can do some basic checks that will help diagnose a large number of dumps. When you open the dump you should get some basic info including the load at the time of the crash - always a useful pointer. Looking in the ring buffer log will give you a trace of the crash, taking info from here and googling will often show it is a known issue with a fix. Another place to look is at free memory - if you're down to a handful of small pages you know why the crash/hang occurred.

This is a pretty big subject. I've never come across any really good tutorial type resources with example crash dumps to look through, starting with simple to diagnose problems leading through to much more in depth root causes. Maybe that would be a worthy project.

share|improve this answer

Here's one pointer which may apply:

Kdump/Kexec Howto

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.