From: Andrew Morton <akpm@zip.com.au>
To: Patrick Mau <mau@oscar.prima.de>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Oops with 2.4.16-pre1 (nfs related)
Date: Sat, 15 Dec 2001 21:34:10 -0800 [thread overview]
Message-ID: <3C1C3252.EFA44817@zip.com.au> (raw)
In-Reply-To: <20011216015622.GA913@oscar.dorf.de>
Patrick Mau wrote:
>
> Hi all,
>
> today I had the following oops which makes the machine hang.
> Lots of processes where in D state and I had no keyboard so
> I pushed the Big Button and rebooted.
>
> The kernel runs without modules and uses ext3.
> Hardware is an old AMD K6-2, 384MB RAM, IDE Disks
> VIA chipset ... what else is important ?
Old.
Was this just a once-off?
> ...
>
> >>EIP; c0129cf8 <__insert_into_lru_list+1c/5c> <=====
> Trace; c012a5f0 <__refile_buffer+48/50>
> Trace; c012a600 <refile_buffer+8/10>
> Trace; c014dca4 <journal_dirty_data+168/19c>
> Trace; c0146ab8 <journal_dirty_sync_data+14/58>
> Trace; c0146922 <walk_page_buffers+56/7c>
> Trace; c0146ccc <ext3_commit_write+104/1b4>
> Trace; c0146aa4 <journal_dirty_sync_data+0/58>
> Trace; c0120834 <generic_file_write+498/640>
> Trace; c0144a06 <ext3_file_write+42/4c>
> Trace; c0173638 <nfsd_write+120/29c>
> Trace; c01782f2 <nfsd3_proc_write+ea/108>
> Trace; c0170032 <nfsd_dispatch+d2/1a0>
> Trace; c0215604 <svc_process+28c/4d8>
> Trace; c016fe2a <nfsd+1b2/2e8>
If anything, that would be an ext3 bug. But that particular code
path has been trodden so many times by so many machines that
I'd be suspecting your RAM. There are a couple of pointers
in the buffer_head which should be zero, and one of them is not.
-
prev parent reply other threads:[~2001-12-16 5:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-16 1:56 Oops with 2.4.16-pre1 (nfs related) Patrick Mau
2001-12-16 5:34 ` Andrew Morton [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=3C1C3252.EFA44817@zip.com.au \
--to=akpm@zip.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=mau@oscar.prima.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.