Daniel Schroeder wrote:
ata3.00: exception Emask 0x0 SAct 0x2ef SErr 0x0 action 0x0
ata3.00: (irq_stat 0x00020002, device error via SDB FIS)
ata3.00: cmd 61/28:30:17:83:68/00:00:1f:00:00/40 tag 6 cdb 0x0 data
20480 out
res 51/04:30:17:83:68/50:04:1f:00:00/40 Emask 0x1 (device error)
Command 0x61 is FPDMA WRITE (NCQ WRITE).
Error 0x04 is 'command aborted'.
Not much the driver can do but follow what the device is telling us...
If you disable NCQ, presumably this should go away.
thanks for your explanation, i will monitor this drive and disable ncq
if it happens again
I should have added: given your report, it sounds like the error
handling code took appropriate action for your error. It should
continue transferring data (though perhaps not in NCQ mode anymore).
HOPEFULLY all you see is a nasty message when the drive complains :)
If that is not the case, if you are seeing data transfer suddenly cease
(or worse, data corruption) please do speak up...
Jeff
-
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
