All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steven Haigh <netwiz@crc.id.au>
To: linux-ide@vger.kernel.org
Subject: sata-sil drive detection issues.
Date: Thu, 17 Feb 2011 14:16:04 +1100	[thread overview]
Message-ID: <4D5C92F4.5000906@crc.id.au> (raw)

Hi all,

Firstly, please CC me in all replies as I am not a member of this list.

I have been having an issue with quite a few of the fedora kernels in 
detecting drives on a sil3112 or sil3114 PCI card.

When plugging in a SATA drive (I'm using an external esata drive for 
this test), I see the following appear in dmesg:

[   74.664034] ata10: exception Emask 0x10 SAct 0x0 SErr 0x50000 action 0xe
frozen
[   74.664208] ata10: SError: { PHYRdyChg CommWake }
[   74.664310] ata10: hard resetting link
[   80.416870] ata10: link is slow to respond, please be patient (ready=-19)
[   81.789464] ata10: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[   81.789572] ata10.00: NODEV after polling detection
[   81.789593] ata10: EH complete

No device is detected.

This seems to occur if the drive is turned on after the machine is 
started, and when the system boots. I can see the drive in the card BIOS 
when the system starts if it is powered on after the drive has power.

So far, I have tried the following kernel versions:
2.6.32.26-174.2.xendom0.fc12.x86_64
2.6.35.10-71.fc14.x86_64
2.6.35.11-83.fc14.x86_64
2.6.38-0.rc4.git0.2.fc15.x86_64

If I move the internal SATA cable from the sil3112 or sil3114 card to 
the onboard SATA ports (detected as AHCI), then the drive is detected as 
it should and works perfectly.

I have a current bug open for Fedora at:
https://bugzilla.redhat.com/show_bug.cgi?id=677217

The sil3114 that is currently installed seemed to work perfectly using 
CentOS 5.5 kernel (based on 2.6.18) - I am going to try and install 
CentOS to a different LV to confirm this shortly.

Does anyone have any suggestions on this?

-- 
Steven Haigh

Email: netwiz@crc.id.au
Web: http://www.crc.id.au
Phone: (03) 9001 6090 - 0412 935 897
Fax: (03) 8338 0299

             reply	other threads:[~2011-02-17  3:49 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-17  3:16 Steven Haigh [this message]
2011-02-17  4:23 ` sata-sil drive detection issues Steven Haigh
2011-02-17  9:58   ` Tejun Heo
2011-02-17 23:20     ` Steven Haigh
2011-02-18  9:16       ` Tejun Heo
2011-02-24  2:24         ` Steven Haigh
2011-02-24  8:31           ` Tejun Heo
2011-02-24  9:53             ` Steven Haigh
2011-02-24 10:06               ` Tejun Heo
2011-02-24 16:21                 ` Mark Lord
2011-02-24 16:29                   ` Steven Haigh
2011-02-24 19:04                     ` Mark Lord
2011-02-24 20:26                       ` Mark Lord
2011-02-28 10:07                 ` Steven Haigh

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4D5C92F4.5000906@crc.id.au \
    --to=netwiz@crc.id.au \
    --cc=linux-ide@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.