From: Andrew Morton <akpm@zip.com.au>
To: Alois Treindl <alois@astro.ch>
Cc: linux-kernel@vger.kernel.org
Subject: Re: oops with kjournald in SMP 2.4.16
Date: Wed, 27 Mar 2002 09:40:10 -0800 [thread overview]
Message-ID: <3CA203FA.262EB621@zip.com.au> (raw)
In-Reply-To: <Pine.HPX.4.21.0203271410460.15639-100000@as73.astro.ch>
Alois Treindl wrote:
>
> I had an OOPS and kernel crash last night,
> on a dual CPU 2.4.16 (Dell Poweredge 2450, dual 933 Mhz P3, 1.75 gb RAM).
>
> The system had been up for about 100 days without reboot.
>
> I use the ext3 file system with 3 SCSI disks and various NFS clients
> attached to this file server.
>
[ oops in slab allocation for bh_cachep ]
This looks like random memory corruption - someone wrote somewhere
where they shouldn't have.
For a while we were seeing a lot of these. Around 2.4.14 to 2.4.17.
I have twenty or thirty different reports saved away.
But they seem to have stopped. It's beginning to look like whatever
it was got fixed somehow.
>
> Does anyone recognize this problem, and has it been fixed in later kernels?
>
Possibly so, yes. 2.4.16 is suspect in this regard.
-
next prev parent reply other threads:[~2002-03-27 17:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-27 13:15 oops with kjournald in SMP 2.4.16 Alois Treindl
2002-03-27 17:40 ` Andrew Morton [this message]
2002-03-27 19:10 ` Alois Treindl
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=3CA203FA.262EB621@zip.com.au \
--to=akpm@zip.com.au \
--cc=alois@astro.ch \
--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