You are not logged in.
I'm running a Asus P6X58D Premium mobo with a Marvell 9123 SATA 3 controller. When connecting an OCZ Agility 3 SSD drive (with SATA 6 Gb/s cable) or a SATA 3 WD Caviar Black HDD to the Marvell controller, this system will freeze up for about a minute a couple times a day. The system runs fine with drives connected to the regular SATA 2 ports. When the system recovers, dmesg outputs the following:
[ 9441.677779] ata8.00: exception Emask 0x0 SAct 0xf SErr 0x0 action 0x6 frozen
[ 9441.677785] ata8.00: failed command: READ FPDMA QUEUED
[ 9441.677792] ata8.00: cmd 60/70:00:e8:a4:ec/00:00:01:00:00/40 tag 0 ncq 57344 in
[ 9441.677794] res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 9441.677797] ata8.00: status: { DRDY }
[ 9441.677800] ata8.00: failed command: READ FPDMA QUEUED
[ 9441.677835] ata8.00: cmd 60/08:08:40:9d:47/00:00:02:00:00/40 tag 1 ncq 4096 in
[ 9441.677838] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 9441.677845] ata8.00: status: { DRDY }
[ 9441.677847] ata8.00: failed command: READ FPDMA QUEUED
[ 9441.677852] ata8.00: cmd 60/08:10:68:23:8d/00:00:00:00:00/40 tag 2 ncq 4096 in
[ 9441.677853] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 9441.677855] ata8.00: status: { DRDY }
[ 9441.677857] ata8.00: failed command: READ FPDMA QUEUED
[ 9441.677861] ata8.00: cmd 60/88:18:80:bd:f6/00:00:00:00:00/40 tag 3 ncq 69632 in
[ 9441.677862] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 9441.677865] ata8.00: status: { DRDY }
[ 9441.677869] ata8: hard resetting link
[ 9442.163191] ata8: SATA link up 6.0 Gbps (SStatus 133 SControl 370)
[ 9442.184717] ata8.00: configured for UDMA/133
[ 9442.185156] ata8.00: device reported invalid CHS sector 0
[ 9442.185160] ata8.00: device reported invalid CHS sector 0
[ 9442.185163] ata8.00: device reported invalid CHS sector 0
[ 9442.185166] ata8.00: device reported invalid CHS sector 0
[ 9442.185174] ata8: EH complete
I've tried updating the Marvell controller's firmware (http://www.station-drivers.com/page/marvell.htm), but the mobo keeps reverting it back. At this point I'm not really sure how much of this is the controller's fault or if its something in Linux. Any idea?
Offline