On 17/02/2011 2:16 PM, Steven Haigh wrote:
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?
I might have acted a bit prematurely on this. After booting off the
CentOS 5.5 installation DVD, I noticed that the esata drive at the same
problem. After lots of cable swapping and testing, I have found that the
esata cable may be faulty as a direct SATA -> drive connection works
perfectly.
I am unsure however why my previous test of plugging the esata drive
directly to the onboard SATA controller worked - however now this also
fails.
I shall attempt to try some different eSATA cables and report back if I
manage to isolate the issue directly to the sata_sil module.
--
Steven Haigh
Email: netwiz@xxxxxxxxx
Web: http://www.crc.id.au
Phone: (03) 9001 6090 - 0412 935 897
Fax: (03) 8338 0299
--
To unsubscribe from this list: send the line "unsubscribe linux-ide" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
