Jeff Garzik wrote:
Mark Lord wrote:
..
I triggered this by accident, issuing an IDENTIFY command
which incorrectly specified ATA_PROT_NODATA. My error, for sure,
but libata never recovered from the "stuck DRQ bit" that resulted.
..
Maybe we do need to recover from a stuck DRQ bit, but I'll wait until
that symptom shows up with a different catalyst.
It's a failure mode that occurs very often (as far as failures go)
with the IDE driver. *Lots* of occurance.
So as more things migrate to libata, we'll eventually have to deal
with it here, too. I'm just trying to give us a chance to fix it
before somebody loses data over it.
Actually, I'm not so sure that this problem hasn't *already* been
posted to this very mailing list.
http://lkml.org/lkml/2006/10/1/264
http://www.mail-archive.com/linux-ide@xxxxxxxxxxxxxxx/msg05078.html
...
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
