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.
While testing MCE injection, got this vmcore porcessing failure:
--- Running analyze_VMcore ---
Installing kernel debuginfo(s)
Coredump references 0 debuginfo files, 1 of them are not installed
Setting up yum repositories
Looking for needed packages in repositories
Can't find packages for 1 debuginfo files
All debuginfo files are available
Generating backtrace
abrt-dump-oops: Found oopses: 0
There may be more than one problem here. First one is this clearly broken
behavior of debuginfo installer:
# /usr/libexec/abrt-action-install-debuginfo-to-abrt-cache --size_mb=4096 --exact=/usr/lib/debug/lib/modules/2.6.32-430.el6.i686/vmlinux
Coredump references 0 debuginfo files, 1 of them are not installed
Setting up yum repositories
Looking for needed packages in repositories
Can't find packages for 1 debuginfo files
All debuginfo files are available
[root@guinea ~]# /usr/libexec/abrt-action-install-debuginfo-to-abrt-cache --size_mb=4096 --exact=/usr/lib/debug/lib/modules/2.6.32-430.el6.i686/vmlinux; echo $?
Coredump references 0 debuginfo files, 1 of them are not installed
Setting up yum repositories
Looking for needed packages in repositories
Can't find packages for 1 debuginfo files
All debuginfo files are available
0
# ls /usr/lib/debug/lib/modules/2.6.32-430.el6.i686/vmlinux
ls: cannot access /usr/lib/debug/lib/modules/2.6.32-430.el6.i686/vmlinux: No such file or directory
Debuginfo was NOT installed. Exit code is wrong as well.
Without double-pasted mess:
# /usr/libexec/abrt-action-install-debuginfo-to-abrt-cache --size_mb=4096 --exact=/usr/lib/debug/lib/modules/2.6.32-430.el6.i686/vmlinux; echo $?
Coredump references 0 debuginfo files, 1 of them are not installed
Setting up yum repositories
Looking for needed packages in repositories
Can't find packages for 1 debuginfo files
All debuginfo files are available
0
Since debuginfo installer lied to us, abrt-action-analyze-vmcore thinks that everything is fine, and runs "crash -s vmcore <path-to-missing-debuginfo", storing result in "kernel_log" element... which ends up as:
kernel_log
=====
crash: /var/cache/abrt-di/usr/lib/debug/lib/modules/2.6.32-430.el6.i686/vmlinux: No such file or directory
Usage:
crash [OPTION]... NAMELIST MEMORY-IMAGE (dumpfile form)
crash [OPTION]... [NAMELIST] (live system form)
Enter "crash -h" for details.
=====
abrt-action-analyze-vmcore does not check "crash -s" exit code (this is a second bug).
Then abrt-dump-oops "Found oopses: 0" in kernel_log. Not really a surprise...
Comment 4RHEL Program Management
2013-11-10 12:55:15 UTC
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.
Upstream already has a bit different code, so the fix below may be unnucessary, but on RHEL6.5 machine the folloving hack in vmcore_event.conf works around the problem:
EVENT=analyze_VMcore analyzer=vmcore
# hack
if test -f vmcore-dmesg.txt; then
exec abrt-dump-oops -o vmcore-dmesg.txt >backtrace
fi
# end hack
abrt-action-analyze-vmcore
It uses the fact that kdump in RHEL6 already saves dmesg output as a separate file.