From: Alan on
Does anyone know the status of the SIIG DP SATA 6Gb/s 2S1P PCIe (Part
number: SC-SA0E12-S1)?

I am encountering problems writing a large quantity through this
controller and I want to see if there is a way to fix this. The pci ids
do not appear to be referenced in the kernel.

Are any of the siig sata controllers supported? Is there some issue with
them supporting Linux that I am not aware of?

Here is the lspci data:

05:00.0 SATA controller: Device 1b4b:9123 (rev 11) (prog-if 01 [AHCI 1.0])
Subsystem: Device 1b4b:9123
Flags: bus master, fast devsel, latency 0, IRQ 30
I/O ports at dc00 [size=8]
I/O ports at d880 [size=4]
I/O ports at d800 [size=8]
I/O ports at d480 [size=4]
I/O ports at d400 [size=16]
Memory at f9fff800 (32-bit, non-prefetchable) [size=2K]
Expansion ROM at f9fe0000 [disabled] [size=64K]
Capabilities: <access denied>
Kernel driver in use: ahci

05:00.1 IDE interface: Device 1b4b:91a4 (rev 11) (prog-if 8f [Master SecP
SecO PriP PriO])
Subsystem: Device 1b4b:91a4
Flags: fast devsel, IRQ 18
I/O ports at d080 [size=8]
I/O ports at d000 [size=4]
I/O ports at cc00 [size=8]
I/O ports at c880 [size=4]
I/O ports at c800 [size=16]
Memory at f9fff400 (32-bit, non-prefetchable) [size=16]
Expansion ROM at f9fd0000 [disabled] [size=64K]
Capabilities: <access denied>
Kernel modules: ata_generic, pata_acpi

Thanks!

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
From: Jeff Garzik on
On 06/10/2010 12:39 AM, Alan wrote:
> Does anyone know the status of the SIIG DP SATA 6Gb/s 2S1P PCIe (Part
> number: SC-SA0E12-S1)?
>
> I am encountering problems writing a large quantity through this
> controller and I want to see if there is a way to fix this. The pci ids
> do not appear to be referenced in the kernel.
>
> Are any of the siig sata controllers supported? Is there some issue with
> them supporting Linux that I am not aware of?
>
> Here is the lspci data:
>
> 05:00.0 SATA controller: Device 1b4b:9123 (rev 11) (prog-if 01 [AHCI 1.0])
> Subsystem: Device 1b4b:9123
> Flags: bus master, fast devsel, latency 0, IRQ 30
> I/O ports at dc00 [size=8]
> I/O ports at d880 [size=4]
> I/O ports at d800 [size=8]
> I/O ports at d480 [size=4]
> I/O ports at d400 [size=16]
> Memory at f9fff800 (32-bit, non-prefetchable) [size=2K]
> Expansion ROM at f9fe0000 [disabled] [size=64K]
> Capabilities:<access denied>
> Kernel driver in use: ahci

What issues are you seeing?

The 'ahci' driver is aware of this controller...

Jeff



--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
From: alan on
On Thu, 10 Jun 2010, Jeff Garzik wrote:

> On 06/10/2010 12:39 AM, Alan wrote:
>> Does anyone know the status of the SIIG DP SATA 6Gb/s 2S1P PCIe (Part
>> number: SC-SA0E12-S1)?
>>
>> I am encountering problems writing a large quantity through this
>> controller and I want to see if there is a way to fix this. The pci ids
>> do not appear to be referenced in the kernel.
>>
>> Are any of the siig sata controllers supported? Is there some issue with
>> them supporting Linux that I am not aware of?
>>
>> Here is the lspci data:
>>
>> 05:00.0 SATA controller: Device 1b4b:9123 (rev 11) (prog-if 01 [AHCI 1.0])
>> Subsystem: Device 1b4b:9123
>> Flags: bus master, fast devsel, latency 0, IRQ 30
>> I/O ports at dc00 [size=8]
>> I/O ports at d880 [size=4]
>> I/O ports at d800 [size=8]
>> I/O ports at d480 [size=4]
>> I/O ports at d400 [size=16]
>> Memory at f9fff800 (32-bit, non-prefetchable) [size=2K]
>> Expansion ROM at f9fe0000 [disabled] [size=64K]
>> Capabilities:<access denied>
>> Kernel driver in use: ahci
>
> What issues are you seeing?
>
> The 'ahci' driver is aware of this controller...

If you write a large amount of data to the drive (about 6-8 gigs+) the
drive will error out and disconnect.

I will post the string of error messages when I get home.

