Bug 1008592 - abrt fails to detect oops
Summary: abrt fails to detect oops
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: abrt
Version: 22
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: abrt
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 1284286 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-09-16 16:20 UTC by Nicolas Mailhot
Modified: 2016-07-29 10:00 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-07-19 10:22:58 UTC
Type: Bug

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Nicolas Mailhot 2013-09-16 16:20:47 UTC 
Description of problem:
gnome-abrt fails to detect oops such as the one in https://bugzilla.redhat.com/attachment.cgi?id=798313

gnome-abrt-0.3.1-1.fc21.x86_64
Comment 1 Jakub Filak 2013-09-17 15:02:43 UTC 
Thank you for the report!

ABRT doesn't detect lot of oopses coming from kernel/lockdep.c [1] and I'm not sure if ABRT should support all of them. We have to ask kernel folks which oopses do they want to see in Bugzilla.

Not supported oops types:
  INFO: %s-safe -> %s-unsafe lock order detected
  INFO: inconsistent lock state
  INFO: possible circular locking dependency detected
  INFO: possible irq lock inversion dependency detected
  INFO: suspicious RCU usage.
  

1: http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/kernel/lockdep.c
Comment 2 Nicolas Mailhot 2013-09-17 19:48:14 UTC 
If it was not useful to kernel people they wouldn't activate the check in Fedora kernels in the first place, it's not like it was a user setting…
Comment 3 Jakub Filak 2013-09-18 07:28:41 UTC 
CCing Anton because he has the right domain knowledge.
Comment 4 Jakub Filak 2013-10-11 15:05:20 UTC 
Anton, could you please tell us which oopses are kernel people interested in?
Comment 5 Anton Arapov 2014-01-30 16:16:47 UTC 
Jakub,

I prefer to keep the status quo for now. Fedora kernel bug triagers are already overloaded, let them be focused on panics.

Nicolas, your request has been recorded and the next such request will get more decision weight.

Nowadays kernel people are interested and prefer Abrt team to resolve bug 1000000 as soon as possible. :)

thanks,
Comment 6 Jaroslav Reznik 2015-03-03 15:03:56 UTC 
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle.
Changing version to '22'.

More information and reason for this action is here:
https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22
Comment 7 Fedora End Of Life 2016-07-19 10:22:58 UTC 
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.
Comment 8 Jakub Filak 2016-07-29 09:57:53 UTC 
Per comment #5.
Comment 9 Jakub Filak 2016-07-29 10:00:57 UTC 
*** Bug 1284286 has been marked as a duplicate of this bug. ***
Note You need to log in before you can comment on or make changes to this bug.