Tejun Heo writes:
> No, none is related to m15w. It seems that your drive is failing some
> commands w/ ID not found error, which might be a media problem.
> Anyways, libata is having problem recovering from the error condition
> and retrying the command, thus the catastrophe.
>
>> So far I've upgraded the BIOS to the latest from Abit, which
>> includes a more recent SATA BIOS from Silicon Image, and fiddled with
>> some of the BIOS settings - particularly changing Ext-P2P Discard from
>> 30us to 1ms, as suggested in a much older NVIDIA/Abit bug dialogue. I
>> don't know if any of this is actually helping yet, though.
>
> I'm skeptical.
>
> Can you try 2.6.18-rc5? Latest libata has much improved error handling.
> If the error your drive is reporting are transient, new libata EH
> should be able to recover from most of them and, even if not, it will
> help diagnosing the problem.
Unfortunately, Fedora hasn't packaged up the 2.6.18 kernels, and
this is not yet a bad enough problem yet to motivate me to build my own.
BIOS adjustments and updates may have worked around the problem - it
hasn't happened again since doing them. If not I'll just back off on
using this drive until I can get a 2.6.18 kernel. I was hoping this was
a well-known problem :-(
Thanks!
Jon
-
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
