Re: [PATCH] sata_via: pcim_iomap_regions() conversion missed BAR5

[Tim Valenzuela <tim@deadlyninja.com>]

[-- Attachment #1: Type: text/plain, Size: 1953 bytes --]

I swapped the drives out and I got identical results, which means the 
problem lies in the driver or the card itself....
I moved the card to a win32 machine to see what the official driver 
would do. It failed on the 2nd sata channel too. So I'm gonna conclude 
its physically broken. Sorry for the trouble.

Tim Valenzuela

Tejun Heo wrote:
> Tim Valenzuela wrote:
>   
>> Good news: This patch does correct the IO access errors.
>> Bad news: The sata driver now performs exactly like previous kernels, my
>> sata3 works, sata4 has IDENTIFY errors.
>>     
>
> The patch doesn't do anything about that problem, so it's expected.
>
>   
>> [   26.927349] ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
>> [   26.961636] ata4.00: ata_hpa_resize 1: sectors = 625142448,
>> hpa_sectors = 625142448
>> [   26.961754] ata4.00: ATA-7: WDC WD3200AAKS-00SBA0, 12.01B01, max
>> UDMA/133
>> [   26.961843] ata4.00: 625142448 sectors, multi 0: LBA48 NCQ (depth 0/32)
>> [   26.979289] ata4.00: failed to IDENTIFY (I/O error, err_mask=0x1)
>> [   26.979376] ata4.00: revalidation failed (errno=-5)
>> [   26.979458] ata4: failed to recover some devices, retrying in 5 secs
>> [   32.451247] ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
>> [   32.475231] ata4.00: failed to IDENTIFY (I/O error, err_mask=0x1)
>> [   32.475317] ata4.00: revalidation failed (errno=-5)
>> [   32.475401] ata4.00: limiting speed to UDMA/133:PIO3
>> [   32.475483] ata4: failed to recover some devices, retrying in 5 secs
>> [   37.947188] ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
>> [   37.971173] ata4.00: failed to IDENTIFY (I/O error, err_mask=0x1)
>> [   37.971259] ata4.00: revalidation failed (errno=-5)
>> [   37.971341] ata4.00: disabled
>>     
>
> Can you swap the two disks and see what happens?  It seems the second
> IDENTIFY after configuring transfer mode fails.  I'm curious whether
> that's caused by the disk or the controller.
>
>   


[-- Attachment #2: in_windows_too.png --]
[-- Type: image/png, Size: 30004 bytes --]