public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Eric D. Mudama" <edmudama@mail.bounceswoosh.org>
To: linux-kernel@vger.kernel.org
Subject: Re: Is it safe to ignore UDMA BadCRC errors?
Date: Tue, 30 Dec 2003 13:06:43 -0700	[thread overview]
Message-ID: <20031230200643.GC6992@bounceswoosh.org> (raw)
In-Reply-To: <16369.25514.425834.153361@jik.kamens.brookline.ma.us>

On Tue, Dec 30 at  6:38, Jonathan Kamens wrote:
>I replaced the cable with a brand new one and I'm still getting the
>CRC errors.  What now?

Do you know if you're doing reads or writes when the errors occur?

What motherboard/chipset are you using with this drive?

Is the environment especially warm?

-- 
Eric D. Mudama
edmudama@mail.bounceswoosh.org


  reply	other threads:[~2003-12-30 20:05 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 [this message]
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=20031230200643.GC6992@bounceswoosh.org \
    --to=edmudama@mail.bounceswoosh.org \
    --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