Tejun Heo wrote:
Mark Lord wrote:
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
ata1.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 0
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
ata1.00: status: { DRDY }
I wonder if it's just a case of too short a timeout on the cache
flushes?
..
However, in this case the drive is not reporting Busy status at the
timeout, which suggests maybe an interrupt got lost or something.
(Could be still the drive's fault.)
..
If I recall correctly, The reported shadow register contents are bogus
when a timeout occurs. So we don't actually know what the drive state was.
Or do we, Tejun?
Yeah, it's bogus. Maybe we should just report zeros.
Didn't know that. Shouldn't we be able to do a qc_fill_rtf before error
handling in this case? That would make it easier to tell if we lost an
interrupt or if the drive is just taking too long..
--
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
