From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Allard Hoeve <allard@byte.nl>
Cc: nfs@lists.sourceforge.net
Subject: Re: Kernel oops (NLM?)
Date: Mon, 14 Aug 2006 10:33:47 -0400 [thread overview]
Message-ID: <1155566027.5664.56.camel@localhost> (raw)
In-Reply-To: <Pine.LNX.4.62.0608140949350.23888@office2.c1.internal>
On Mon, 2006-08-14 at 10:01 +0200, Allard Hoeve wrote:
> Hello all,
>
> Some time ago, I encountered a kernel oops that resulted in a crashed lock
> daemon. nfsd never stopped working, but all client lock requests stalled.
>
> The machine is a PowerEdge 2850 and had a vanilla 2.6.16.13 kernel
> running.
I'd suggest upgrading. We've eliminated a lot of races in NLM since
then, and have (among other things) completely removed the codepath that
appears to have Oopsed below.
Cheers,
Trond
> I'm not sure how to debug this, so I thought I might just send it to you.
>
> If you need any more information, please ask. I'm on the list.
>
> Regards,
>
> Allard Hoeve
>
> PS: Kernel config attached
>
>
>
> Unable to handle kernel paging request at virtual address 6e6f6974
> printing eip:
> c0176469
> *pde = 00000000
> Oops: 0000 [#1]
> SMP
> Modules linked in: nfsd ipv6 shpchp pci_hotplug ehci_hcd uhci_hcd usbcore
> ide_cd cdrom
> CPU: 0
> EIP: 0060:[<c0176469>] Not tainted VLI
> EFLAGS: 00010246 (2.6.16.13-byte #2)
> EIP is at posix_locks_deadlock+0x3b/0x5e
> eax: 00000000 ebx: 6e6f6974 ecx: f7fb74b8 edx: 00000000
> esi: f7fb74b8 edi: f73622b8 ebp: f7362200 esp: f7247efc
> ds: 007b es: 007b ss: 0068
> Process lockd (pid: 2478, threadinfo=f7246000 task=f7d89030)
> Stack: <0>f77634c8 f7fb74b8 f7fb74b8 f7362600 f7362224 c022446d f73622b8 f7fb74b8
> 00000000 d22430c0 f7362224 f7362200 00000000 c0229148 f7735400 f7247f40
> f7477c00 f73622b8 f7362200 f7362600 f7735400 f7735464 c02293a9 f7735400
> Call Trace:
> [<c022446d>] nlmsvc_lock+0x9a/0x414
> [<c0229148>] nlm4svc_retrieve_args+0x7c/0xe9
> [<c02293a9>] nlm4svc_proc_lock+0xe2/0x13d
> [<c045ce98>] svc_process+0x3f0/0x684
> [<c0223a6a>] lockd+0x133/0x23a
> [<c0223937>] lockd+0x0/0x23a
> [<c0101141>] kernel_thread_helper+0x5/0xb
> Code: 24 04 89 3c 24 e8 f7 fa ff ff 85 c0 75 39 8b 1d 5c 47 4e c0 eb 15 8d
> 43 fc 89 74 24 04 89 04 24 e8 dc fa ff ff 85 c0 75 19 8b 1b <8b> 03 0f 18
> 00 90 81 fb 5c 47 4e c0 75 dd 31 c0 83 c4 08 5b 5e
> <4>lockd_down: lockd failed to exit, clearing pid
> ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
> _______________________________________________
> NFS maillist - NFS@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/nfs
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2006-08-14 14:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-14 8:01 Kernel oops (NLM?) Allard Hoeve
2006-08-14 13:51 ` Wendy Cheng
2006-08-14 14:09 ` Allard Hoeve
2006-08-14 14:24 ` Wendy Cheng
2006-08-14 14:33 ` Trond Myklebust [this message]
2006-08-14 15:39 ` Allard Hoeve
2006-08-14 17:29 ` J. Bruce Fields
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=1155566027.5664.56.camel@localhost \
--to=trond.myklebust@fys.uio.no \
--cc=allard@byte.nl \
--cc=nfs@lists.sourceforge.net \
/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.