Bug 437854
| Summary: | kerneloops shouldn't trigger on some WARNING's | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Warren Togami <wtogami> | ||||
| Component: | kerneloops | Assignee: | Kernel Maintainer List <kernel-maint> | ||||
| Status: | CLOSED RAWHIDE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | low | Docs Contact: | |||||
| Priority: | low | ||||||
| Version: | rawhide | CC: | cebbert | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | All | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2008-03-28 16:07:29 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: | |||||||
| Attachments: |
|
||||||
|
Description
Warren Togami
2008-03-17 18:58:35 UTC
end_request: I/O error, dev fd0, sector 0 This also should be ignored by kerneloops. This is too common. (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? (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 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?) (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 Created attachment 299514 [details]
dmesg output
Comment on attachment 299514 [details]
dmesg output
I'm getting an apparent false positive. Dmesg output attached. I don't see an
oops.
Sorry, I didn't realize this bug was closed. Should I file a new one? (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. |