Re: excess timeouts accessing pci-sata card both ports

[<drtyc@centrum.cz>]

Hi.

Reproducible with only one disk and one card on one SATA port.
The card has 3 ports. 2 internal, 1 external. The internal closer to the external and the extrenal has the problem.

Just doing cat /dev/disk > /dev/null
or any intensive IO - it happens in less then aprox 30sec.

Or setting raid speed min and max to some high number and do a resync with multiple disks can trigger similar write error.
Anyway got already 6 different cards and all behave similarly plus one of the internal ports is rock solid while the other has problems so I take it as falty design and RMA hoprfully last time now to legaly request money back.
______________________________________________________________
> Od: htejun@gmail.com
> Komu: drtyc@centrum.cz
> CC: linux-ide@vger.kernel.org
> Datum: 02.02.2008 06:11
> Předmět: Re: excess timeouts accessing pci-sata card both ports
>
>drtyc@centrum.cz wrote:
>> Removed 3 drives. Both data and power.
>> Left only port1 connected
>> It's the drive and power cable that in the first test was port2 failing
>> and in second test was port1 and ok
>> both cards plugged in and initialized.
>> third test it's the port1 alone sda working ok
>> fourth test it's the port2 alone sda failing.
>> 
>> any idea what's wrong as this does not seem to be power related
problem.
>> 
>> vanilla 2.6.23.14
>> sata_via module... details in the inlined emails.
>> 
>> (4th test config)
>> ata1: SATA link down (SStatus 0 SControl 310)
>> ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
>> ata4: SATA link down (SStatus 0 SControl 310)
>> ata5: SATA link down (SStatus 0 SControl 310)
>> 
>> Faulty card? Both cards? Driver bug? Or design bug/incompatibility on
second port?
>
>It seems like you're experiencing transmission problems on reads.
>SError value of 0x3000400 is Protocol Error, Link Sequence Error and
>Transport State Transition Error.  Hardresetting the link should usually
>recover from such conditions but error handling on via has never been
>reliable.  How easily can you trigger the problem?
>
>Thanks.
>
>-- 
>tejun
>