From: Samuel Flory <sflory@rackable.com>
To: Alan Cox <alan@redhat.com>
Cc: linux-kernel@vger.kernel.org, B.Zolnierkiewicz@elka.pw.edu.pl
Subject: Re: ICH5-SATA file corruption under 2.4.21-ac1
Date: Mon, 30 Jun 2003 14:58:21 -0700 [thread overview]
Message-ID: <3F00B27D.9060008@rackable.com> (raw)
In-Reply-To: <200306270956.h5R9uH911387@devserv.devel.redhat.com>
Alan Cox wrote:
>> On an Intel winterpark motherboard I'm seeing file corruption when
>>using the onboard SATA interface. The test I'm running is ctcs's new
>>kdiff test which just copies a kernel, diffs it, deletes the tree, and
>>starts over. (Which seems to find file system issues like this pretty
>>quickly.)
>>
>>
>
>Random bit errors. This really doesn't look like an IDE layer problem
>to be honest.
>
>
When I switch out the drive for a pata drive everything works. Same
system, and OS config. This would seem to indicate an issue with the
ide driver.
--
Once you have their hardware. Never give it back.
(The First Rule of Hardware Acquisition)
Sam Flory <sflory@rackable.com>
prev parent reply other threads:[~2003-06-30 21:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-26 22:46 ICH5-SATA file corruption under 2.4.21-ac1 Samuel Flory
2003-06-27 9:56 ` Alan Cox
2003-06-27 10:16 ` Matti Aarnio
2003-06-30 21:58 ` Samuel Flory [this message]
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=3F00B27D.9060008@rackable.com \
--to=sflory@rackable.com \
--cc=B.Zolnierkiewicz@elka.pw.edu.pl \
--cc=alan@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox