From: "H. Peter Anvin" <hpa@zytor.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: 2.5.49: Severe PIIX4/ATA filesystem corruption
Date: Tue, 26 Nov 2002 16:36:30 -0800 [thread overview]
Message-ID: <3DE4138E.8060600@zytor.com> (raw)
In-Reply-To: 1038359021.3267.110.camel@irongate.swansea.linux.org.uk
Alan Cox wrote:
>
> The base 2.5.47/8/9 Linus tree PIIX code has had no corruption reports
> (except someone whose box failed memtest86) and its about the most
> tested IDE controller.
>
> I would be interested to know what happens if you boot a base 2.5.49
> without raid6 adulteration and stress it on your hw there, just to be
> sure.
>
I will try it once the system gets put back together, which will be in
about two weeks (we're moving, and today was computer teardown day.)
All I have ATM is my laptop, which I won't be running experimental stuff
on :-/
-hpa
next prev parent reply other threads:[~2002-11-27 0:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-26 21:07 2.5.49: Severe PIIX4/ATA filesystem corruption H. Peter Anvin
2002-11-27 0:32 ` Alan Cox
2002-11-27 0:13 ` H. Peter Anvin
2002-11-27 1:03 ` Alan Cox
2002-11-27 0:36 ` H. Peter Anvin [this message]
2002-12-17 20:41 ` H. Peter Anvin
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=3DE4138E.8060600@zytor.com \
--to=hpa@zytor.com \
--cc=alan@lxorguk.ukuu.org.uk \
--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.