Red Hat Bugzilla – Bug 924839
Capture output of makedumpfile --dump-dmesg for available vmcores
Last modified: 2016-04-18 06:22:36 EDT
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@redhat.com> 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@redhat.com>
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