From: Tejun Heo <tj@kernel.org>
To: Sachin Sant <sachinp@in.ibm.com>
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: -next March 3: Boot failure on x86 (Oops)
Date: Thu, 04 Mar 2010 10:28:48 +0900 [thread overview]
Message-ID: <4B8F0CD0.1040507@kernel.org> (raw)
In-Reply-To: <4B8E83D4.6090507@in.ibm.com>
On 03/04/2010 12:44 AM, Sachin Sant wrote:
> Today's next failed to boot on x86 box with following trace
>
> Unpacking initramfs...
> Freeing initrd memory: 10584k freed
> BUG: unable to handle kernel NULL pointer dereference at (null)
> IP: [<c01a6b12>] pcpu_alloc+0x1cb/0x75e
> *pdpt = 00000000005dd001 *pde = 0000000000000000
> Oops: 0000 [#1] SMP
> last sysfs file:
> Modules linked in:
>
> Pid: 1, comm: swapper Not tainted 2.6.33-autotest-next-20100303 #1
> /eserver xSeries 235 -[86717AX]-
> EIP: 0060:[<c01a6b12>] EFLAGS: 00010002 CPU: 1
> EIP is at pcpu_alloc+0x1cb/0x75e
> EAX: 00000000 EBX: c05c4100 ECX: cccccccc EDX: 00000000
> ESI: 000000b0 EDI: 00000005 EBP: f5c69fa8 ESP: f5c69f2c
> DS: 007b ES: 007b FS: 00d8 GS: 0000 SS: 0068
> Process swapper (pid: 1, ti=f5c68000 task=f5c66ce0 task.ti=f5c68000)
> Stack:
> 00000000 00000005 61746164 0a383d29 5f656400 61746164 00000004 000000b0
> <0> 000a3036 00000286 61637061 29656863 0a36313d c0579100 c058da30 f5c69f94
> <0> c01310be c05c41cc 00000028 c058da30 f5c69fa4 c0116a73 c0492091 c0492089
> Call Trace:
> [<c058da30>] ? crash_save_vmcoreinfo_init+0x0/0x31a
> [<c01310be>] ? log_buf_kexec_setup+0x3f/0x67
> [<c058da30>] ? crash_save_vmcoreinfo_init+0x0/0x31a
> [<c0116a73>] ? arch_crash_save_vmcoreinfo+0x37/0x3c
> [<c058d9ff>] ? crash_notes_memory_init+0x0/0x31
> [<c01a70be>] ? __alloc_percpu+0xa/0xc
> [<c058da11>] ? crash_notes_memory_init+0x12/0x31
> [<c0101139>] ? do_one_initcall+0x4c/0x131
> [<c057b352>] ? kernel_init+0x127/0x178
> [<c057b22b>] ? kernel_init+0x0/0x178
> [<c0102df6>] ? kernel_thread_helper+0x6/0x10
> Code: 45 a8 e9 65 ff ff ff 8b 4d 9c 8b 55 a0 8b 45 84 e8 31 fa ff ff 85
> c0 89 45 a4 0f 89 fd 00 00 00 8b 45 84 8b 00 89 45 84 8b 55 84 <8b> 02
> 0f 18 00 90 8b 45 cc 03 05 a0 9b 57 c0 39 c2 0f 85 67 ff
> EIP: [<c01a6b12>] pcpu_alloc+0x1cb/0x75e SS:ESP 0068:f5c69f2c
> CR2: 0000000000000000
> ---[ end trace a7919e7f17c0a725 ]---
>
> x86_64 boots fine. Have attached dmesg log.
Can you please feed the address to gdb and get the line number? Also,
is it reproducible on mainline?
Thanks.
--
tejun
next prev parent reply other threads:[~2010-03-04 1:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-03 6:46 linux-next: Tree for March 3 Stephen Rothwell
2010-03-03 15:44 ` -next March 3: Boot failure on x86 (Oops) Sachin Sant
2010-03-04 1:28 ` Tejun Heo [this message]
2010-03-04 5:23 ` Sachin Sant
2010-03-05 6:08 ` Tejun Heo
2010-03-05 6:09 ` Tejun Heo
2010-03-05 6:17 ` Tejun Heo
2010-03-05 7:47 ` Sachin Sant
2010-03-05 13:25 ` Tejun Heo
2010-03-05 10:44 ` Sachin Sant
2010-03-05 13:24 ` Tejun Heo
2010-03-06 7:39 ` Sachin Sant
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=4B8F0CD0.1040507@kernel.org \
--to=tj@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sachinp@in.ibm.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