Bug 437854 - kerneloops shouldn't trigger on some WARNING's
Summary: kerneloops shouldn't trigger on some WARNING's
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: kerneloops
Version: rawhide
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-03-17 18:58 UTC by Warren Togami
Modified: 2011-12-13 22:29 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-03-28 16:07:29 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
dmesg output (39.50 KB, text/plain)
2008-03-28 19:19 UTC, Thomas J. Baker 		no flags Details
View All

Description Warren Togami 2008-03-17 18:58:35 UTC 
md0: WARNING: sda2 appears to be on the same physical disk as sda3.

kerneloops shouldn't react to certain WARNING's that are not kernel failures
like above.

kerneloops-0.10-6.fc9.x86_64
Comment 1 Warren Togami 2008-03-17 21:05:54 UTC 
end_request: I/O error, dev fd0, sector 0

This also should be ignored by kerneloops.  This is too common.
Comment 2 Chuck Ebbert 2008-03-17 22:34:12 UTC 
(In reply to comment #1)
> end_request: I/O error, dev fd0, sector 0
> 
> This also should be ignored by kerneloops.  This is too common.

This should not be triggering anything. Maybe the first error is being reported
again?
Comment 3 Chuck Ebbert 2008-03-17 23:02:21 UTC 
(In reply to comment #0)
> md0: WARNING: sda2 appears to be on the same physical disk as sda3.
> 
> kerneloops shouldn't react to certain WARNING's that are not kernel failures
> like above.
> 

This is fixed in 0.10-8
Comment 4 Warren Togami 2008-03-18 02:38:46 UTC 
If you dismiss the pop-up window what causes it to pop-up again?  It saw
previous ignored messages from the logs?  (Isn't this a broken behavior?)
Comment 5 Chuck Ebbert 2008-03-18 05:05:00 UTC 
(In reply to comment #4)
> If you dismiss the pop-up window what causes it to pop-up again?  It saw
> previous ignored messages from the logs?  (Isn't this a broken behavior?)
> 

That would be bug 435065
Comment 6 Thomas J. Baker 2008-03-28 19:19:38 UTC 
Created attachment 299514 [details]
dmesg output
Comment 7 Thomas J. Baker 2008-03-28 19:20:25 UTC 
Comment on attachment 299514 [details]
dmesg output

I'm getting an apparent false positive. Dmesg output attached. I don't see an
oops.
Comment 8 Thomas J. Baker 2008-03-28 19:21:24 UTC 
Sorry, I didn't realize this bug was closed. Should I file a new one?
Comment 9 Chuck Ebbert 2008-04-01 04:03:00 UTC 
(In reply to comment #8)
> Sorry, I didn't realize this bug was closed. Should I file a new one?

Yes please file a new bug.
Note You need to log in before you can comment on or make changes to this bug.