External eSATA drive downgraded to 1.5Gbs

[Konstantin Svist]

On 10/24/2009 05:12 AM, Andy Campbell wrote:
> I've noticed that an external eSATA drive I use for backups
> gets downgraded to 1.5Gbs, with errors when I boot.
>
> + I'm running Fedora 11 (64bit ).
> + The eSATA port is from a JMicron JMB361, which is also used
>    for two PATA DVD drives -  if that makes any difference.
> + The drive is an Icy Box - Ib-390stus-b enclosure.
> + In the BIOS, I've select AHCI.
> + I've tried booting with noapic acpi=off
> + The drive seems to work fine at 1.5GBps, but I'd
>    rather have the full speed its capable off.
>
>
> Any ideas on the meaning of the errors ...
>
> [trantor] ~ $dmesg | grep ata7
>
> ata7: SATA max UDMA/133 abar m8192 at 0xfeafe000 port 0xfeafe100 irq 10
> ata7: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> ata7.00: ATA-8: WDC WD10EACS-00D6B1, 01.01A01, max UDMA/133
> ata7.00: 1953525168 sectors, multi 0: LBA48 NCQ (depth 31/32)
>   sda:<6>ata7.00: configured for UDMA/133
>   sde:<3>ata7.00: exception Emask 0x10 SAct 0x1 SErr 0x780100 action 0x6
> ata7.00: irq_stat 0x08000000
>
> ata7: SError: { UnrecovData 10B8B Dispar BadCRC Handshk }
> ata7.00: cmd 60/08:00:00:00:00/00:00:00:00:00/40 tag 0 ncq 4096 in
> ata7.00: status: { DRDY }
> ata7: hard resetting link
>
> ata7: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> ata7.00: failed to IDENTIFY (I/O error, err_mask=0x100)
> ata7.00: revalidation failed (errno=-5)
> ata7: hard resetting link
>
> ata7: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> ata7.00: configured for UDMA/133
> ata7: EH complete
>
> ata7: limiting SATA link speed to 1.5 Gbps
> ata7.00: exception Emask 0x10 SAct 0x1 SErr 0x780100 action 0x6
> ata7.00: irq_stat 0x08000000
> ata7: SError: { UnrecovData 10B8B Dispar BadCRC Handshk }
> ata7.00: cmd 60/08:00:00:00:00/00:00:00:00:00/40 tag 0 ncq 4096 in
> ata7.00: status: { DRDY }
> ata7: hard resetting link
>
> ata7: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
> ata7.00: configured for UDMA/133
> ata7: EH complete
>
>
> Thanks
> Andy
>


I've seen this error come up many times on my servers and I've seen 
other people asking about it on this list -- but there are never any 
answers.
I think it's time to ask on kernel list, maybe they can tell us something.