[Bug 323302] Re: Wrong UDMA mode due to error in 40/80 wire cable detection

[biebel]

This has been a problem for me for some time.

If someone does open a new report for this bug, please add this info:

Workaround that works for me since the introduction of the bug: add
libata.force=80c as kernel parameter.

As I don't have any 40-wire cables nor udma  < 66 devices this
workaround has never caused a problem for me.

dmesg output without the parameter;
[    1.880262] ata4.00: ATAPI: TSSTcorp CDDVDW SH-S222L, SB00, max UDMA/66
[    1.880292] ata4: nv_mode_filter: 0x1f39f&0x1f39f->0x1f39f, BIOS=0x1f000 (0xc7c7c500) ACPI=0x1f01f (30:600:0x13)
[    1.880296] ata4.00: limited to UDMA/33 due to 40-wire cable
[    1.920202] ata4.00: configured for UDMA/33

dmesg output with the parameter:
[    1.950236] ata4: FORCE: cable set to 80c
[    1.950288] ata4.00: ATAPI: TSSTcorp CDDVDW SH-S222L, SB00, max UDMA/66
[    1.950348] ata4: nv_mode_filter: 0x1f39f&0x1f39f->0x1f39f, BIOS=0x1f000 (0xc7c7c500) ACPI=0x1f01f (30:600:0x13)
[    1.981205] ata4.00: configured for UDMA/66

-- 
Wrong UDMA mode due to error in 40/80 wire cable detection
https://bugs.launchpad.net/bugs/323302
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to linux in ubuntu.