Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 242902
Description
Robert Spanton
2007-06-06 11:59:03 UTC
Created attachment 156339 [details]
dmesg output
I should add that there were no problems with hard disk access whilst using FC6 on the same laptop. Still happens with kernel 2.6.21-1.3228.fc7, but seems to be less often. Created attachment 159891 [details]
kernel-2.6.22.1-27.fc7 dmesg output (grep for ata1)
Also still happens with kernel-2.6.22.1-27.fc7. I retract the previous
statement about it happening less often - it seems fairly random.
Please find dmesg attached - grep for ata1 to see messages.
Again, still occurs in kernel-2.6.22.1-33.fc7 And kernel-2.6.22.1-41.fc7 Hello, I'm reviewing this bug as part of the kernel bug triage project, an attempt to isolate current bugs in the fedora kernel. http://fedoraproject.org/wiki/KernelBugTriage I am CC'ing myself to this bug and will try and assist you in resolving it if I can. There hasn't been much activity on this bug for a while. Could you tell me if you are still having problems with the latest kernel? I'm re-assigning this bug to the PATA maintainer which will hopefully prompt a review. If the problem no longer exists then please close this bug or I'll do so in a few days if there is no additional information lodged. Cheers Chris Thanks for assigning it over. I'll take a look next week Hi, Sorry, I've been away from my machine for a week - hence the lack of updates. I still get the problem with 2.6.22.4-65.fc7. I've just updated to 2.6.22.5-76.fc7, and should know within the next couple of days if the bug persists. Cheers, Rob Created attachment 196591 [details]
kernel-2.6.22.5-76.fc7 dmesg output
After around an hour of laptop use, 2.6.22.5-76.fc7 showed the same bug. I've attached the dmesg just in case there are some subtle differences between it and the previous versions. Rob Problems persist in kernel-2.6.22.9-91.fc7 Created attachment 220391 [details]
kernel-2.6.22.9-91.fc7 dmesg
dmesg for kernel-2.6.22.9-91.fc7
Created attachment 243811 [details]
2.6.23.1-10.fc7 dmesg
Problem persists in kernel-2.6.23.1-10.fc7.
Getting fairly annoying - I can't give presentations etc without having to
sometimes wait 30 seconds between slides :-S
Created attachment 252311 [details]
2.6.23.1-42.fc8 dmesg
Same problem happens in F8 - see attached dmesg. Problem does not seem to happen in kernel-2.6.23.1-49.fc8. Closing; reopen bug if problem occurs again. Created attachment 287351 [details]
2.6.23.8-63.fc8 dmesg
Turns out that the bug is still present in kernel-2.6.23.8-63.fc8. Please find
dmesg attached. I'm reopening this bug.
Created attachment 290234 [details]
2.6.23.9-85.fc8 dmesg
Bug still in kernel-2.6.23.9-85.fc8.
I've run smartctl -t short /dev/sda on it. I had to try this several times to get the test to complete, because the drive kept getting reset when the error this bug is about happened. When it did complete, it reported no errors. Is there any more information that I should be providing? Cheers, Rob I see the same bug on an old reliable uniprocessor system after upgrading to Fedora 8 and kernel 2.6.23.9-85.fc8 -- this hardware never had this problem before (using fc6 and kernel 2.6.22.14-72.fc6, before PATA hd drivers got merged with sd). This system uses Intel motherboard with 82801 chip, plus a couple of PATA cards (PDC20267 and 20269). The symptoms are bursts of error messages about 5 seconds apart similar to the following: kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 kernel: ata4.00: BMDMA stat 0x64 kernel: ata4.00: cmd ca/00:10:1f:35:00/00:00:00:00:00/e0 tag 0 cdb 0x0 data 8192 out kernel: res 51/84:10:1f:35:00/00:00:00:00:00/e0 Emask 0x10 (ATA bus error) kernel: ata4: soft resetting port kernel: ata4.00: configured for UDMA/100 kernel: ata4.01: configured for UDMA/100 kernel: ata4: EH complete kernel: sd 3:0:0:0: [sdd] 320173056 512-byte hardware sectors (163929 MB) kernel: sd 3:0:0:0: [sdd] Write Protect is off kernel: sd 3:0:0:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA kernel: sd 3:0:1:0: [sde] 320173056 512-byte hardware sectors (163929 MB) kernel: sd 3:0:1:0: [sde] Write Protect is off kernel: sd 3:0:1:0: [sde] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA kernel: sd 3:0:0:0: [sdd] 320173056 512-byte hardware sectors (163929 MB) kernel: sd 3:0:0:0: [sdd] Write Protect is off kernel: sd 3:0:0:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA kernel: sd 3:0:1:0: [sde] 320173056 512-byte hardware sectors (163929 MB) kernel: sd 3:0:1:0: [sde] Write Protect is off kernel: sd 3:0:1:0: [sde] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Since there were no hardware changes in upgrading FC6->F8, I suspect the new merged hd/sd driver. (In reply to comment #22) > I see the same bug on an old reliable uniprocessor system after upgrading to > Fedora 8 and kernel 2.6.23.9-85.fc8 -- this hardware never had this problem > before (using fc6 and kernel 2.6.22.14-72.fc6, before PATA hd drivers got merged > with sd). This system uses Intel motherboard with 82801 chip, plus a couple of > PATA cards (PDC20267 and 20269). Here is the relevant lspci output: 00:1f.1 IDE interface: Intel Corporation 82801BA IDE U100 Controller (rev 04) 02:0b.0 Mass storage controller: Promise Technology, Inc. 20269 (rev 02) 02:0c.0 Mass storage controller: Promise Technology, Inc. PDC20267 (FastTrak100/Ultra100) (rev 02) I checked past 3 months of logs -- there were NO errors of this type before upgrading to Fedora 8 and the latest kernel 2.6.23.9-85.fc8 -- and there were no hardware changes -- so the most reasonable hypothesis is that there is something wrong with the merged hd/sd driver. My machine's problem seems to be related to a Promise controller driver. See http://www.opensubscriber.com/message/linux-ide@vger.kernel.org/8302327.html which says that for Promise 20267 which uses pata_pdc202xx_old module, one needs burst mode -- it is pretty essential and should not be optional. I haven't tested this patch yet. ...but the pata_pdc202xx_old module patch doesn't help: Jan 8 21:17:16 fw kernel: ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen Jan 8 21:17:16 fw kernel: ata3.00: cmd ca/00:08:97:0c:00/00:00:00:00:00/e0 tag 0 cdb 0x0 data 4096 out Jan 8 21:17:16 fw kernel: res 40/00:08:77:16:00/00:00:00:00:00/e0 Emask 0x4 (timeout) Jan 8 21:17:17 fw kernel: ata3: soft resetting port Jan 8 21:17:17 fw kernel: ata3.00: configured for UDMA/33 Jan 8 21:17:17 fw kernel: ata3.01: configured for UDMA/100 Jan 8 21:17:17 fw kernel: ata3: EH complete Jan 8 21:17:17 fw kernel: sd 2:0:0:0: [sdb] 320173056 512-byte hardware sectors (163929 MB) Jan 8 21:17:17 fw kernel: sd 2:0:0:0: [sdb] Write Protect is off Jan 8 21:17:17 fw kernel: sd 2:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Jan 8 21:17:17 fw kernel: sd 2:0:1:0: [sdc] 320173056 512-byte hardware sectors (163929 MB) Jan 8 21:17:17 fw kernel: sd 2:0:1:0: [sdc] Write Protect is off Jan 8 21:17:17 fw kernel: sd 2:0:1:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Jan 8 21:17:17 fw kernel: sd 2:0:0:0: [sdb] 320173056 512-byte hardware sectors (163929 MB) Jan 8 21:17:17 fw kernel: sd 2:0:0:0: [sdb] Write Protect is off Jan 8 21:17:17 fw kernel: sd 2:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Jan 8 21:17:17 fw kernel: sd 2:0:1:0: [sdc] 320173056 512-byte hardware sectors (163929 MB) Jan 8 21:17:17 fw kernel: sd 2:0:1:0: [sdc] Write Protect is off Jan 8 21:17:17 fw kernel: sd 2:0:1:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA FYI: Reverting to hd style drivers fixes the sd style driver's "ata ... frozen" messages -- although there are some "SeekComplete" errors reported by the hd* device, the raid5 driver sails through them. Created attachment 293049 [details]
2.6.23.14-107.fc8 dmesg
Bug still present in kernel-2.6.23.14-107.fc8.
Comment #22-#26 are a different bug. I know what the promise one occurs and is being worked up upstream and here. Promise controllers sometimes complete an I/O and don't send us an interrupt. Old IDE cleans up in that case libata doesn't (because the cleanup technique that works for PATA hangs a lot of SATA controllers). The original bug is a drive simply "going away" for a bit but without providing any more meaningful diagnostics. Thanks, Alan, that's a lucid explanation. As a workaround for comment #22-#26, I'd recommend that Promise users recompile their kernels with hd-style PATA drivers. This worked for me. Created attachment 295618 [details]
2.6.23.15-137.fc8 dmesg
Bug still present in 2.6.23.15-137.fc8.
After reading some of the comments on the kernel bug that I linked to, I tried leaving a CD in my CD drive. This appears to make the errors go away. The CD drive isn't the drive that features in the error messages. I have no idea what this means! Created attachment 297436 [details]
2.6.24.3-12.fc8 dmesg
Bug still present in 2.6.24.3-12.fc8.
Still only happens when there isn't a CD in the drive.
Created attachment 308918 [details]
kernel-2.6.25.3-18.fc9 dmesg
Bug still occurring in F9.
Created attachment 319462 [details]
kernel-2.6.26.3-29.fc9 dmesg
Bug still present in 2.6.26.3-29
This message is a reminder that Fedora 8 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 8. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '8'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 8's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 8 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping This message is a reminder that Fedora 9 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 9. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '9'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 9's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 9 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping Fedora 9 changed to end-of-life (EOL) status on 2009-07-10. Fedora 9 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed. |