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.
DescriptionDr. David Alan Gilbert
2015-06-04 17:13:53 UTC
Description of problem:
abrt flags anything in the kernel logs with DEBUG as an oops because it spots the BUG in DEBUG; e.g. running a 3.1.0.0-258 I get 5 'oops' recorded
Version-Release number of selected component (if applicable):
abrt-console-notification-2.1.11-19.el7.x86_64
abrt-2.1.11-19.el7.x86_64
abrt-tui-2.1.11-19.el7.x86_64
abrt-addon-python-2.1.11-19.el7.x86_64
abrt-addon-pstoreoops-2.1.11-19.el7.x86_64
abrt-addon-xorg-2.1.11-19.el7.x86_64
abrt-cli-2.1.11-19.el7.x86_64
abrt-retrace-client-2.1.11-19.el7.x86_64
abrt-libs-2.1.11-19.el7.x86_64
abrt-python-2.1.11-19.el7.x86_64
abrt-addon-vmcore-2.1.11-19.el7.x86_64
abrt-addon-ccpp-2.1.11-19.el7.x86_64
abrt-addon-kerneloops-2.1.11-19.el7.x86_64
How reproducible:
100%
Steps to Reproduce:
1. Boot a -debug kernel
2. watch abrt complain
Actual results:
cd /var/tmp/abrt
# cat oops*/backtrace
ODEBUG: 213 of 213 active objects replaced
EDAC DEBUG: edac_mc_sysfs_init: device mc created
EDAC DEBUG: sbridge_get_onedevice: Detected 8086:3cf4
EDAC DEBUG: get_memory_layout: SAD#1, interleave #0: 1
EDAC DEBUG: get_dimm_config: mc#1: Node ID: 1, source ID: 1
Expected results:
A happy relaxed abrt that realise DEBUG's aren't BUGs
Additional info:
(This is a machine that started off as 7.0 and has been slowly had bits upgraded).
Thank you for reporting this bug! Unfortunately the fix is not trivial and we're not going to be able to do it in time for RHEL 7.2, so I'm deferring it to 7.3.
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.
https://access.redhat.com/errata/RHBA-2018:0949