Hide Forgot
Created attachment 558986 [details] These are the errors I see booting with the JMicron Controller plugged in Description of problem: I get these "SATA link down" error messages (see 1st attachment) on boot. They go away if I remove the Jmicron controller card. I also occasionally experience additional messages (2nd attachment) post boot during normal operation. Version-Release number of selected component (if applicable): Linux version 3.2.2-1.fc16.x86_64 (mockbuild.fedoraproject.org) (gcc version 4.6.2 20111027 (Red Hat 4.6.2-1) (GCC) ) #1 SMP How reproducible: Always Steps to Reproduce: 1.Boot with JMicron Controller attached to the PCI Bus 2. 3. Actual results: Expected results: Additional info:
Created attachment 558987 [details] Post boot SATA link down errors
Created attachment 558988 [details] lspci output
[mass update] kernel-3.3.0-4.fc16 has been pushed to the Fedora 16 stable repository. Please retest with this update.
Created attachment 573182 [details] This contains a the message logs errors with kernel 3.3.0-4.fc16.x86_64 I still experience the errors with the new kernel. See attachment.
I am seeing similar error on a StarTech S352U2RER RAID enclosure with an eSATA connection. This enclosure uses the Sil5744 IC. My kernel is 3.5.4-1.fc17.x86_64.
This bug seems similar to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/910999
# Mass update to all open bugs. Kernel 3.6.2-1.fc16 has just been pushed to updates. This update is a significant rebase from the previous version. Please retest with this kernel, and let us know if your problem has been fixed. In the event that you have upgraded to a newer release and the bug you reported is still present, please change the version field to the newest release you have encountered the issue with. Before doing so, please ensure you are testing the latest kernel update in that release and attach any new and relevant information you may have gathered. If you are not the original bug reporter and you still experience this bug, please file a new report, as it is possible that you may be seeing a different problem. (Please don't clone this bug, a fresh bug referencing this bug in the comment is sufficient).
With no response, we are closing this bug under the assumption that it is no longer an issue. If you still experience this bug, please feel free to reopen the bug report.