From: William Lee Irwin III <wli@holomorphy.com>
To: linux-kernel@vger.kernel.org
Cc: nfs@lists.sourceforge.net
Subject: nfsd oops 2.6.7-rc1
Date: Fri, 28 May 2004 19:35:50 -0700 [thread overview]
Message-ID: <20040529023550.GB2370@holomorphy.com> (raw)
While idle, the following oops happened. On virgin 2.6.7-rc1.
-- wli
------------[ cut here ]------------
kernel BUG at include/linux/dcache.h:276!
invalid operand: 0000 [#1]
Modules linked in:
CPU: 0
EIP: 0060:[<c01e1de1>] Not tainted
EFLAGS: 00010246 (2.6.7-rc1-holomorphy-1)
EIP is at fh_compose+0x3d1/0x430
eax: 00000000 ebx: 00800070 ecx: effe8d14 edx: 00000020
esi: e29bf800 edi: 00000000 ebp: ddc24f58 esp: e29b3eb0
ds: 007b es: 007b ss: 0068
Process nfsd (pid: 1335, threadinfo=e29b3000 task=e29c0410)
Stack: 00000000 edd2444c c014b66f e29b3ed4 e432c0c0 8191bdfa ddc24b4c ddc24b4c
eca73d0c 0100bdfa effe8d14 0000001a ddc24f58 ddc24f58 e29ce000 e432c0a6
c01e247b e29ce000 00000001 effe7314 c0419bee ddc24b4c e2a23000 effe8d14
Call Trace:
[<c014b66f>] __lookup_hash+0x5f/0xb0
[<c01e247b>] nfsd_lookup+0x12b/0x420
[<c0419bee>] svcauth_unix_accept+0x23e/0x280
[<c01e0513>] nfsd_proc_lookup+0x53/0xa0
[<c01e82c4>] nfssvc_decode_diropargs+0x54/0xb0
[<c01e8270>] nfssvc_decode_diropargs+0x0/0xb0
[<c01dfb36>] nfsd_dispatch+0xb6/0x1c0
[<c0416523>] svc_process+0x463/0x5c0
[<c01df92f>] nfsd+0x16f/0x2c0
[<c01df7c0>] nfsd+0x0/0x2c0
[<c0103a7d>] kernel_thread_helper+0x5/0x18
Code: 0f 0b 14 01 ba 29 44 c0 e9 99 fd ff ff 8b 45 18 8b 4c 24 1c
next reply other threads:[~2004-05-29 2:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-29 2:35 William Lee Irwin III [this message]
2004-05-29 3:24 ` nfsd oops 2.6.7-rc1 Neil Brown
2004-05-29 3:25 ` William Lee Irwin III
2004-05-29 4:47 ` William Lee Irwin III
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=20040529023550.GB2370@holomorphy.com \
--to=wli@holomorphy.com \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox