public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rogier Wolff <R.E.Wolff@BitWizard.nl>
To: Peter <sw98234@hotmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: wrt: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Date: Sun, 27 Aug 2006 09:11:31 +0200	[thread overview]
Message-ID: <20060827071131.GC6932@bitwizard.nl> (raw)
In-Reply-To: <ecpru4$9t3$1@sea.gmane.org>

On Sat, Aug 26, 2006 at 04:12:52PM +0000, Peter wrote:
> Diagnostics on the drives are fine. Removing the b drive removes the
> messages. System functions fine anyway, and no data is lost as a result
> of the errors. The persistence of it is frustrating!

What diagnostics did you try? 

(I've got experience with a guy saying: "I have 5 which test perfect
with my diagnostics, but my embedded machine refuses them. What's
wrong?" All of them report through SMART that they HAVE reported media
errors, and they all have bad blocks.)

Do you have "smartd" running? I vaguely remember that it sometimes
triggered error messages from the normal driver. 

	Roger. 

-- 
** R.E.Wolff@BitWizard.nl ** http://www.BitWizard.nl/ ** +31-15-2600998 **
*-- BitWizard writes Linux device drivers for any device you may have! --*
Q: It doesn't work. A: Look buddy, doesn't work is an ambiguous statement. 
Does it sit on the couch all day? Is it unemployed? Please be specific! 
Define 'it' and what it isn't doing. --------- Adapted from lxrbot FAQ

  parent reply	other threads:[~2006-08-27  7:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-26 16:12 wrt: dma_intr: status=0x51 { DriveReady SeekComplete Error } Peter
2006-08-26 17:41 ` Peter
2006-08-26 22:46 ` Alan Cox
2006-08-27  7:11 ` Rogier Wolff [this message]
2006-08-27 10:49   ` Peter
2006-08-27 17:44 ` RESOLVED: " Peter

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=20060827071131.GC6932@bitwizard.nl \
    --to=r.e.wolff@bitwizard.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sw98234@hotmail.com \
    /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