From: David Ford <david+powerix@blue-labs.org>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Trond Myklebust <trond.myklebust@fys.uio.no>,
Neil Brown <neilb@cse.unsw.edu.au>,
Oleg Drokin <green@namesys.com>, Hans Reiser <reiser@namesys.com>
Subject: [OOPS] 100% repeatable OOPS, 2.5.61-66, NFS and reiserfs
Date: Tue, 08 Apr 2003 12:31:15 -0400 [thread overview]
Message-ID: <3E92F953.8080401@blue-labs.org> (raw)
1. Power loss this morning
2. Fixed filesystems (reiserfstools is fscking useless on root filesystems)
3. Now server OOPSes when nfs client tries to stat/read files/dirs
Unable to handle kernel NULL pointer dereference at virtual address 00000000
printing eip:
00000000
*pde = 00000000
Oops: 0000
CPU: 0
EIP: 0060:[<00000000>] Not tainted
EFLAGS: 00010202
EIP is at 0x0
eax: 00000000 ebx: 00000006 ecx: c03efb28 edx: c827be94
esi: c83ad014 edi: dfd16e00 ebp: c827beac esp: c827be70
ds: 007b es: 007b ss: 0068
Process nfsd (pid: 1188, threadinfo=c827a000 task=df3c2740)
Stack: c01ce6b8 dfd16e00 c827bea0 c827be94 c01ad070 dfff04f4 00000006
c83ad004
11270000 00000e07 000008dd 0000004d 0002f4f2 00000e07 01214b98
c827bef4
c01ad4c7 dfd16e00 c83ad014 00000006 00000006 c01ad070 dfff04f4
c83ad004
Call Trace:
[<c01ce6b8>] reiserfs_decode_fh+0xb4/0xc0
[<c01ad070>] nfsd_acceptable+0x0/0x114
[<c01ad4c7>] fh_verify+0x343/0x4f8
[<c01ad070>] nfsd_acceptable+0x0/0x114
[<c01ae694>] nfsd_access+0x28/0xf4
[<c01b4ec9>] nfsd3_proc_access+0xc1/0xd0
[<c01ab4a3>] nfsd_dispatch+0xc3/0x18f
[<c033b5cd>] svc_process+0x3ed/0x67a
[<c01ab200>] nfsd+0x23c/0x41c
[<c01aafc4>] nfsd+0x0/0x41c
[<c0107145>] kernel_thread_helper+0x5/0xc
Code: Bad EIP value.
<1>Unable to handle kernel NULL pointer dereference at virtual address
00000000
printing eip:
00000000
*pde = 00000000
Oops: 0000
CPU: 1
EIP: 0060:[<00000000>] Not tainted
EFLAGS: 00010202
EIP is at 0x0
eax: 00000000 ebx: 00000006 ecx: c03efb28 edx: c8269e94
esi: c83a0014 edi: dfd16e00 ebp: c8269eac esp: c8269e70
ds: 007b es: 007b ss: 0068
Process nfsd (pid: 1189, threadinfo=c8268000 task=df5ba720)
Stack: c01ce6b8 dfd16e00 c8269ea0 c8269e94 c01ad070 dfff04f4 00000006
c83a0004
11270000 00000e07 000008dd 0000004d 0002f4f2 00000e07 01214b98
c8269ef4
c01ad4c7 dfd16e00 c83a0014 00000006 00000006 c01ad070 dfff04f4
c83a0004
Call Trace:
[<c01ce6b8>] reiserfs_decode_fh+0xb4/0xc0
[<c01ad070>] nfsd_acceptable+0x0/0x114
[<c01ad4c7>] fh_verify+0x343/0x4f8
[<c01ad070>] nfsd_acceptable+0x0/0x114
[<c01ae694>] nfsd_access+0x28/0xf4
[<c01b4ec9>] nfsd3_proc_access+0xc1/0xd0
[<c01ab4a3>] nfsd_dispatch+0xc3/0x18f
[<c033b5cd>] svc_process+0x3ed/0x67a
[<c01ab200>] nfsd+0x23c/0x41c
[<c01aafc4>] nfsd+0x0/0x41c
[<c0107145>] kernel_thread_helper+0x5/0xc
(repeats several times)
Server is now useless and needs to be rebooted. I've shutdown my NFS
clients in order to run the server minimally, it's a mail/web server.
Assistance would be appreciated.
next reply other threads:[~2003-04-07 21:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-08 16:31 David Ford [this message]
2003-04-07 23:17 ` [OOPS] 100% repeatable OOPS, 2.5.61-66, NFS and reiserfs Neil Brown
2003-04-08 21:47 ` David Ford
2003-04-08 3:38 ` Neil Brown
2003-04-08 3:44 ` David Ford
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=3E92F953.8080401@blue-labs.org \
--to=david+powerix@blue-labs.org \
--cc=green@namesys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@cse.unsw.edu.au \
--cc=reiser@namesys.com \
--cc=trond.myklebust@fys.uio.no \
/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