Red Hat Bugzilla – Bug 1228344
Don't record oops if the kernel says DEBUG
Last modified: 2018-04-10 13:43:10 EDT
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.
We are hitting this very often on RHEL-7.3 builds, such as RHEL-7.3-20160719.1 Is there any update about this problem?
No update yet, but I believe we can fix this issue by introducing a black list of ignored messages.
Clearing the needinfo as the info was provided in #4.
Fix pull request: https://github.com/abrt/abrt/pull/1244
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