From: Florian Schuele <schuele@gmx.de>
To: linux-kernel@vger.kernel.org
Subject: Re: Is it safe to ignore UDMA BadCRC errors?
Date: Mon, 29 Dec 2003 21:52:52 +0100 [thread overview]
Message-ID: <20031229205252.GB8418@spacken.de> (raw)
In-Reply-To: <20031229203448.GD27234@bounceswoosh.org>
On 29.12.03 13:34 -0700, Eric D. Mudama wrote:
> 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.
ups, sorry... i was too fast with my post...
>
> 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.
ah, ok perhaps i`ll find a way to debug or someone else who can help.
>
> The previous poster reported 0x51 with error code 0x80, that is
> specifically UDMA CRC errors, and I diagnosed it as such.
>
--
florian schuele
next prev parent reply other threads:[~2003-12-29 20:45 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-29 16:07 Is it safe to ignore UDMA BadCRC errors? Jonathan Kamens
2003-12-29 16:12 ` Jonathan Kamens
2003-12-29 19:52 ` Eric D. Mudama
2003-12-29 20:24 ` Florian Schuele
2003-12-29 20:34 ` Eric D. Mudama
2003-12-29 20:52 ` Florian Schuele [this message]
2003-12-30 11:38 ` Jonathan Kamens
2003-12-30 20:06 ` Eric D. Mudama
2003-12-30 20:11 ` Jonathan Kamens
2003-12-30 20:25 ` Eric D. Mudama
2003-12-30 20:30 ` Jonathan Kamens
2003-12-30 20:48 ` Eric D. Mudama
2003-12-30 20:14 ` Ed Sweetman
2004-01-15 2:21 ` Updated on UDMA BadCRC errors + subsequent problems (was: Is it safe to ignore UDMA BadCRC errors?) Jonathan Kamens
2004-01-16 3:47 ` Jonathan Kamens
2004-01-16 7:47 ` John Bradford
2004-01-16 15:27 ` Jonathan Kamens
2004-01-16 15:46 ` John Bradford
2004-01-16 15:48 ` Jonathan Kamens
2004-01-16 16:48 ` John Bradford
2004-01-16 18:04 ` Jonathan Kamens
2004-01-16 20:52 ` Alan Cox
2004-01-16 16:12 ` Updated on UDMA BadCRC errors + subsequent problems Ed Sweetman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20031229205252.GB8418@spacken.de \
--to=schuele@gmx.de \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox