From: Andre Noll <maan@systemlinux.org>
To: linux-kernel@vger.kernel.org, nfs@lists.sourceforge.net
Subject: Re: 2.6.18-rc5 page_to_pfn: Unable to handle kernel NULL pointer dereference
Date: Fri, 15 Sep 2006 14:40:43 +0200 [thread overview]
Message-ID: <20060915124043.GA20462@skl-net.de> (raw)
In-Reply-To: <20060908073125.GA23642@skl-net.de>
[-- Attachment #1: Type: text/plain, Size: 2264 bytes --]
On 09:31, Andre Noll wrote:
> The following just happend to one of our 8-way Opteron cluster nodes
> (nfs client version 3, solaris nfs server).
The problem is still present in 2.6.18-rc7. This time it happend on a
2-processor Opteron machine:
Pid: 945, comm: sge_execd Not tainted 2.6.18-rc7-tt64-6-g1883c5ab #4
RIP: 0010:[<ffffffff80150cad>] [<ffffffff80150cad>] page_to_pfn+0x0/0x33
RSP: 0018:ffff8100fac73bb0 EFLAGS: 00010283
RAX: 0000000000000a57 RBX: 00000000000004ae RCX: 0000000000000a57
RDX: ffff8100fac73bf0 RSI: ffff8101b9b1c540 RDI: 0000000000000000
RBP: 00000000000005a9 R08: ffff8101f7aa31d0 R09: ffff8101f7aa3040
R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000b52
R13: ffff8100fac73bf8 R14: 0000000000002000 R15: ffff8101f7aa32e8
FS: 00002b83ded037a0(0000) GS:ffff8101000dc540(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
CR2: 0000000000000000 CR3: 00000000fad78000 CR4: 00000000000006a0
Process sge_execd (pid: 945, threadinfo ffff8100fac72000, task ffff810004be5180)
Stack: ffffffff801d6276 ffff8101fc4f0440 ffff8101b9b1c3c0 0000000000000a57
ffff8101f7aa31d0 00000000000005a9 ffffffff801d64fc 0000000000000001
ffff8101ffec2e18 0000000000000000 ffff8101f7aa31d0 ffff8101ffec2e18
Call Trace:
[<ffffffff801d6276>] nfs_readpage_truncate_uninitialised_page+0x76/0xeb
[<ffffffff801d64fc>] nfs_readpage_sync+0x211/0x253
[<ffffffff801d6f89>] nfs_readpage+0x118/0x151
[<ffffffff8014c6fe>] do_generic_mapping_read+0x1ec/0x398
[<ffffffff8014c8aa>] file_read_actor+0x0/0xd1
[<ffffffff8014caf2>] __generic_file_aio_read+0x177/0x1b0
[<ffffffff8014cb5f>] generic_file_aio_read+0x34/0x39
[<ffffffff801cf3eb>] nfs_file_read+0x84/0x93
[<ffffffff8016e0fc>] do_sync_read+0xc9/0x106
[<ffffffff8013e5fd>] autoremove_wake_function+0x0/0x2e
[<ffffffff8015bf32>] do_mmap_pgoff+0x5fd/0x6de
[<ffffffff8016e1e6>] vfs_read+0xad/0x14c
[<ffffffff8016e520>] sys_read+0x45/0x6e
[<ffffffff80109726>] system_call+0x7e/0x83
Code: 48 8b 07 48 c1 e8 3a 48 8b 14 c5 c0 79 5f 80 48 b8 b7 6d db
RIP [<ffffffff80150cad>] page_to_pfn+0x0/0x33
RSP <ffff8100fac73bb0>
CR2: 0000000000000000
--
The only person who always got his work done by Friday was Robinson Crusoe
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-09-15 12:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-08 7:31 Andre Noll
2006-09-15 12:40 ` Andre Noll [this message]
2006-09-15 20:07 ` [NFS] " Trond Myklebust
2006-09-18 8:07 ` Andre Noll
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=20060915124043.GA20462@skl-net.de \
--to=maan@systemlinux.org \
--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
Powered by JetHome