From: Florian Lohoff <flo@rfc822.org>
To: ext3-users@redhat.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: Oops in iput
Date: Tue, 26 Jun 2001 16:10:49 +0200 [thread overview]
Message-ID: <20010626161049.C1425@paradigm.rfc822.org> (raw)
In-Reply-To: <20010625201612.A701@paradigm.rfc822.org> <20010625194213.J18856@redhat.com> <20010626110933.R1503@niksula.cs.hut.fi>
In-Reply-To: <20010626110933.R1503@niksula.cs.hut.fi>; from vherva@mail.niksula.cs.hut.fi on Tue, Jun 26, 2001 at 11:09:33AM +0300
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), and haven't seen any
> problems whatsoever. I see _much_ more problems with scsi (aic7xxx), for
> example.
I have been using the udma ide patches for a long time and as long as
you stay away from known buggy drives controllers you are fine.
BTW: The machine i reported the bug for is mostly running on SCSI - Only
/var/tmp is an large IDE drive.
> I don't mean to say the ide patches are 100% bug free, but I wouldn't
> consider them as the prime suspect for an oops that happened elsewhere
> either. It could be hw or any other part of kernel just as well... What
> about memtest86?
I'll try
Flo
--
Florian Lohoff flo@rfc822.org +49-5201-669912
Why is it called "common sense" when nobody seems to have any?
prev parent reply other threads:[~2001-06-26 14:11 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
2001-06-26 14:10 ` Florian Lohoff [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=20010626161049.C1425@paradigm.rfc822.org \
--to=flo@rfc822.org \
--cc=ext3-users@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
all inboxes | Powered by JetHome®