From: Ville Herva <vherva@mail.niksula.cs.hut.fi>
To: "Stephen C. Tweedie" <sct@redhat.com>
Cc: ext3-users@redhat.com, linux-kernel@vger.kernel.org,
Florian Lohoff <flo@rfc822.org>
Subject: Re: Oops in iput
Date: Tue, 26 Jun 2001 14:07:42 +0300 [thread overview]
Message-ID: <20010626140742.V1503@niksula.cs.hut.fi> (raw)
In-Reply-To: <20010625201612.A701@paradigm.rfc822.org> <20010625194213.J18856@redhat.com> <20010626110933.R1503@niksula.cs.hut.fi> <20010626115651.A9176@redhat.com>
In-Reply-To: <20010626115651.A9176@redhat.com>; from sct@redhat.com on Tue, Jun 26, 2001 at 11:56:51AM +0100
On Tue, Jun 26, 2001 at 11:56:51AM +0100, you [Stephen C. Tweedie] claimed:
> Hi,
>
> On Tue, Jun 26, 2001 at 11:09:33AM +0300, Ville Herva wrote:
>
> > Well, I for one use the 2.2 ide patches extensively (on almost all of my
> > machines, including a heavy-duty backup server)
>
> It is highly hardware-dependent. A huge amount of effort was spent
> early in 2.4 getting blacklists and hardware tweaks right to work
> around problems with specific chipsets with ide udma. Just because it
> works for one person doesn't give you any confidence that it won't
> trash data for somebody else.
Well, the report said 'Intel BX chipset' - that's as solid as chipsets get
(to loosely quote Alan). Almost all of my boxes are BX (one has HPT366 in
addition, and another one was changed to Via686a recently), and I imagine
that BX gets most testing since it is very common chipset. Moreover, it only
does UDMA33, not any fancy 66 or 100 stuff (although I haven't had problems
with those either on HPT366, HPT370 nor 686a).
As said, it could be the ide patch, but surely there are other just as
likely suspects as well.
-- v --
v@iki.fi
next prev parent reply other threads:[~2001-06-26 11:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-25 18:16 Florian Lohoff
2001-06-25 18:42 ` Stephen C. Tweedie
2001-06-26 8:09 ` Ville Herva
2001-06-26 10:56 ` Stephen C. Tweedie
2001-06-26 11:07 ` Ville Herva [this message]
2001-06-26 14:10 ` Florian Lohoff
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=20010626140742.V1503@niksula.cs.hut.fi \
--to=vherva@mail.niksula.cs.hut.fi \
--cc=ext3-users@redhat.com \
--cc=flo@rfc822.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sct@redhat.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
all inboxes | Powered by JetHome®