From: Andre Noll <maan@systemlinux.org>
To: linux-kernel@vger.kernel.org, nfs@lists.sourceforge.net
Subject: 2.6.18-rc5 page_to_pfn: Unable to handle kernel NULL pointer dereference
Date: Fri, 8 Sep 2006 09:31:25 +0200 [thread overview]
Message-ID: <20060908073125.GA23642@skl-net.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 2355 bytes --]
The following just happend to one of our 8-way Opteron cluster nodes
(nfs client version 3, solaris nfs server).
Just let me know if you need further info.
Andre
Unable to handle kernel NULL pointer dereference at 0000000000000000 RIP:
[<ffffffff80150c09>] page_to_pfn+0x0/0x33
PGD 74ba36067 PUD 0
Oops: 0000 [1] SMP
CPU 0
Pid: 1782, comm: sge_execd Not tainted 2.6.18-rc5-tt64-6-gd9629953 #23
RIP: 0010:[<ffffffff80150c09>] [<ffffffff80150c09>] page_to_pfn+0x0/0x33
RSP: 0018:ffff81074b99bbb0 EFLAGS: 00010287
RAX: 0000000000000b9a RBX: 0000000000000734 RCX: 0000000000000b9a
RDX: ffff81074b99bbf0 RSI: ffff810812320500 RDI: 0000000000000000
RBP: 0000000000000466 R08: ffff8104c53a89a0 R09: ffff8104c53a8810
R10: 0000000000000000 R11: 0000000000000000 R12: 00000000000008cc
R13: ffff81074b99bbf8 R14: 0000000000002000 R15: ffff8104c53a8ab8
FS: 00002b75f92987a0(0000) GS:ffffffff80703000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
CR2: 0000000000000000 CR3: 000000080b603000 CR4: 00000000000006a0
Process sge_execd (pid: 1782, threadinfo ffff81074b99a000, task ffff81080bc50040)
Stack: ffffffff80205a72 ffff8104c53a89a0 ffff810812320380 0000000000000b9a
ffff8104c53a89a0 0000000000000466 ffffffff80205cf8 0000000000000000
ffff810817df9678 0000000000000000 ffff8104c53a89a0 ffff810817df9678
Call Trace:
[<ffffffff80205a72>] nfs_readpage_truncate_uninitialised_page+0x77/0xec
[<ffffffff80205cf8>] nfs_readpage_sync+0x211/0x255
[<ffffffff8020677e>] nfs_readpage+0x118/0x151
[<ffffffff8014c65e>] do_generic_mapping_read+0x1ec/0x398
[<ffffffff8014c80a>] file_read_actor+0x0/0xd1
[<ffffffff8014ca52>] __generic_file_aio_read+0x177/0x1b0
[<ffffffff8014cabf>] generic_file_aio_read+0x34/0x39
[<ffffffff801fea68>] nfs_file_read+0xb1/0xc0
[<ffffffff8016df5c>] do_sync_read+0xc9/0x106
[<ffffffff8013e541>] autoremove_wake_function+0x0/0x2e
[<ffffffff8015bd8e>] do_mmap_pgoff+0x5fd/0x6de
[<ffffffff8016e046>] vfs_read+0xad/0x14c
[<ffffffff8016e380>] sys_read+0x45/0x6e
[<ffffffff80109726>] system_call+0x7e/0x83
Code: 48 8b 07 48 c1 e8 3a 48 8b 14 c5 00 c8 70 80 48 b8 b7 6d db
RIP [<ffffffff80150c09>] page_to_pfn+0x0/0x33
RSP <ffff81074b99bbb0>
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 reply other threads:[~2006-09-08 7:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-08 7:31 Andre Noll [this message]
2006-09-15 12:40 ` Andre Noll
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=20060908073125.GA23642@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