From: Alan Cox <alan@redhat.com>
To: John Bradford <john@grabjohn.com>
Cc: Jonathan Kamens <jik@kamens.brookline.ma.us>,
linux-kernel@vger.kernel.org, alan@redhat.com
Subject: Re: Updated on UDMA BadCRC errors + subsequent problems (was: Is it safe to ignore UDMA BadCRC errors?)
Date: Fri, 16 Jan 2004 15:52:36 -0500 [thread overview]
Message-ID: <20040116205236.GI9648@devserv.devel.redhat.com> (raw)
In-Reply-To: <200401161648.i0GGmYlJ002181@81-2-122-30.bradfords.org.uk>
On Fri, Jan 16, 2004 at 04:48:34PM +0000, John Bradford wrote:
> I _think_ that UDMA CRC checking is only done on data transfers, not
> commands. I've CC'ed Alan in the hope of getting some confirmation on
> this. Maybe a command being corrupted on the wire could theoretically
> cause that error.
You are correct for PATA but the situation there is very very unlikely,
let alone for it to be repeatable
next prev parent reply other threads:[~2004-01-16 20:53 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
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 [this message]
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=20040116205236.GI9648@devserv.devel.redhat.com \
--to=alan@redhat.com \
--cc=jik@kamens.brookline.ma.us \
--cc=john@grabjohn.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.