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.
*** This bug has been marked as a duplicate of bug 639068 ***
Not really a duplicate - warnings shouldn't be reported to the user at all.
(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...
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 ...