Bug 459625 - kdump console trace not preserved with dump
kdump console trace not preserved with dump
Status: CLOSED NOTABUG
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: kexec-tools (Show other bugs)
5.2
All Linux
medium Severity low
: rc
: ---
Assigned To: Neil Horman
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2008-08-20 14:01 EDT by Rich Johnson
Modified: 2008-08-20 15:07 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2008-08-20 14:34:39 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Rich Johnson 2008-08-20 14:01:08 EDT
Description of problem:
  kdump console trace preserved with dump.  The console trace contains info (such as script output) useful for debugging problems that may occur during kdump processing.  This info is not kept with the vmcore and is lost with the reboot.

Version-Release number of selected component (if applicable):
  kexec-tools-1.102pre-21.el5_2.2

How reproducible:
  Trigger a kdump.
  
Actual results:
  Dump directory created containing only vmcore.

Desired results:
  Dump directory created containing:
   - vmcore
   - console trace of the dump process.

Additional info:
  dmesg can be used in a pre/post script to optain a partial trace.
  Probably an enhancement.

Avoidance:  
  Use kernel command line to echo console to aserial port and use an external device to capture the trace.
Comment 1 Rich Johnson 2008-08-20 14:27:07 EDT
(In reply to comment #0)
> Description of problem:
>   kdump console trace preserved with dump.  The console trace contains info
[...snip...]
Of course that should be:  kdump console trace *not* preserved with dump...
Comment 2 Neil Horman 2008-08-20 14:34:39 EDT
kdump captures the vmcore, not the log of the capture session.  Given that recording of the log is most usefull for debugging of kdump setups, you will nominally have access to a serial console which can log the session independently.  If you do want to grab the log from within a kdump session, this can be easily implemented using kdump_post and dmesg.
Comment 3 Rich Johnson 2008-08-20 15:07:05 EDT
Unfortunately, it's not quite so easy. 

A dmesg in the kdump_post doesn't capture everything that's been sent to the console--e.g. command output from the scripts.  This could be captured separately  but you'd lose the timing interplay with the kernel messages.  Also, dmesg gives only the current ring buffer contents.  It does not provide the full session.

My concern is more with forensic analysis of a failure at a customer site where the serial output is not necessarily collected.

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