Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
The makedumpfile command has the ability to extract the dmesg buffer from a saved kernel dump (vmcore) file.

Often the oops, panic and other messages logged are all that are required to match an instance with a known problem, or to support initial first-fault debugging.

Capturing this data in sos avoids the need for further round trips to collect it manually.

E.g.:

  # makedumpfile  --dump-dmesg vmcore dmesg

  The dmesg log is saved to dmesg.

RHEL6 kernels include the VMCOREINFO section in the dump file so there is no need for additional debuginfo.


Version-Release number of selected component (if applicable):
2.2-*.el6

How reproducible:
100%

Steps to Reproduce:
1. sosreport
2. tar xf $report
3. ls $report_path/sos_commands/kernel
  
Actual results:
No saved dmesg files.

Expected results:
Saved dmesg files with a named based on the name of the dump file from which it was generated.

Additional info:

commit 04d4e4145d695232ba7f7e0a4dd539b39de1dc8b
Author: Bryn M. Reeves <bmr>
Date:   Tue Aug 13 18:46:47 2013 +0100

    Collect saved vmcore-dmesg.txt files in kdump plug-in
    
    Recent versions of kexec-utils automatically generate a text
    file containing the dmesg buffer of the captured vmcore.
    
    This is useful for first-fault debugging and should be included.
    
    Signed-off-by: Bryn M. Reeves <bmr>

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2013-1688.html