Bug 755671

Summary:	abrt incorrectly describes kernel warnings as crashes
Product:	[Fedora] Fedora	Reporter:	Matthew Garrett <mjg>
Component:	abrt	Assignee:	Jiri Moskovcak <jmoskovc>
Status:	CLOSED NOTABUG	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	16	CC:	dfediuck, dvlasenk, iprikryl, jfeeney, jmoskovc, kklic, mmilata, mtoman, npajkovs
Target Milestone:	---	Keywords:	Reopened
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-12-14 11:58:20 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	744774

Description Matthew Garrett 2011-11-21 17:55:06 UTC

abrt just popped up a message telling me that a crash had been detected in the kernel. In reality, dmesg just shows a warning. Warnings aren't considered high-priority issues, shouldn't be brought to the user's attention in this way and certainly shouldn't be described as crashes.

Comment 1 Jiri Moskovcak 2011-11-24 09:33:01 UTC


*** This bug has been marked as a duplicate of bug 639068 ***

Comment 2 Matthew Garrett 2011-11-24 14:27:21 UTC

Not really a duplicate - warnings shouldn't be reported to the user at all.

Comment 3 Jiri Moskovcak 2011-11-25 08:28:29 UTC

(In reply to comment #2)
> Not really a duplicate - warnings shouldn't be reported to the user at all.

- I don't understand it, so if users are not supposed to know about the warnings why to print them to logs when kernel is compiled without the debugging flags? If I remember correctly even the old kerneloops tool did that...

Comment 4 Jiri Moskovcak 2011-11-25 08:32:53 UTC

After thinking more about this ... We can make abrt to just notify user about the warnings, but not allow him to report it (like we did with the broken bios warnings: #701171), but can someone guarantee that all kernel devs use warnings consistently? AFAICT they don't ...