Hello, Hans.
Andrew Morton wrote:
since I upgraded to 2.6.24.3 on one of my production systems, I see
regular device resets like these:
Mar 20 14:33:03 lisa5 kernel: ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
Mar 20 14:33:03 lisa5 kernel: ata2.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 0
Mar 20 14:33:03 lisa5 kernel: res 40/00:00:01:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
Ouch, timeout on FLUSH_EXT. Are all errors on cmd ea?
Should I be worried? smartd doesn't show anything suspicious on those.
Can you please post the result of "smartctl -a /dev/sdX"?
It's been 4 samsung drives at all hanging on a sata sil 3124:
FLUSH_EXT timing out usually indicates that the drive is having problem
writing out what it has in its cache to the media. There was one case
where FLUSH_EXT timeout was caused by the driver failing to switch
controller back from NCQ mode before issuing FLUSH_EXT but that was on
sata_nv. There hasn't been any similar problem on sata_sil24.
Thanks.
--
tejun
--
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