--
Truth is stranger than fiction because fiction has to make sense.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
From: Alan on
> On 06/10/2010 12:39 AM, Alan wrote:
>> Does anyone know the status of the SIIG DP SATA 6Gb/s 2S1P PCIe (Part
>> number: SC-SA0E12-S1)?
>>
>> I am encountering problems writing a large quantity through this
>> controller and I want to see if there is a way to fix this. The pci ids
>> do not appear to be referenced in the kernel.
>>
>> Are any of the siig sata controllers supported? Is there some issue with
>> them supporting Linux that I am not aware of?
>>
>> Here is the lspci data:
>>
>> 05:00.0 SATA controller: Device 1b4b:9123 (rev 11) (prog-if 01 [AHCI
>> 1.0])
>> Subsystem: Device 1b4b:9123
>> Flags: bus master, fast devsel, latency 0, IRQ 30
>> I/O ports at dc00 [size=8]
>> I/O ports at d880 [size=4]
>> I/O ports at d800 [size=8]
>> I/O ports at d480 [size=4]
>> I/O ports at d400 [size=16]
>> Memory at f9fff800 (32-bit, non-prefetchable) [size=2K]
>> Expansion ROM at f9fe0000 [disabled] [size=64K]
>> Capabilities:<access denied>
>> Kernel driver in use: ahci
>
> What issues are you seeing?
>
> The 'ahci' driver is aware of this controller...

When writing large amounts of data I see messages like the following:

Jun 8 19:31:46 zowie kernel: ata2.00: exception Emask 0x0 SAct 0x3fffffff
SErr 0x0 action 0x6 frozen
Jun 8 19:31:46 zowie kernel: ata2.00: failed command: WRITE FPDMA QUEUED
Jun 8 19:31:46 zowie kernel: ata2.00: cmd
61/28:00:17:fb:06/00:00:04:00:00/40 tag 0 ncq 20480 out
Jun 8 19:31:46 zowie kernel: res
40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
Jun 8 19:31:46 zowie kernel: ata2.00: status: { DRDY }
Jun 8 19:31:46 zowie kernel: ata2.00: failed command: WRITE FPDMA QUEUED
Jun 8 19:31:46 zowie kernel: ata2.00: cmd
61/20:08:9f:db:06/00:00:04:00:00/40 tag 1 ncq 16384 out
Jun 8 19:31:46 zowie kernel: res
40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Jun 8 19:31:46 zowie kernel: ata2.00: status: { DRDY }
Jun 8 19:31:46 zowie kernel: ata2.00: failed command: WRITE FPDMA QUEUED
Jun 8 19:31:46 zowie kernel: ata2.00: cmd
61/28:10:d7:df:06/00:00:04:00:00/40 tag 2 ncq 20480 out
Jun 8 19:31:46 zowie kernel: res
40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Jun 8 19:31:46 zowie kernel: ata2.00: status: { DRDY }
Jun 8 19:31:46 zowie kernel: ata2.00: failed command: WRITE FPDMA QUEUED
Jun 8 19:31:46 zowie kernel: ata2.00: cmd
61/30:18:0f:e4:06/00:00:04:00:00/40 tag 3 ncq 24576 out
Jun 8 19:31:46 zowie kernel: res
40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Jun 8 19:31:46 zowie kernel: ata2.00: status: { DRDY }
Jun 8 19:31:46 zowie kernel: ata2.00: failed command: WRITE FPDMA QUEUED
Jun 8 19:31:46 zowie kernel: ata2.00: cmd
61/28:20:17:fc:06/00:00:04:00:00/40 tag 4 ncq 20480 out
Jun 8 19:31:46 zowie kernel: res
40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Jun 8 19:31:46 zowie kernel: ata2.00: status: { DRDY }
Jun 8 19:31:46 zowie kernel: ata2.00: failed command: WRITE FPDMA QUEUED
Jun 8 19:31:46 zowie kernel: ata2.00: cmd
61/08:28:b7:b7:06/00:00:04:00:00/40 tag 5 ncq 4096 out
Jun 8 19:31:46 zowie kernel: res
40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Jun 8 19:31:46 zowie kernel: ata2.00: status: { DRDY }
Jun 8 19:31:46 zowie kernel: ata2.00: failed command: WRITE FPDMA QUEUED
Jun 8 19:31:46 zowie kernel: ata2.00: cmd
61/20:30:1f:d3:06/00:00:04:00:00/40 tag 6 ncq 16384 out
Jun 8 19:31:46 zowie kernel: res
40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Jun 8 19:31:46 zowie kernel: ata2.00: status: { DRDY }
Jun 8 19:31:46 zowie kernel: ata2.00: failed command: WRITE FPDMA QUEUED

After a bit it does this:

