Re: Failure with SATA DVD-RW

On Thu, 6 Dec 2007 01:33:16 +0000 (UTC)
Parag Warudkar [off-list ref] wrote:

Tom Lanyon <tomlanyon <at> gmail.com> writes:

quoted

scsi4: ahci
ata5: SATA link up at 1.5 Gbps (SStatus 113 SControl 300)
ata5.00: ATAPI, max UDMA/66
ata5.00: qc timeout (cmd 0xef)
ata5.00: failed to set xfermode (err_mask=0x104)
ata5.00: limiting speed to UDMA/44
ata5: failed to recover some devices, retrying in 5 secs
ata5: port is slow to respond, please be patient (Status 0x80)
ata5: port failed to respond (30 secs, status 0x80)
ata5: COMRESET failed (device not ready)
ata5: hardreset failed, retrying in 5 secs
ata5: SATA link up at 1.5 Gbps (SStatus 113 SControl 300)
ata5.00: ATAPI, max UDMA/66
ata5.00: qc timeout (cmd 0xef)
ata5.00: failed to set xfermode (err_mask=0x104)
ata5.00: limiting speed to PIO0
ata5: failed to recover some devices, retrying in 5 secs
ata5: port is slow to respond, please be patient (Status 0x80)
ata5: port failed to respond (30 secs, status 0x80)
ata5: COMRESET failed (device not ready)
ata5: hardreset failed, retrying in 5 secs
ata5.00: ATAPI, max UDMA/66
ata5.00: qc timeout (cmd 0xef)
ata5.00: failed to set xfermode (err_mask=0x104)
ata5.00: disabled

Looks like it is trying to set transfer mode to UDMA/66 and failing. After 
that it tried UDMA/44 and failed again. Next UDMA/66 again with unsurprising 
result - failed. After that PIO0 which seems to cause some kind of trouble, 
then it tries UDMA/66 again, and I am not stating the result again :) ! 

quoted

Any ideas what to try to get it working under AHCI?

I recall reading somewhere - the Pioneer drive needs UDMA/33 which it did not 
try in your case - need to some how have it try UDMA/33 but I don't find a 
boot parameter which will do that. So may be adding a quirk for this device to 
limit the xfer mode to 33 may work. 

What does your dmesg output for the drives look like when you run in IDE 
compat mode? (Particularly the DMA for this drive?)

Please cc linux-ide on sata, pata and ide-related issues.

If nothing happens within a few days please raise a report at
bugzilla.kernel.org so we can ignore this in an organised fashion, thanks.