Comment 46 for bug 198871

--------------------------------------------------------------------------------------------------------------------
Temporary Solution?
--------------------------------------------------------------------------------------------------------------------

I think I have a possible temporary solution...

* Limit your eSATA drives on JBM363 controllers to 1.5Gbps operatiton (via a jumper on Seagate drives)
* Plug the drive into the eSATA port, dmesg | tail should show it being detected

--------------------------------------------------------------------------------------------------------------------
Background...
--------------------------------------------------------------------------------------------------------------------

Hey everyone, I think I have a temporary solution... I'm not sure if this can be fixed in software or not?

Anyway... I have an ASUS P5K Deluxe with JMB363 on Ubuntu 9.04 64-bit (2.6.28-17-generic). Previously on this installation I had a Gigabyte P35 DQ6 which also used the JBM363, there were no problems with eSATA on the DQ6 board.

With the P5K however, eSATA does not work:

> dmesg | tail

--------------------------------------------------------------------------------------------------------------
[ 113.233690] ata7: exception Emask 0x10 SAct 0x0 SErr 0x4050000 action 0xe frozen
[ 113.233694] ata7: irq_stat 0x00000040, connection status changed
[ 113.233697] ata7: SError: { PHYRdyChg CommWake DevExch }
[ 113.233702] ata7: hard resetting link
[ 119.160019] ata7: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 119.160025] ata7: link online but device misclassified, retrying
[ 119.160027] ata7: reset failed (errno=-11), retrying in 5 secs
[ 123.232014] ata7: hard resetting link
[ 113.233694] ata7: irq_stat 0x00000040, connection status changed
[ 113.233697] ata7: SError: { PHYRdyChg CommWake DevExch }
[ 113.233702] ata7: hard resetting link
[ 119.160019] ata7: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 119.160025] ata7: link online but device misclassified, retrying
[ 119.160027] ata7: reset failed (errno=-11), retrying in 5 secs
[ 123.232014] ata7: hard resetting link
[ 129.160022] ata7: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 129.160028] ata7: link online but device misclassified, retrying
[ 129.160030] ata7: reset failed (errno=-11), retrying in 5 secs
[ 139.164032] ata7: reset failed (errno=-11), retrying in 30 secs
[ 168.232009] ata7: limiting SATA link speed to 1.5 Gbps
[ 168.232013] ata7: hard resetting link
--------------------------------------------------------------------------------------------------------------

After much head scratching and confusion, I decided to try limiting the drive (a 750GB Seagate 7200.11) to SATA-I speeds via its onboard jumper. I then connected the drive... lo and behold, IT WORKED!

> dmesg | tail

--------------------------------------------------------------------------------------------------------------
[61622.384301] sd 7:0:0:0: [sdk] Attached SCSI disk
[61622.384366] sd 7:0:0:0: Attached scsi generic sg11 type 0
[61622.355200] sd 7:0:0:0: [sdk] Write Protect is off
[61622.355202] sd 7:0:0:0: [sdk] Mode Sense: 00 3a 00 00
[61622.355225] sd 7:0:0:0: [sdk] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[61622.355297] sd 7:0:0:0: [sdk] 1465149168 512-byte hardware sectors: (750 GB/698 GiB)
[61622.355434] sd 7:0:0:0: [sdk] Write Protect is off
[61622.355436] sd 7:0:0:0: [sdk] Mode Sense: 00 3a 00 00
[61622.355638] sd 7:0:0:0: [sdk] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[61622.355642] sdk: sdk1
--------------------------------------------------------------------------------------------------------------

And hey, the drive NOW WORKS! So yeah - not sure what this means for those involved in fixing this bug - but for us end users, at least some kind of solution exists... even if it is annoying (adding/removing jumpers sucks)...