From: "Gabriel A. Devenyi" <ace@staticwave.ca>
To: linux-kernel@vger.kernel.org
Subject: [OOPS] nfsv4 in linux 2.6.13 (-ck7)
Date: Wed, 12 Oct 2005 19:03:04 -0400 [thread overview]
Message-ID: <200510121903.04485.ace@staticwave.ca> (raw)
This oops seems to occur during heavy i/o load over nfsv4.
nfs-utils version 1.0.7
OOps follows, what other information is needed?
[kernel] Unable to handle kernel paging request at 0000000000100108 RIP:
[kernel] <ffffffff80185e98>{generic_drop_inode+56}
[kernel] PGD 34e3b067 PUD 34e68067 PMD 0
[kernel] CPU 0
[kernel] Modules linked in: nvidia snd_seq_midi snd_emu10k1_synth snd_emux_synth snd_seq_virmidi snd_seq_midi_emul snd_pcm_oss snd_mixer_oss snd_seq_oss snd_seq_midi_event sn
d_seq snd_emu10k1 snd_rawmidi snd_seq_device snd_ac97_codec snd_pcm snd_timer snd_page_alloc snd_util_mem snd_hwdep snd
[kernel] Pid: 179, comm: kswapd0 Tainted: P 2.6.13-ck7
[kernel] RIP: 0010:[<ffffffff80185e98>] <ffffffff80185e98>{generic_drop_inode+56}
[kernel] RSP: 0018:ffff81003fcd7b68 EFLAGS: 00010246
[kernel] RAX: 0000000000100100 RBX: ffff81001a58c950 RCX: 0000000000200200
[kernel] RDX: ffff81001a58c960 RSI: ffff81003eb84000 RDI: ffff81001a58c950
[kernel] RBP: ffff81001a58c950 R08: 00000000fffffffa R09: ffff81001a58ca68
[kernel] R10: 0000000000000001 R11: ffffffff80185e60 R12: 0000000000000000
[kernel] R13: ffff81001a58c7d0 R14: ffff81001a58c860 R15: ffff81003f1f5200
[kernel] FS: 0000000040800960(0000) GS:ffffffff80494800(0000) knlGS:0000000056160040
[kernel] CS: 0010 DS: 0018 ES: 0018 CR0: 000000008005003b
[kernel] CR2: 0000000000100108 CR3: 0000000034de7000 CR4: 00000000000006e0
[kernel] Process kswapd0 (pid: 179, threadinfo ffff81003fcd6000, task ffff81003fcb2760)
[kernel] Stack: ffff81003f1f5c00 ffffffff801d7a25 00000001803e8238 ffff81003fcd7c18
[kernel] ffffffffffffffff ffff81003fcd7c18 ffff81003fcd7c00 ffff81001a58c938
[kernel] 0000000000000000 0000000000000000
[kernel] Call Trace:<ffffffff801d7a25>{__nfs_revalidate_inode+261} <ffffffff8014e5df>{find_get_pages_tag+31}
[kernel] <ffffffff8015781a>{pagevec_lookup_tag+26} <ffffffff8014e00e>{wait_on_page_writeback_range+206}
[kernel] <ffffffff801f11ba>{nfs_do_return_delegation+42} <ffffffff801f12e5>{nfs_inode_return_delegation+197}
[kernel] <ffffffff801d8a10>{nfs4_clear_inode+32} <ffffffff80184cfe>{clear_inode+158}
[kernel] <ffffffff8018594e>{dispose_list+94} <ffffffff80185b82>{shrink_icache_memory+434}
[kernel] <ffffffff8015806b>{shrink_slab+219} <ffffffff80159517>{balance_pgdat+695}
[kernel] <ffffffff801597a8>{kswapd+312} <ffffffff80143b30>{autoremove_wake_function+0}
[kernel] <ffffffff80143b30>{autoremove_wake_function+0} <ffffffff8010f30e>{child_rip+8}
[kernel] <ffffffff80159670>{kswapd+0} <ffffffff8010f306>{child_rip+0}
[kernel]
[kernel] Code: 48 89 48 08 48 89 01 48 8b 05 aa 43 26 00 48 89 50 08 48 89
[kernel] RIP <ffffffff80185e98>{generic_drop_inode+56} RSP <ffff81003fcd7b68>
--
Gabriel A. Devenyi
ace@staticwave.ca
next reply other threads:[~2005-10-12 23:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-12 23:03 Gabriel A. Devenyi [this message]
2005-10-12 23:24 ` [OOPS] nfsv4 in linux 2.6.13 (-ck7) Chris Wright
2005-10-12 23:27 ` Gabriel A. Devenyi
2005-10-12 23:31 ` Chris Wright
2005-10-12 23:37 ` Gabriel A. Devenyi
2005-10-12 23:56 ` Chris Wright
2005-10-14 14:05 ` Gabriel A. Devenyi
2005-10-14 18:13 ` Chris Wright
2005-10-14 15:49 ` Trond Myklebust
2005-10-15 17:23 ` Gabriel A. Devenyi
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=200510121903.04485.ace@staticwave.ca \
--to=ace@staticwave.ca \
--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.