From: Ville Herva <vherva@mail.niksula.cs.hut.fi>
To: ext3-users@redhat.com, linux-kernel@vger.kernel.org,
Florian Lohoff <flo@rfc822.org>
Subject: Re: Oops in iput
Date: Tue, 26 Jun 2001 11:09:33 +0300 [thread overview]
Message-ID: <20010626110933.R1503@niksula.cs.hut.fi> (raw)
In-Reply-To: <20010625201612.A701@paradigm.rfc822.org> <20010625194213.J18856@redhat.com>
In-Reply-To: <20010625194213.J18856@redhat.com>; from sct@redhat.com on Mon, Jun 25, 2001 at 07:42:13PM +0100
On Mon, Jun 25, 2001 at 07:42:13PM +0100, you [Stephen C. Tweedie] claimed:
> Hi,
>
> On Mon, Jun 25, 2001 at 08:16:12PM +0200, Florian Lohoff wrote:
> >
> > oops in iput - Kernel 2.2.19/i386 + ide-udma patches + ext3 patches (0.0.7a)
>
> The ide-udma patches for 2.2 haven't had nearly the testing of the 2.4
> ones, and simply can't be trusted as a baseline for debugging other
> code. Can you reproduce this problem without them applied? The oops
> here is a networking oops on the face of it, and I wouldn't expect to
> see that on 2.2 unless something was corrupting memory.
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 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?
-- v --
v@iki.fi
next prev parent reply other threads:[~2001-06-26 8:10 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 [this message]
2001-06-26 10:56 ` Stephen C. Tweedie
2001-06-26 11:07 ` Ville Herva
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=20010626110933.R1503@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 \
/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®