From: Andrew Morton <akpm@zip.com.au>
To: Nico Schottelius <nicos@pcsystems.de>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: multiply NULL pointer
Date: Sun, 12 Aug 2001 16:06:44 -0700 [thread overview]
Message-ID: <3B770C04.C8FDD6E6@zip.com.au> (raw)
In-Reply-To: <3B72BA01.34D2A67F@pcsystems.de>
Nico Schottelius wrote:
>
> Hello!
>
> Running a p2 400 mhz box with a 3com 3c905, with
> _very_ heavy nfs traffic and disc io the following NULL
> pointers were produced. I attached the whole dmesg output.
> If more informations are needed, I will send them.
>
> After every NULL pointer printed on the console
> I took a new dmesg, so the one with the highest number
> should be relevant.
>
Please tell us exactly which kernel you're using. It appears
to be a flavour of 2.4.7 with ext3, yes?
Also, please take the very first oops output which occurs
after a reboot and feed that into
ksymoops -m System.map < oops-trace-file.txt
Make sure you have the correct System.map!
The fact that your bdflush and kupdate daemons have gone zombie
suggests that the kernel died in the new buffer flushing code.
There was a bug fixed in that area late in the 2.4.8-pre series.
>From memory, the bug was a missing test for a null bh in
fs/buffer.c:sync_old-buffers():
for (;;) {
struct buffer_head *bh;
spin_lock(&lru_list_lock);
bh = lru_list[BUF_DIRTY];
if (!bh || time_before(jiffies, bh->b_flushtime))
^^^^^^
You should try 2.4.8.
-
next prev parent reply other threads:[~2001-08-12 23:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-09 16:27 multiply NULL pointer Nico Schottelius
2001-08-11 6:38 ` Brian
2001-08-12 23:06 ` Andrew Morton [this message]
2001-08-12 23:28 ` Brian
2001-08-21 20:16 ` Nico Schottelius
[not found] <Pine.LNX.4.10.10108122305360.7374-100000@coffee.psychology.mcmaster.ca>
2001-08-21 20:10 ` Nico Schottelius
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=3B770C04.C8FDD6E6@zip.com.au \
--to=akpm@zip.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=nicos@pcsystems.de \
/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