Re: Is it safe to ignore UDMA BadCRC errors?

[Eric D. Mudama]

On Mon, Dec 29 at 21:24, Florian Schuele wrote:
> i wrote a mail to this list a few days ago.
> i have the same error messages as the above.
> but _only_ with kernel 2.6.0, _not_ with 2.4.20 ...
> thats strange. isnt it?
> after i little traffic on the hd`s the system freezes.

Your error message wasn't the same.

You reported status 0x51 with error code 0x04.  That is the generic
catch-all error message, which usually refers to aborted commands.
Unfortunately, it's tough to know what command the system was
attempting to issue when your drive aborted the command.  There may be
some IDE debugging code you can enable to attempt to find out, but I
don't know exactly how to do that, a linux IDE person will need to
speak up... i'm just a generic IDE person.

The previous poster reported 0x51 with error code 0x80, that is
specifically UDMA CRC errors, and I diagnosed it as such.

--
Eric D. Mudama
edmudama@xxxxxxxxxxxxxxxxxxxxx

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/