From: Srikar Dronamraju on
When I updated my tip/master and rebooted into it, I am seeing a panic on boot.


Here is the ooops message. (x86_64 box)

PCI: MMCONFIG for domain 0000 [bus 00-2e] at [mem 0xd0000000-0xd2efffff] (base 0xd0000000)
PCI: MMCONFIG at [mem 0xd0000000-0xd2efffff] reserved in E820
------------[ cut here ]------------
kernel BUG at lib/ioremap.c:26!
invalid opcode: 0000 [#1] SMP
last sysfs file:
CPU 0
Modules linked in:

Pid: 1, comm: swapper Not tainted 2.6.35-rc2-tip-uprobes+ #8 Node1 Processor Card/IBM 3850 M2 / x3950 M2 -[71414RA]-
RIP: 0010:[<ffffffff811a1d25>] [<ffffffff811a1d25>] ioremap_page_range+0x1c5/0x248
RSP: 0018:ffff88083cd39d80 EFLAGS: 00010286
RAX: 00000000d0180000 RBX: ffffc90003200000 RCX: ffff88083cf99000
RDX: 0000000000000000 RSI: 00000000000001ba RDI: ffffffff817a0c90
RBP: ffff88083cd39de0 R08: 0000000000000004 R09: ffffffff817bf578
R10: ffff88083cf99000 R11: 0000000000000002 R12: ffffc90005f80000
R13: ffffc90003400000 R14: ffffffff817a0c90 R15: ffff88083fc0c0c8
FS: 0000000000000000(0000) GS:ffff880002e00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
CR2: 000000001fd69a10 CR3: 00000000017a0000 CR4: 00000000000006f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Process swapper (pid: 1, threadinfo ffff88083cd38000, task ffff88083cd30000)
Stack:
ffff88083cd39da0 00000000d0000000 ffffc90005f80000 ffffc90005f80000
<0> ffff88083fc07000 8000000000000573 000036fffcf80000 0000000002f00000
<0> ffff88083cdd6aa0 ffffc90003080000 00000000d0000000 00000000d0000000
Call Trace:
[<ffffffff810262e5>] __ioremap_caller+0x295/0x30e
[<ffffffff81a583a3>] ? pci_mmcfg_arch_init+0x33/0x9d
[<ffffffff81a59005>] ? pci_parse_mcfg+0x109/0x130
[<ffffffff81a582bb>] ? pci_arch_init+0x0/0x69
[<ffffffff810263fb>] ioremap_nocache+0x17/0x19
[<ffffffff81a583a3>] pci_mmcfg_arch_init+0x33/0x9d
[<ffffffff81a58da4>] __pci_mmcfg_init+0x1c0/0x1ea
[<ffffffff8124057b>] ? device_register+0x1e/0x22
[<ffffffff81a58de9>] pci_mmcfg_early_init+0xe/0x10
[<ffffffff81a582d9>] pci_arch_init+0x1e/0x69
[<ffffffff810001f2>] do_one_initcall+0x57/0x13c
[<ffffffff81a27934>] kernel_init+0x14c/0x1d6
[<ffffffff81003954>] kernel_thread_helper+0x4/0x10
[<ffffffff813625fc>] ? restore_args+0x0/0x30
[<ffffffff81a277e8>] ? kernel_init+0x0/0x1d6
[<ffffffff81003950>] ? kernel_thread_helper+0x0/0x10
Code: 89 da 48 c1 ea 09 48 89 c1 81 e2 f8 0f 00 00 48 01 d1 74 49 48 8b 45 a8 48 03 45 d0 48 01 d8 48 25 00 f0 ff ff 48 83 39 00 74 04 <0f> 0b eb fe 48 8b 55 c8 f6 c2 01 74 07 48 23 15 47 aa 6a 00 48
RIP [<ffffffff811a1d25>] ioremap_page_range+0x1c5/0x248
RSP <ffff88083cd39d80>
---[ end trace 4eaa2a86a8e2da22 ]---


$ git log tip_master --pretty=oneline |head -n 10
1e6d1f4ce66b60d7b5046dd0de6693309f61b6fa Merge branch 'linus'
9370a9525e3661295d478de657f53008ba4232c5 Merge branch 'x86/urgent'
c171adb13ab5ccba9525662ca6cc1b6608a846f5 Merge branch 'x86/cpu'
43e9742305bcbcd1d02d6b9f2e5ac2798ae1d5a7 Merge branch 'x86/alternatives'
f88731e3068f9d1392ba71cc9f50f035d26a0d4f x86, alternatives: Use 16-bit numbers for cpufeature index
12d8a961289644d265d8b3e88201878837c3b814 x86, AMD: Extend support to future families
8cc1176e5de534d55cb26ff0cef3fd0d6ad8c3c0 x86, cacheinfo: Carve out L3 cache slot accessors
d6d4d4205cf4ce4ba13bc320305afbda25303496 x86, xsave: Cleanup return codes in check_for_xstate()
cc7f0a7b3004a4ca0bfef0e1ca79f2e0da6ca1b0 x86, hweight: Fix UML boot crash
a4384df3e24579d6292a1b3b41d500349948f30b x86, irq: Rename gsi_end gsi_top, and fix off by one errors


previously it booted well with commit
a2e42da15c9c72bc7caf9e494d409819babbc9c8

--
Thanks and Regards
Srikar
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
From: H. Peter Anvin on
On 06/10/2010 04:28 AM, Srikar Dronamraju wrote:
> When I updated my tip/master and rebooted into it, I am seeing a panic on boot.
>
>
> Here is the ooops message. (x86_64 box)
>
>
> previously it booted well with commit
> a2e42da15c9c72bc7caf9e494d409819babbc9c8
>

Any way you could run a bisect between these commits?

-hpa


--
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel. I don't speak on their behalf.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
From: Srikar Dronamraju on
> On 06/10/2010 04:28 AM, Srikar Dronamraju wrote:
> > When I updated my tip/master and rebooted into it, I am seeing a panic on boot.
> >
> >
> > Here is the ooops message. (x86_64 box)
> >
> >
> > previously it booted well with commit
> > a2e42da15c9c72bc7caf9e494d409819babbc9c8
> >
>
> Any way you could run a bisect between these commits?
>
> -hpa


Now sure I got to those commit id's. Those don't seem to be present in
the git log when I grep today. And I am able to boot the system with today's
tip tree.

I am extremely sorry for the noise.

--
Thanks and Regards
Srikar
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
From: Ingo Molnar on

* Srikar Dronamraju <srikar(a)linux.vnet.ibm.com> wrote:

> > Any way you could run a bisect between these commits?
>
> Now sure I got to those commit id's. Those don't seem to be present in the
> git log when I grep today. And I am able to boot the system with today's tip
> tree.
>
> I am extremely sorry for the noise.

Not noise at all! Yesternight i triggered a different boot crash myself and
bisected it down to:

f88731e3068f9d1392ba71cc9f50f035d26a0d4f x86, alternatives: Use 16-bit numbers for cpufeature index

.... which was included in your git log as well.

So i am quite sure that commit has caused your boot crash as well!

Thanks,

Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
From: Maciej Rutecki on
On czwartek, 10 czerwca 2010 o 13:28:39 Srikar Dronamraju wrote:
> When I updated my tip/master and rebooted into it, I am seeing a panic on
> boot.
>
I created a Bugzilla entry at
https://bugzilla.kernel.org/show_bug.cgi?id=16208
for your bug report, please add your address to the CC list in there, thanks!


--
Maciej Rutecki
http://www.maciek.unixy.pl
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/