Bug 786689

Summary: SATA link down errors on JMicron controller
Product: [Fedora] Fedora Reporter: Erasmo Acosta <eacosta>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 16CC: agajania, eacosta, gansalmon, itamar, jforbes, jonathan, kernel-maint, madhu.chinakonda
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-11-14 15:36:29 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
These are the errors I see booting with the JMicron Controller plugged in
none
Post boot SATA link down errors
none
lspci output
none
This contains a the message logs errors with kernel 3.3.0-4.fc16.x86_64 none

Description Erasmo Acosta 2012-02-02 07:09:44 UTC
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:

Comment 1 Erasmo Acosta 2012-02-02 07:10:26 UTC
Created attachment 558987 [details]
Post boot SATA link down errors

Comment 2 Erasmo Acosta 2012-02-02 07:11:35 UTC
Created attachment 558988 [details]
lspci output

Comment 3 Dave Jones 2012-03-22 17:15:54 UTC
[mass update]
kernel-3.3.0-4.fc16 has been pushed to the Fedora 16 stable repository.
Please retest with this update.

Comment 4 Dave Jones 2012-03-22 17:17:54 UTC
[mass update]
kernel-3.3.0-4.fc16 has been pushed to the Fedora 16 stable repository.
Please retest with this update.

Comment 5 Dave Jones 2012-03-22 17:26:23 UTC
[mass update]
kernel-3.3.0-4.fc16 has been pushed to the Fedora 16 stable repository.
Please retest with this update.

Comment 6 Erasmo Acosta 2012-03-27 21:19:36 UTC
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.

Comment 7 Aram Agajanian 2012-10-02 18:50:51 UTC
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.

Comment 8 Aram Agajanian 2012-10-02 18:53:47 UTC
This bug seems similar to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/910999

Comment 9 Dave Jones 2012-10-23 15:36:55 UTC
# 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).

Comment 10 Justin M. Forbes 2012-11-14 15:36:29 UTC
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.