From: Kamalesh Babulal <kamalesh@linux.vnet.ibm.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
yhlu.kernel@gmail.com, Andrew Morton <akpm@linux-foundation.org>,
",
pbadari@us.ibm.com, michael@ellerman.id.au,
Andy Whitcroft <apw@shadowen.org>"@d23av01.au.ibm.com
Subject: [BUG] linux-next: Tree for April 14 - kernel BUG at arch/powerpc/mm/init_64.c:240! (fixed in -mm)
Date: Mon, 14 Apr 2008 17:41:23 +0530 [thread overview]
Message-ID: <480349EB.8040708@linux.vnet.ibm.com> (raw)
In-Reply-To: <20080414203423.22bf99d1.sfr@canb.auug.org.au>
Hi Stephen,
The next-20080414 kernel panic's while booting up on the ppc machines.
The same was seen in the 2.6.25-rc8-mm1 kernel and was fixed by
the patch at http://lkml.org/lkml/2008/4/2/650
------------[ cut here ]------------
kernel BUG at arch/powerpc/mm/init_64.c:240!
Oops: Exception in kernel mode, sig: 5 [#1]
SMP NR_CPUS=128 NUMA pSeries
Modules linked in:
NIP: c0000000006ca18c LR: c0000000006ca184 CTR: 0000000000000000
REGS: c00000000081f950 TRAP: 0700 Not tainted (2.6.25-rc9-next-20080414-x86-latest.git-autotest)
MSR: 8000000000021032 <ME,IR,DR> CR: 24000088 XER: 20000001
TASK = c0000000007334d0[0] 'swapper' THREAD: c00000000081c000 CPU: 0
GPR00: c0000000006ca184 c00000000081fbd0 c00000000081c778 0000000000000001
GPR04: c0000000006def90 000000000000016e 0000000000000170 0000000000001090
GPR08: 0000000207038208 0000000000000000 0000000000000001 800000000ed93080
GPR12: c00000000081fae0 c000000000733e80 0000000000000000 c0000000005f4788
GPR16: 4000000002100000 c0000000005f3010 0000000000000000 000000000023f000
GPR20: 00000000027d07d8 c0000000006d07d8 00000000027d0a48 c0000000006d0a48
GPR24: c0000000005f41c8 0000000002b00000 0000000000000000 0000000000000000
GPR28: cf000000001f8000 cf00000001000000 0000000001000000 cf00000000000000
NIP [c0000000006ca18c] .vmemmap_populate+0xbc/0x100
LR [c0000000006ca184] .vmemmap_populate+0xb4/0x100
Call Trace:
[c00000000081fbd0] [c0000000006ca184] .vmemmap_populate+0xb4/0x100 (unreliable)
[c00000000081fc70] [c0000000006cae08] .sparse_mem_map_populate+0x38/0x5c
[c00000000081fd00] [c0000000006b8db0] .sparse_early_mem_map_alloc+0x54/0x94
[c00000000081fd90] [c0000000006b91d8] .sparse_init+0x1dc/0x218
[c00000000081fe40] [c0000000006a54f4] .setup_arch+0x1ac/0x218
[c00000000081fed0] [c00000000069c6c0] .start_kernel+0xec/0x464
[c00000000081ff90] [c000000000008524] .start_here_common+0x54/0xb0
Instruction dump:
7fe3fb78 7ca02a14 4082000c 3860fff4 48000040 e9228980 e9628988 e8e90002
e90b0002 4b961ab1 60000000 78630fe0 <0b030000> 7ffff214 7fbdf214 7fbfe040
---[ end trace 8640abe69a316dee ]---
Kernel panic - not syncing: Attempted to kill the idle task!
Call Trace:
[c00000000081f470] [c00000000000f970] .show_stack+0x70/0x1bc (unreliable)
[c00000000081f520] [c0000000000540fc] .panic+0x80/0x1b8
[c00000000081f5c0] [c000000000058ca4] .do_exit+0x8c/0x758
[c00000000081f680] [c0000000000235cc] .die+0x24c/0x27c
[c00000000081f720] [c0000000000238fc] ._exception+0x88/0x204
[c00000000081f8e0] [c000000000004a84] program_check_common+0x104/0x180
--- Exception: 700 at .vmemmap_populate+0xbc/0x100
LR = .vmemmap_populate+0xb4/0x100
[c00000000081fc70] [c0000000006cae08] .sparse_mem_map_populate+0x38/0x5c
[c00000000081fd00] [c0000000006b8db0] .sparse_early_mem_map_alloc+0x54/0x94
[c00000000081fd90] [c0000000006b91d8] .sparse_init+0x1dc/0x218
[c00000000081fe40] [c0000000006a54f4] .setup_arch+0x1ac/0x218
[c00000000081fed0] [c00000000069c6c0] .start_kernel+0xec/0x464
[c00000000081ff90] [c000000000008524] .start_here_common+0x54/0xb0
--
Thanks & Regards,
Kamalesh Babulal,
Linux Technology Center,
IBM, ISTL.
next prev parent reply other threads:[~2008-04-14 12:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-14 10:34 linux-next: Tree for April 14 Stephen Rothwell
2008-04-14 12:11 ` Kamalesh Babulal [this message]
2008-04-14 18:26 ` [BUG] linux-next: Tree for April 14 - kernel BUG at arch/powerpc/mm/init_64.c:240! (fixed in -mm) Yinghai Lu
2008-04-14 18:31 ` Yinghai Lu
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=480349EB.8040708@linux.vnet.ibm.com \
--to=kamalesh@linux.vnet.ibm.com \
--cc=", pbadari@us.ibm.com, michael@ellerman.id.au, Andy Whitcroft <apw@shadowen.org>"@d23av01.au.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=yhlu.kernel@gmail.com \
/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