kdump and crash(8) [more Re: tracking down a lockup problem]

D. Hugh Redelmeier hugh at mimosa.com
Sat Jun 16 17:50:59 UTC 2007


On June 5th, I wrote about how to use the console (including serial
console) to view kernel OOPS, BUGs, and PANICs.
  https://www.redhat.com/archives/fedora-list/2007-June/msg01499.html

Unfortunately, that doesn't work in some cases (like mine).  I want to
be using X, so the console isn't visible and cannot be made visible
after a crash.  Furthermore, I don't have a serial port to use for a
serial console.

Another way of dealing with a kernel panic is using kdump and
crash(8).  There is a howto for using kdump:
  http://fedoraproject.org/wiki/FC6KdumpKexecHowTo

Summary: when the kernel panics, kdump takes over, dumps the system
state to a file, and reboots the system.  Then you can use crash(8) to
analyze the dump file.

Unfortunately, the F7 kdump initscript doesn't work for me.  I have
developed a work-around.  See
  https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=244464

The F7 version of crash(8) doesn't work for me.  I found that a later
version does work.  See
  https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=244524

Now that I've got this figured out, maybe I can focus on the actual
kernel bug
  https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=242836


Has anyone successfully used kdump or crash on F7?  Am I the only one
to hit these problems?




More information about the fedora-list mailing list