From: Peter Clay <pete@azuro.com>
To: linux-kernel@vger.kernel.org
Subject: NFS oops with 2.6.4 server / Solaris 2.8 client
Date: Fri, 16 Apr 2004 15:10:16 +0100 [thread overview]
Message-ID: <20040416141016.GA27316@platinum.azuro.com> (raw)
I have this oops with the situation described in the subject, using the Solaris
automounter in /net to access the Linux server. This is repeatable. It doesn't
always crash the machine, but fairly soon after I end up with all the nfsd
processes stuck in 'D' state. What other debugging information would help find
this problem?
(output of dmesg follows)
...
nfs warning: mount version older than kernel
RPC request reserved 0 but used 112
Unable to handle kernel NULL pointer dereference at virtual address 00000004
printing eip:
c02a91c0
*pde = 00000000
Oops: 0002 [#1]
CPU: 0
EIP: 0060:[<c02a91c0>] Not tainted
EFLAGS: 00010287
EIP is at do_tcp_sendpages+0x660/0xbf0
eax: 00000000 ebx: ddc5cb80 ecx: 00000008 edx: 00000000
esi: 00000001 edi: cfd0d9c8 ebp: d0632100 esp: dd0dbe34
ds: 007b es: 007b ss: 0068
Process nfsd (pid: 1366, threadinfo=dd0da000 task=dd100d40)
Stack: 000000b0 000000d0 c014d61a dd19670c dd0dbe70 c01c7efd d0632110 00000000
00000008 00000000 00000000 00000000 000005b4 00007530 00000000 cfd0d800
00000008 00000000 c02a97d9 cfd0d800 dd0dbeac 00000000 00000008 00000000
Call Trace:
[<c014d61a>] close_private_file+0x2a/0x30
[<c01c7efd>] nfsd_close+0x1d/0x40
[<c02a97d9>] tcp_sendpage+0x89/0xa0
[<c02e8343>] svc_sendto+0x173/0x2b0
[<c01d0e28>] encode_post_op_attr+0x1c8/0x260
[<c02e941c>] svc_tcp_sendto+0x6c/0xc0
[<c02e9bbc>] svc_send+0xbc/0x100
[<c02eb828>] svcauth_unix_release+0x58/0x60
[<c02e7858>] svc_process+0x1b8/0x640
[<c01c43b0>] nfsd+0x190/0x300
[<c01c4220>] nfsd+0x0/0x300
[<c0108c49>] kernel_thread_helper+0x5/0xc
Code: ff 42 04 8b 83 a8 00 00 00 8b 6c 24 28 8d 04 f0 89 68 10 8d
next reply other threads:[~2004-04-16 14:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-16 14:10 Peter Clay [this message]
2004-04-16 21:30 ` Andrew Morton
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=20040416141016.GA27316@platinum.azuro.com \
--to=pete@azuro.com \
--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®