From: linux@horizon.com
To: neilb@cse.unsw.edu.au
Cc: akpm@osdl.org, kerndev@sc-software.com,
linux-kernel@vger.kernel.org, linux@horizon.com
Subject: Re: 2.6.6 is crashing repeatedly
Date: 27 May 2004 11:25:08 -0000 [thread overview]
Message-ID: <20040527112508.24292.qmail@science.horizon.com> (raw)
In-Reply-To: <20040520060805.1620.qmail@science.horizon.com>
Even with neilb's patch, I just got an nfs oops:
Unable to handle kernel paging request at virtual address f2590000
printing eip:
c01a99a1
*pde = 004b1067
*pte = 32590000
Oops: 0002 [#1]
DEBUG_PAGEALLOC
CPU: 0
EIP: 0060:[<c01a99a1>] Not tainted
EFLAGS: 00010246 (2.6.6)
EIP is at encode_entry+0x51/0x530
eax: cc010000 ebx: 00000000 ecx: 000001cc edx: f32dcdf8
esi: f258fffc edi: d4ec21cc ebp: 000001e0 esp: ebfd9b98
ds: 007b es: 007b ss: 0068
Process nfsd (pid: 1059, threadinfo=ebfd8000 task=ec000a80)
Stack: 00000006 0000002f e2c63080 00000027 00000000 e2c63080 f32dcdf8 0000000a
d4ec21d4 0000001c 02000001 04000900 002bed40 0019a454 00249005 0019a43b
00248f88 00000000 00000000 00000000 00000000 00000000 00000000 00000000
Call Trace:
[<c016af69>] ext3_bread+0x69/0x90
[<c0168505>] ext3_readdir+0x305/0x490
[<c011dba7>] set_current_groups+0x37/0x40
[<c01a9ed0>] nfs3svc_encode_entry_plus+0x0/0x50
[<c019d930>] fh_verify+0x280/0x550
[<c019d5d0>] nfsd_acceptable+0x0/0xe0
[<c013da8c>] open_private_file+0x1c/0x90
[<c014ba2d>] vfs_readdir+0x7d/0x90
[<c01a11f9>] nfsd_readdir+0x79/0xc0
[<c01a6b8a>] nfsd3_proc_readdirplus+0xda/0x1d0
[<c01a9ed0>] nfs3svc_encode_entry_plus+0x0/0x50
[<c01a8e90>] nfs3svc_decode_readdirplusargs+0x0/0x180
[<c019bce6>] nfsd_dispatch+0xb6/0x1a0
[<c03139fd>] svc_authenticate+0x4d/0x80
[<c03112d7>] svc_process+0x487/0x5f0
[<c019bad9>] nfsd+0x179/0x2d0
[<c019b960>] nfsd+0x0/0x2d0
[<c0101fbd>] kernel_thread_helper+0x5/0x18
Code: 89 46 04 81 7c 24 1c 00 01 00 00 b8 ff 00 00 00 8b 94 24 24
This is causing NFS client hangs. Bugger; time to reboot.
next prev parent reply other threads:[~2004-05-27 11:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-20 4:05 2.6.6 is crashing repeatedly linux
2004-05-20 4:23 ` Andrew Morton
2004-05-20 5:29 ` Neil Brown
2004-05-20 6:08 ` linux
2004-05-27 11:25 ` linux [this message]
2004-05-27 11:35 ` Neil Brown
2004-05-27 12:06 ` Olaf Kirch
2004-05-28 2:42 ` Neil Brown
-- strict thread matches above, loose matches on Subject: below --
2004-05-15 6:22 linux
2004-05-15 6:28 ` Andrew Morton
2004-05-15 7:56 ` linux
2004-05-15 10:07 ` John Heil
2004-05-14 14:46 linux
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=20040527112508.24292.qmail@science.horizon.com \
--to=linux@horizon.com \
--cc=akpm@osdl.org \
--cc=kerndev@sc-software.com \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@cse.unsw.edu.au \
/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.