On Tue, 14 Sep 2004 11:43:36 +0200, Michal 'hramrach' Suchanek
[off-list ref] wrote:

With 2.6.5 I get the same results.

The libata error message:

ata1: DMA timeout, stat 0x0
ATA: abnormal status 0xD0 on prot 0xEC07
scsi0: ERROR on channel 0, id0, lin0, CDB: Write (10) 00 01 65 dc e7 00
00 42 00
Current sda: sense key Medium Error
Additional sense: Write Error - auto reallocation failed
end_request: I/O error, dev sda, sector 23452903
ATA: abnormal status 0xD0 on prot 0xEC07
ATA: abnormal status 0xD0 on prot 0xEC07
ATA: abnormal status 0xD0 on prot 0xEC07

Note that the 0xd0 is the same as the ide DMA timeout error.

Not sure how libata queried the additional sense: key/code/qual etc
from the drive, since it appears to have gotten a busy timeout.

FYI, 0xD0 is simply a 0x50 status (ready/seek complete) + the busy
bit, which is automatically set most by hardware upon receipt of a new
command.  In SATA, this is often set internally in a shadow task file
register, and has nothing to do with physical "registers" on the drive
itself.

Can someone quickie translate that CDB for me into its ATA command?

--eric