From: Frank Smith <frank.smith@amirix.com>
To: linux-kernel@vger.kernel.org
Cc: Frank Smith <frank.smith@amirix.com>
Subject: __d_lookup in 2.6.6
Date: Fri, 01 Oct 2004 12:40:35 -0300 [thread overview]
Message-ID: <415D7A73.6060205@amirix.com> (raw)
Hello,
Are there any known issues with fs/dcache in kernel 2.6.6 that
would cause oopses like the following in __d_lookup to happen
occasionally? I've done lots of googling on this, and it appears
that there is a lot of flux in this code, so I'm wondering how
solid fs/dcache is in 2.6.6.
This is on a 74xx PPC board, using an NFS root filesystem.
-Frank.
---------
Oops: kernel access of bad area, sig: 11 [#2]
PREEMPT
NIP: C007FD68 LR: C0074694 SP: CE4E7E10 REGS: ce4e7d60 TRAP: 0301 Not tainted
MSR: 00009032 EE: 1 PR: 0 FP: 0 ME: 1 IR/DR: 11
DAR: 2CC7FFFE, DSISR: 40000000
TASK = cfb92740[494] 'split-include' THREAD: ce4e6000Last syscall: 5
GPR00: 00001008 CE4E7E10 CFB92740 CDE8B4CC CE4E7ED8 00000000 00000004 CE4E6000
GPR08: CFF80000 C0290000 00000001 000132F4 24000428
NIP [c007fd68] __d_lookup+0x80/0x1c8
LR [c0074694] __lookup_hash+0x88/0x174
Call trace:
[c0074694] __lookup_hash+0x88/0x174
[c0074f7c] open_namei+0x160/0x4b0
[c0061044] filp_open+0x3c/0x84
[c0061438] sys_open+0x6c/0xbc
[c0006740] ret_from_syscall+0x0/0x44
reply other threads:[~2004-10-01 15:42 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=415D7A73.6060205@amirix.com \
--to=frank.smith@amirix.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 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.