From: Rogier Wolff <R.E.Wolff@BitWizard.nl>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Eric Bickle <ebickle@healthspace.ca>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Problem: IDE data corruption with VIA chipsets on2.4.20-19.8+others
Date: Fri, 12 Sep 2003 10:14:54 +0200 [thread overview]
Message-ID: <20030912101454.A17364@bitwizard.nl> (raw)
In-Reply-To: <1063305812.3606.4.camel@dhcp23.swansea.linux.org.uk>
On Thu, Sep 11, 2003 at 07:43:33PM +0100, Alan Cox wrote:
> On Iau, 2003-09-11 at 19:20, Eric Bickle wrote:
> > > > kernel: hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error }
> > > > kernel: hdc: dma_intr: error=0x40 { UncorrectableError },
> > LBAsect=150637065,
> > > > sector=150636992
> A test that rewrites such a sector will generally clear the error, its
> one of the problems of some diagnostic tools. A pure read test should
> fine the error again unless its something like overheat causing the
> problem. SMART data will tell you drive temperatures
Some drives don't have the sensor for that. :-(
Anyway, speaking about SMART, some "smartd" was interfering with
normal operation on one of our systems and we saw similar "nasty"
stuff on that system until I removed "smartd".
Aug 10 06:54:25 falbala kernel: hda: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
Aug 10 06:54:25 falbala kernel: hda: drive_cmd: error=0x04 { DriveStatusError }
Aug 10 06:54:25 falbala kernel: hdb: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
Aug 10 06:54:25 falbala kernel: hdb: drive_cmd: error=0x04 { DriveStatusError }
Aug 10 07:24:25 falbala kernel: hda: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
Aug 10 07:24:25 falbala kernel: hda: drive_cmd: error=0x04 { DriveStatusError }
Aug 10 07:24:25 falbala kernel: hdb: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
Aug 10 07:24:25 falbala kernel: hdb: drive_cmd: error=0x04 { DriveStatusError }
Aug 10 08:24:25 falbala kernel: hda: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
Aug 10 08:24:25 falbala kernel: hda: drive_cmd: error=0x04 { DriveStatusError }
Aug 10 08:24:25 falbala kernel: hdb: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
Aug 10 08:24:25 falbala kernel: hdb: drive_cmd: error=0x04 { DriveStatusError }
Linux version 2.4.19-rc1 (root@zurix) (gcc version 2.95.4 20011002 (Debian prerelease)) #1 Mon Jul 8 15:37:19 CEST 2002
Roger.
--
** R.E.Wolff@BitWizard.nl ** http://www.BitWizard.nl/ ** +31-15-2600998 **
*-- BitWizard writes Linux device drivers for any device you may have! --*
**** "Linux is like a wigwam - no windows, no gates, apache inside!" ****
next prev parent reply other threads:[~2003-09-12 8:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-11 18:20 Problem: IDE data corruption with VIA chipsets on2.4.20-19.8+others Eric Bickle
2003-09-11 18:43 ` Alan Cox
2003-09-12 8:14 ` Rogier Wolff [this message]
2003-09-12 10:44 ` Alan Cox
2003-09-13 4:48 ` Problem: IDE data corruption with VIA chipsets Resident Boxholder
2003-09-13 17:04 ` Alan Cox
-- strict thread matches above, loose matches on Subject: below --
2003-09-11 19:11 Problem: IDE data corruption with VIA chipsets on2.4.20-19.8+others Eric Bickle
2003-09-12 11:19 Roman Kagan
2003-09-12 11:45 John Bradford
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=20030912101454.A17364@bitwizard.nl \
--to=r.e.wolff@bitwizard.nl \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=ebickle@healthspace.ca \
--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.