From: Sachin Sant <sachinp@in.ibm.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: boot panic in serial init
Date: Fri, 24 Jul 2009 16:35:01 +0530 [thread overview]
Message-ID: <4A69955D.2040000@in.ibm.com> (raw)
In-Reply-To: <20090724171841.b128f8be.sfr@canb.auug.org.au>
Stephen Rothwell wrote:
> Hi Alan,
>
> Today's linux-next on a pSeries PowerPC machine panics during boot like
> this:
>
Similar problem on x86 as well.
Serial: 8250/16550 driver, 8 ports, IRQ sharing disabled
BUG: unable to handle kernel NULL pointer dereference at 0000000000000070
IP: [<ffffffff8132d15a>] mutex_lock+0xc/0x2d
PGD 0
Oops: 0002 [#1] SMP
last sysfs file:
CPU 0
Modules linked in:
Pid: 1, comm: swapper Not tainted 2.6.31-rc4-autotest-next-20090724-5-default #1 BladeCenter LS21 -[79716AA]-
RIP: 0010:[<ffffffff8132d15a>] [<ffffffff8132d15a>] mutex_lock+0xc/0x2d
RSP: 0018:ffff88012b319da0 EFLAGS: 00010286
RAX: ffff88012b319e10 RBX: 0000000000000070 RCX: ffffffff85d06ad0
RDX: 0000000000000008 RSI: ffffffff85d06ad0 RDI: 0000000000000070
RBP: ffff88012b319db0 R08: 0000000000000001 R09: ffff88012b319d40
R10: 0000000300000000 R11: 0000000000018600 R12: ffffffff85d06ad0
R13: ffff88012846a000 R14: ffffffff8154bd00 R15: 0000000000000070
FS: 0000000000000000(0000) GS:ffff880028022000(0000) knlGS:0000000000000000
CS: 0010 DS: 0018 ES: 0018 CR0: 000000008005003b
CR2: 0000000000000070 CR3: 0000000001001000 CR4: 00000000000006f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Process swapper (pid: 1, threadinfo ffff88012b318000, task ffff88012b316000)
Stack:
ffff88012b319e10 00000000ffffffea ffff88012b319e40 ffffffff8126c572
<0> 0000000000000000 0000000000000000 ffff88012b319de0 ffffffff811e9ea7
<0> ffff8801284c6a10 ffff8801284c6a00 0000000000000000 00000000ffffffea
Call Trace:
[<ffffffff8126c572>] uart_add_one_port+0x72/0x332
[<ffffffff811e9ea7>] ? kobject_init+0x43/0x83
[<ffffffff81686a2e>] ? serial8250_init+0x0/0x143
[<ffffffff81686b2c>] serial8250_init+0xfe/0x143
[<ffffffff8100905c>] do_one_initcall+0x56/0x12b
[<ffffffff8108b3ca>] ? register_irq_proc+0xb0/0xcc
[<ffffffff81120000>] ? sys_quotactl+0x7c/0x748
[<ffffffff8165b691>] kernel_init+0x181/0x1db
[<ffffffff8100ca1a>] child_rip+0xa/0x20
[<ffffffff8165b510>] ? kernel_init+0x0/0x1db
[<ffffffff8100ca10>] ? child_rip+0x0/0x20
Code: c0 b0 b1 05 81 48 89 45 c8 48 89 45 d0 e8 1d ff ff ff 48 83 c4 40 5b 41 5c 41 5d 41 5e c9 c3 55 48 89 e5 53 48 89 fb 48 83 ec 08 <f0> ff 0f 79 05 e8 97 00 00 00 65 48 8b 04 25 b8 b4 00 00 48 2d
RIP [<ffffffff8132d15a>] mutex_lock+0xc/0x2d
RSP <ffff88012b319da0>
CR2: 0000000000000070
---[ end trace b19b3a85649e706b ]---
Thanks
-Sachin
--
---------------------------------
Sachin Sant
IBM Linux Technology Center
India Systems and Technology Labs
Bangalore, India
---------------------------------
next prev parent reply other threads:[~2009-07-24 11:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-24 7:18 linux-next: boot panic in serial init Stephen Rothwell
2009-07-24 11:05 ` Sachin Sant [this message]
2009-07-24 12:15 ` Alan Cox
2009-07-24 13:11 ` Stephen Rothwell
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=4A69955D.2040000@in.ibm.com \
--to=sachinp@in.ibm.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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.