On 10-08-21 02:52 PM, Nicolas Jungers wrote:
My arm box doesn't succeed to use my esata port multiplier (addonics sil3726 based). It was working well with 2.6.34.1 and 2.6.34.4 but not with both 2.6.35.2 and 2.6.35.3. I haven't test other kernels. The kernels are from http://sheeva.with-linux.com/sheeva/ with for example the following config http://sheeva.with-linux.com/sheeva/2.6.35.3/sheeva-2.6.35.3.config The symptoms are in the console a loop on the esata links. Here is the start of it: ata2: exception Emask 0x10 SAct 0x0 SErr 0x4010000 action 0xe frozen ata2: edma_err_cause=00000010 pp_flags=00000000, dev connect ata2: SError: { PHYRdyChg DevExch } ata2: hard resetting link ata2: SATA link up 3.0 Gbps (SStatus 123 SControl F300) ata2.15: Port Multiplier 1.1, 0x1095:0x3726 r23, 6 ports, feat 0x1/0x9 ata2.00: hard resetting link ata2.01: hard resetting link ata2.02: hard resetting link ata2.03: hard resetting link ata2.04: hard resetting link ata2.05: hard resetting link ata2.00: qc timeout (cmd 0xec) ata2.00: failed to IDENTIFY (I/O error, err_mask=0x4) ata2.15: hard resetting link ata2.15: SATA link up 3.0 Gbps (SStatus 123 SControl F300) ata2.00: hard resetting link ata2.01: hard resetting link ata2.02: hard resetting link ata2.04: hard resetting link ata2.05: hard resetting link ata2.00: qc timeout (cmd 0xec) ata2.00: failed to IDENTIFY (I/O error, err_mask=0x4) ata2.15: hard resetting link ata2.15: SATA link up 3.0 Gbps (SStatus 123 SControl F300) ata2.00: hard resetting link ata2.01: hard resetting link ata2.02: hard resetting link ata2.03: hard resetting link ata2.04: hard resetting link ata2.05: hard resetting link ata2.00: qc timeout (cmd 0xec) ata2.00: failed to IDENTIFY (I/O error, err_mask=0x4) ata2.00: failed to recover link after 3 tries, disabling ata2.15: hard resetting link ata2.15: SATA link up 3.0 Gbps (SStatus 123 SControl F300)
... From the "edma_err" keyword above, we can deduce that you've got this PM plugged into a Marvell SATA controller of some kind, managed by sata_mv. Care to tell us more? There are various changes in libata in 2.6.34/35 that break sata_mv, particularly for ATAPI drives and any SSDs that support the DSM/TRIM commands. Do either of those two things apply in your case? If so, there are two pending patches which fix them. They were posted to linux-ide this past Thursday, and can also be found as attachments to this bug report: https://bugzilla.kernel.org/show_bug.cgi?id=16434 Cheers -- To unsubscribe from this list: send the line "unsubscribe linux-ide" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
