Hide Forgot
Description of problem: May 27 22:20:32 lap1 kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x80002 action 0x6 frozen May 27 22:20:32 lap1 kernel: ata1: SError: { RecovComm 10B8B } May 27 22:20:32 lap1 kernel: ata1.00: failed command: FLUSH CACHE EXT May 27 22:20:32 lap1 kernel: ata1.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 0 May 27 22:20:32 lap1 kernel: res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout) May 27 22:20:32 lap1 kernel: ata1.00: status: { DRDY } May 27 22:20:32 lap1 kernel: ata1: hard resetting link May 27 22:20:33 lap1 kernel: ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300) May 27 22:20:33 lap1 kernel: ata1.00: SB600 AHCI: limiting to 255 sectors per cmd May 27 22:20:33 lap1 kernel: ata1.00: SB600 AHCI: limiting to 255 sectors per cmd May 27 22:20:33 lap1 kernel: ata1.00: configured for UDMA/100 May 27 22:20:33 lap1 kernel: ata1.00: retrying FLUSH 0xea Emask 0x4 May 27 22:20:33 lap1 kernel: ata1.00: device reported invalid CHS sector 0 May 27 22:20:33 lap1 kernel: ata1: EH complete Drive: Model Family: Seagate Momentus 5400.3 series Model Number: ST9160821AS Firmware Revision: 3.BHE The problem is pretty old (I think since Fedora 11, maybe earlier). Version-Release number of selected component (if applicable): Fedora 13, kernel 2.6.33.4-95.fc13.i686.PAE. How reproducible: Seems pretty random. Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Does the kernel parameter pcie_aspm=off solve the ATA Frozen issue? I do experience a similar issue, (F13 on nVIDIA MOBO), se bug: 611350. (in my case that parameter is a workaround) If pcie_aspm=off does solve the issue, can you upload a lspci -vvv with pcie_aspm enabled and another lspci -vvv with pcie_aspm disabled for comparison?
This message is a reminder that Fedora 13 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 13. 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 '13'. 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 13'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 13 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 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 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.