Bug 13017
Summary: | ATA bus errors on resume | ||
---|---|---|---|
Product: | IO/Storage | Reporter: | Rafael J. Wysocki (rjw) |
Component: | Serial ATA | Assignee: | Jeff Garzik (jgarzik) |
Status: | CLOSED OBSOLETE | ||
Severity: | normal | CC: | alan, florian, niel.lambrechts, tj |
Priority: | P1 | ||
Hardware: | All | ||
OS: | Linux | ||
Kernel Version: | 2.6.29 | Subsystem: | |
Regression: | Yes | Bisected commit-id: | |
Bug Depends on: | |||
Bug Blocks: | 12398 | ||
Attachments: |
EXT4 errors, captured with Tejun's debug patch
No EXT4 errors, using Tejun's debug patch messages (2.6.29.4 - no EXT4 errors) messages (2.6.28.10 - no EXT4 errors) |
Description
Rafael J. Wysocki
2009-04-05 22:04:25 UTC
Ignore-Patch : http://marc.info/?l=linux-kernel&m=123865517107421&w=4 No reporter response, closing. EXT4 file-system errors resurfaced in 2.6.30-rc6. Was able to trigger the bug with Tejun Heo's debug patch. Problem under discussion. Created attachment 21548 [details]
EXT4 errors, captured with Tejun's debug patch
Created attachment 21549 [details]
No EXT4 errors, using Tejun's debug patch
Created attachment 21550 [details]
messages (2.6.29.4 - no EXT4 errors)
Created attachment 21551 [details]
messages (2.6.28.10 - no EXT4 errors)
Description of above /var/log/messages attachments: I did a hibernation/resume cycle using console, then X for each kernel I have back to 2.6.28. I originally noticed EXT4 errors in 2.6.29 and now again in 2.6.30-rc6 (perhaps rc5 as well), but these still only happen intermittently. I attached 2 x /var/log/messages output for 2.6.30-rc6. Both running Tejun's debug patch, but one of them has output when the EXT4 file-system errors triggered. The other older kernel version messages I attached for the sake of comparison. They also seem to contain ATA resets. Niel Tested Tejun's readahead patch, which did not trigger the bug. Bug seen again in latest 2.6.30-rc7 git kernel, with a resume after hibernating leading to EXT4 errors. Also, it seems 2.6.28.10 is good, I took some time to try and trigger it there, but it did not even when hibernating with a reasonably active system. I am going to try and bisect this again, it is driving me up the wall. Regards, Niel Is this bug still present in current mainline kernels? |