Jun 8 19:31:46 zowie kernel: ata2: hard resetting link
Jun 8 19:31:48 zowie kernel: ata2: SATA link up 1.5 Gbps (SStatus 113
SControl 300)
Jun 8 19:31:53 zowie kernel: ata2.00: qc timeout (cmd 0xec)
Jun 8 19:31:53 zowie kernel: ata2.00: failed to IDENTIFY (I/O error,
err_mask=0x4)
Jun 8 19:31:53 zowie kernel: ata2.00: revalidation failed (errno=-5)
Jun 8 19:31:53 zowie kernel: ata2: hard resetting link
Jun 8 19:31:54 zowie kernel: ata2: SATA link up 1.5 Gbps (SStatus 113
SControl 300)
Jun 8 19:32:04 zowie kernel: ata2.00: qc timeout (cmd 0xec)
Jun 8 19:32:05 zowie kernel: ata2.00: failed to IDENTIFY (I/O error,
err_mask=0x4)
Jun 8 19:32:05 zowie kernel: ata2.00: revalidation failed (errno=-5)
Jun 8 19:32:05 zowie kernel: ata2: limiting SATA link speed to 1.5 Gbps
Jun 8 19:32:05 zowie kernel: ata2: hard resetting link
Jun 8 19:32:05 zowie kernel: ata2: SATA link up 1.5 Gbps (SStatus 113
SControl 310)
Jun 8 19:32:35 zowie kernel: ata2.00: qc timeout (cmd 0xec)
Jun 8 19:32:36 zowie kernel: ata2.00: failed to IDENTIFY (I/O error,
err_mask=0x4)
Jun 8 19:32:36 zowie kernel: ata2.00: revalidation failed (errno=-5)
Jun 8 19:32:36 zowie kernel: ata2.00: disabled
Jun 8 19:32:36 zowie kernel: ata2.00: device reported invalid CHS sector 0
Jun 8 19:32:36 zowie kernel: ata2.00: device reported invalid CHS sector 0
Jun 8 19:32:36 zowie kernel: ata2.00: device reported invalid CHS sector 0
Jun 8 19:32:36 zowie kernel: ata2.00: device reported invalid CHS sector 0

The drive goes into a read only state at this point.

It does not matter what drive I put on the controller. The controller has
been replaced once already.

Double-plus ungood.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
From: Rogier Wolff on
On Thu, Jun 10, 2010 at 07:08:43PM -0700, Alan wrote:
> When writing large amounts of data I see messages like the following:

yeah! I'm trying to write some 2.5Tb to my raid array, where 2 of 8
disks are connected to an Asus U3S6 board.
http://www.asus.com/product.aspx?P_ID=lGYmelQ8mJvPtYTv

After a while, those two disks bomb out, and make the raid
inaccessible.

A reboot brings the disks back to life. So in theory, Linux should be
able to restore life into these drives by doing the right magic with
the hardware bits...

I'm running 2.6.34:

Linux version 2.6.34 (root(a)zebigbos) (gcc version 3.4.2) #3 SMP Mon May 17 21:04:13 CEST 2010


Log file entries:

ata5.00: exception Emask 0x0 SAct 0xfff SErr 0x0 action 0x6 frozen
ata5.00: failed command: READ FPDMA QUEUED
ata5.00: cmd 60/a8:00:f6:12:10/00:00:0d:00:00/40 tag 0 ncq 86016 in
res 40/00:14:ee:98:bb/00:00:0a:00:00/40 Emask 0x4 (timeout)
ata5.00: status: { DRDY }
....
ata5.00: failed command: READ FPDMA QUEUED
ata5.00: cmd 60/a0:58:ee:19:10/00:00:0d:00:00/40 tag 11 ncq 81920 in
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
ata5.00: status: { DRDY }
ata5: hard resetting link
ata5: SATA link up 3.0 Gbps (SStatus 123 SControl 370)
ata5.00: configured for UDMA/133
ata5.00: device reported invalid CHS sector 0
*last message repeated 10 times
ata5: EH complete

(all tags 1...10 are aalso listed.)

This seems "harmless", it happend a few times the last hour or so
(during the rebuild).

When things went bad last time I got:

one of these "harmless events" (but this time with 31 tags listed!):

Jun 14 18:26:23 vercingetorix kernel: ata5: SATA link up 3.0 Gbps (SStatus 123 SControl 370)

and then 5 seconds later:

ata5.00: qc timeout (cmd 0xec)
ata5.00: failed to IDENTIFY (I/O error, err_mask=0x4)
ata5.00: revalidation failed (errno=-5)
ata5: hard resetting link
ata5: SATA link up 3.0 Gbps (SStatus 123 SControl 370)
ata5.00: qc timeout (cmd 0xec)
ata5.00: failed to IDENTIFY (I/O error, err_mask=0x4)


Roger.

--
** R.E.Wolff(a)BitWizard.nl ** http://www.BitWizard.nl/ ** +31-15-2600998 **
** Delftechpark 26 2628 XH Delft, The Netherlands. KVK: 27239233 **
*-- BitWizard writes Linux device drivers for any device you may have! --*
Q: It doesn't work. A: Look buddy, doesn't work is an ambiguous statement.
Does it sit on the couch all day? Is it unemployed? Please be specific!
Define 'it' and what it isn't doing. --------- Adapted from lxrbot FAQ
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/