Bug 67609 - Need some kind of kernel crash dump thingy
Summary: Need some kind of kernel crash dump thingy
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Red Hat Enterprise Linux 2.1
Classification: Red Hat
Component: kernel
Version: 2.1
Hardware: i686
OS: Linux
high
medium
Target Milestone: ---
Assignee: Larry Woodman
QA Contact: Brian Brock
URL: http://lkcd.sf.net
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2002-06-28 07:46 UTC by Johan Walles
Modified: 2007-11-30 22:06 UTC (History)
0 users

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2002-06-28 07:46:31 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Johan Walles 2002-06-28 07:46:27 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.9) Gecko/20020412
Debian/0.9.9-6

Description of problem:
Since our RHAS2.1 keeps falling over (bug 67608) it would be helpful if you
could add something like "Linux Kernel Crash Dumps" ("http://lkcd.sf.net") to
your distro(s).  That would enable us (and others) to file kernel bugs with more
information than just "it crashed".

Preferrably you should add a script that generates some kind of text file (with
a list of relevant modules, backtraces and whatever other information you feel
important) that can be attached to the bug report.


Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. Wait for the kernel to crash with a blank screen.
2. Reboot.


Actual Results:  -

Expected Results:  Some kind of kernel crash dump information should appear
under /var/log or wherever.  Possibly, a text file with that information should
be e-mailed to root as well.


Additional info:
Marked priority "high" as it is often impossible to report kernel crashes in any
helpful way.  I have no idea whether LKCD is technically sound, but the idea is
*definitely* correct.

Comment 1 Johan Walles 2002-06-28 11:20:58 UTC
Just discovered netdump.  Will try to get it working.



Note You need to log in before you can comment on or make changes to this bug.