From: "Stephen C. Tweedie" <sct@redhat.com>
To: Michael Frank <mhf@linuxmail.org>
Cc: Marcelo Tosatti <marcelo.tosatti@cyclades.com>,
Daniel Fenert <daniel@fenert.net>,
linux-kernel <linux-kernel@vger.kernel.org>,
Michelle Konzack <linux4michelle@freenet.de>,
Stephen Tweedie <sct@redhat.com>
Subject: Re: Is there some bug in ext3 in 2.4.25?
Date: 05 Mar 2004 14:26:56 +0000 [thread overview]
Message-ID: <1078496816.14033.56.camel@sisko.scot.redhat.com> (raw)
In-Reply-To: <opr4d66wct4evsfm@smtp.pacific.net.th>
Hi,
On Fri, 2004-03-05 at 14:14, Michael Frank wrote:
> Although I have nt received a reply from LKML, it is definitively
> a real kernel bug in 2.4.22 which has been fixed in 2.4.24.
>
> Ein weiterer Fehler trat mehrfach in 'exit.c' auf, der ebenfals
> nach der Installation von Linux 2.4.24 verschwunden war.
>
> Further bug occuring several times in 'exit.c' has also vanished
> after installation of 2.4.24.
Sounds like bad memory. It's quite impossible for a bad memory module
to show up a problem in one kernel but not in another, simply because
kernels are storing their active data in slightly different memory
locations from one release to another (or even from one compiler, or one
set of config options, to another.)
I'd definitely be running memtest86 as the next step here.
Cheers,
Stephen
next prev parent reply other threads:[~2004-03-05 14:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-04 6:50 Daniel Fenert
2004-03-04 7:03 ` Daniel Fenert
2004-03-05 14:06 ` Marcelo Tosatti
2004-03-05 14:14 ` Michael Frank
2004-03-05 14:26 ` Stephen C. Tweedie [this message]
2004-03-05 14:25 ` Stephen C. Tweedie
2004-03-08 13:44 ` Daniel Fenert
2004-04-02 10:20 ` Daniel Fenert
2004-04-02 10:37 ` Stephen C. Tweedie
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=1078496816.14033.56.camel@sisko.scot.redhat.com \
--to=sct@redhat.com \
--cc=daniel@fenert.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux4michelle@freenet.de \
--cc=marcelo.tosatti@cyclades.com \
--cc=mhf@linuxmail.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®