From: Joe Feise <jfeise@feise.com>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [BUG] NFS(?) bug in 2.6.16-rc5-mm3
Date: Mon, 13 Mar 2006 19:54:36 -0800 [thread overview]
Message-ID: <44163E7C.2000001@feise.com> (raw)
In-Reply-To: <1142199317.8871.2.camel@lade.trondhjem.org>
[-- Attachment #1: Type: text/plain, Size: 2180 bytes --]
Trond Myklebust wrote on 03/12/06 13:35:
> On Sun, 2006-03-12 at 11:33 -0800, Joe Feise wrote:
>> In certain cases, when programmatically traversing a directory tree mounted
>> through NFS, I get a kernel oops.
>> Two examples are listed below.
>
> Please could you retry without the cisco_ipsec module (and whatever else
> is tainting the kernel).
Here is the problem without the cisco_ipsec module, with an untainted kernel.
-Joe
BUG: unable to handle kernel paging request at virtual address 02b00025
printing eip:
c016a8b3
*pde = 00000000
Oops: 0000 [#1]
PREEMPT
last sysfs file: /class/net/eth2/ifindex
Modules linked in: pl2303 usbserial softdog snd_pcm_oss snd_mixer_oss snd_cs46xx
gameport snd_rawmidi snd_seq_de
vice snd_ac97_codec snd_ac97_bus snd_pcm snd_timer snd soundcore snd_page_alloc
zoran i2c_algo_bit videodev saa7
111 i2c_core pegasus arc4 ppp_mppe ppp_deflate ppp_generic slhc usblp
CPU: 0
EIP: 0060:[<c016a8b3>] Not tainted VLI
EFLAGS: 00010206 (2.6.16-rc5-mm3 #9)
EIP is at iput+0x1d/0x65
eax: 02b00011 ebx: d4bb5a00 ecx: d4bb5a18 edx: d4bb5a18
esi: f2183d20 edi: 00000020 ebp: ffffe000 esp: c7c67e3c
ds: 007b es: 007b ss: 0068
Process cc1 (pid: 11024, threadinfo=c7c66000 task=f7c8f570)
Stack: <0>f2183d14 c0167e41 c7c66000 c7c66000 000000b6 0004aa24 c17deac0 c0168230
c013c911 00000000 0001eaf8 00000000 012a8900 00000000 00025c2d 0004aa24
0000007e 00000000 00000000 000280d2 00000020 c7c67f08 c05a5218 0000000c
Call Trace:
<c0167e41> prune_dcache+0x12d/0x162 <c0168230> shrink_dcache_memory+0x14/0x37
<c013c911> shrink_slab+0x131/0x1f7 <c013dab9> try_to_free_pages+0xee/0x1ab
<c0138ea8> __alloc_pages+0x113/0x29c <c0141352> do_anonymous_page+0x40/0x148
<c0141796> __handle_mm_fault+0xa5/0x1d9 <c0467197> notifier_call_chain+0x17/0x2b
<c0466cb7> do_page_fault+0x16a/0x633 <c0466b4d> do_page_fault+0x0/0x633
<c010342b> error_code+0x4f/0x54
Code: 85 c9 75 05 e9 4a fd ff ff e9 93 fe ff ff 85 c0 53 89 c3 74 4c 8b 80 90 00
00 00 83 bb 24 01 00 00 20 8b 4
0 20 74 42 85 c0 74 07 <8b> 50 14 85 d2 75 31 8d 43 24 ba 80 84 68 c0 e8 8d a2
11 00 85
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2006-03-14 3:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-12 19:33 [BUG] NFS(?) bug in 2.6.16-rc5-mm3 Joe Feise
2006-03-12 20:06 ` Joe Feise
2006-03-12 21:35 ` Trond Myklebust
2006-03-14 3:54 ` Joe Feise [this message]
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=44163E7C.2000001@feise.com \
--to=jfeise@feise.com \
--cc=linux-kernel@vger.kernel.org \
--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