From: Andrew Morton <akpm@osdl.org>
To: "Jaakko Hyvätti" <jaakko@hyvatti.iki.fi>
Cc: linux-kernel@vger.kernel.org
Subject: Re: ext3 and nfsd do not work under load (Re: x86_64, LOCKUP on CPU0, kjournald)
Date: Mon, 1 Nov 2004 01:31:50 -0800 [thread overview]
Message-ID: <20041101013150.2ab0aaa5.akpm@osdl.org> (raw)
In-Reply-To: <Pine.LNX.4.58.0411010847180.2172@gyre.weather.fi>
Jaakko Hyvätti <jaakko@hyvatti.iki.fi> wrote:
>
>
> Here is another oops and lockup, with nfsd now there in the trace also:
>
> Unable to handle kernel paging request at ffffffff00000808 RIP:
> <ffffffff80161b37>{cache_alloc_refill+329}
> PML4 103027 PGD 0
> Oops: 0002 [1] SMP
> CPU 0
> Modules linked in: w83627hf i2c_sensor i2c_isa i2c_core nfsd exportfs lockd sunrpc md5 ipv6 parport_pc lp parport tg3 ipt_REJECT ipt_state ip_conntrack iptable_filter ip_tables dm_mod ohci_hcd button battery asus_acpi ac ext3 jbd 3w_xxxx sd_mod scsi_mod
> Pid: 1968, comm: nfsd Not tainted 2.6.8-1.521smp
That's a vendor kernel of some form, yes?
> RIP: 0010:[<ffffffff80161b37>] <ffffffff80161b37>{cache_alloc_refill+329}
I'd suggest that you either recompile this vendor kernel with
CONFIG_DEBUG_SLAB=y or try a later kernel.org kernel and see if it's fixed.
Or look for an updated kernel from your vendor. And check the vendor's
bug tracking system for other reports of this problem.
I don't recall having seen anyone else report this crash.
next prev parent reply other threads:[~2004-11-01 9:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-26 5:31 x86_64, LOCKUP on CPU0, kjournald Jaakko Hyvätti
2004-11-01 9:25 ` ext3 and nfsd do not work under load (Re: x86_64, LOCKUP on CPU0, kjournald) Jaakko Hyvätti
2004-11-01 9:31 ` Andrew Morton [this message]
2004-11-01 10:31 ` Jaakko Hyvätti
2004-11-05 9:49 ` Jaakko Hyvätti
2004-11-05 10:03 ` Nigel Cunningham
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=20041101013150.2ab0aaa5.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=jaakko@hyvatti.iki.fi \
--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®