Description of problem: syslog is filled with errors Jan 5 10:09:39 ameeba kernel: [ 45.145715] ata7: exception Emask 0x10 SAct 0x0 SErr 0x4000000 action 0xe frozen Jan 5 10:09:39 ameeba kernel: [ 45.145718] ata7: irq_stat 0x00000040, connection status changed Jan 5 10:09:39 ameeba kernel: [ 45.145721] ata7: SError: { DevExch } Jan 5 10:09:39 ameeba kernel: [ 45.145728] ata7: hard resetting link Jan 5 10:09:39 ameeba kernel: [ 45.868029] ata7: SATA link down (SStatus 0 SControl 300) Jan 5 10:09:39 ameeba kernel: [ 45.868040] ata7: EH complete This port does not have anything connected to it Version-Release number of selected component (if applicable): 2.6.35.10-74.fc14.x86_64 How reproducible: repeats all the time Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Empty ports should not give errors Additional info: Is there a way to disable this from Linux side, disabling port from BIOS is not an option
Created attachment 471813 [details] output from lshw
Created attachment 471814 [details] output from lspci
Created attachment 471815 [details] /var/log/messages from last reboot
The problematic device is ata7, which is located in the controller#2, jmicron: Jan 5 10:09:39 ameeba kernel: [ 45.145715] ata7: exception Emask 0x10 SAct 0x0 SErr 0x4000000 action 0xe frozen Jan 5 10:09:39 ameeba kernel: [ 45.145718] ata7: irq_stat 0x00000040, connection status changed Jan 5 10:09:39 ameeba kernel: [ 45.145721] ata7: SError: { DevExch } Jan 5 10:09:39 ameeba kernel: [ 45.145728] ata7: hard resetting link Jan 5 10:09:39 ameeba kernel: [ 45.868029] ata7: SATA link down (SStatus 0 SControl 300) Jan 5 10:09:39 ameeba kernel: [ 45.868040] ata7: EH complete as a workaround, if the 2 ports are not used, you can blacklist the controller module both in grub and in blaclist.conf. ? is it a usb/2 x sata combo card? Maybe the description of this bug should be changed to something similar to: "empty jmicron sata port generates sata execption emask & link down messages"
This happens sometimes on both ports of this controller, which controls two of the external eSATA ports on Asus Maximus Extreme motherboard: http://www.asus.com/Product.aspx?P_ID=m39mcE6kVFexlQhK&content=specifications If I have a disc attached to either one of the ports, this message does not appear and I prefer this workaround ;-)
I'm getting this on 2.6.38.8-35.fc15.x86_64 : Jul 24 22:24:38 hq2 kernel: [15617.621094] ata12: SATA link down (SStatus 1 SControl 10) Jul 24 22:24:38 hq2 kernel: [15617.621113] ata12: EH complete Jul 24 22:24:38 hq2 kernel: [15617.622127] ata12: exception Emask 0x10 SAct 0x0 SErr 0x0 action 0xe frozen Jul 24 22:24:38 hq2 kernel: [15617.622140] ata12: irq_stat 0x00800080, device exchanged Jul 24 22:24:38 hq2 kernel: [15617.622160] ata12: limiting SATA link speed to 1.5 Gbps Jul 24 22:24:38 hq2 kernel: [15617.622171] ata12: hard resetting link but I found that it's actually coming from a USB drive. The ataXX number mapping to the block device is a real PIA. I eventually gave up and just started unplugging drives until I found the culprit. Could your problem actually be a USB->SATA controller problem?
Well, for me it's eSATA for sure, and still an issue with 2.6.35.13-92.fc14.x86_64
Is this issue still happening with recent Fedora releases? (F16 ot F17) The bug-repor was filled agains F14.
Currently on FC16 3.4.4-4.fc16.x86_64 and it is still happening.
Created attachment 599643 [details] ata errors on an empty eSATAp por when using an usb device (3g modem) (USB/eSATA COMBO) In this example (attached file), i do attach a Huawei e173s-6 3G modem to the eSATAp port of my dell e4310 laptop. ata5 is on the eSATAp port, which causes troubles when the modem is in use. So far this issue happens only with such modem (other mass storage / gadgets are not affected). The modem works, but these errors occasionally slows it down. Kernel: 3.4.4-4.fc16.x86_64 Jul 22 16:34:11 grimmjow kernel: [19499.030299] ata5: exception Emask 0x10 SAct 0x0 SErr 0x4000000 action 0xe frozen Jul 22 16:34:11 grimmjow kernel: [19499.030304] ata5: irq_stat 0x00000040, connection status changed Jul 22 16:34:11 grimmjow kernel: [19499.030309] ata5: SError: { DevExch } Jul 22 16:34:11 grimmjow kernel: [19499.030317] ata5: hard resetting link Jul 22 16:34:12 grimmjow kernel: [19499.750971] ata5: SATA link down (SStatus 0 SControl 300) Jul 22 16:34:12 grimmjow kernel: [19499.750987] ata5: EH complete Controller: SATA controller [0106]: Intel Corporation 5 Series/3400 Series Chipset 6 port SATA AHCI Controller [8086:3b2f] (rev 05) That is a eSATAp port, is yours one like it? http://en.wikipedia.org/wiki/ESATAp
It's eSata port on Maximus Extreme (Rev 1.xx)
This message is a notice that Fedora 14 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 14. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '14' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 14 reached 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, you are encouraged to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. 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