__build_sched_domains panic
Hi, Andrew,
I have an x86_64 system with 4 CPUs and 4GB memory and I see the following panic, when I boot with fake NUMA nodes. I am still investigating the problem. I was trying to use this setup to verify KAMEZAWA's fix for the memcgroup page migration problem.
BUG: unable to handle kernel paging request at 0000007800000020 IP: [<ffffffff8029dd04>] ____cache_alloc_node+0x62/0x133 PGD 0 Oops: 0000 [1] SMP DEBUG_PAGEALLOC last sysfs file: CPU 0 Modules linked in: Pid: 1, comm: swapper Not tainted 2.6.26-rc5-mm1 #1 RIP: 0010:[<ffffffff8029dd04>] [<ffffffff8029dd04>] ____cache_alloc_node+0x62/0x133 RSP: 0000:ffff8100bfdebd30 EFLAGS: 00010007 RAX: ffff81007fdea040 RBX: 0000007800000000 RCX: ffff81007fdea730 RDX: 0000000000000000 RSI: ffff81003fc5d858 RDI: ffff81007fdea040 RBP: ffff8100bfdebd60 R08: 0000000000000004 R09: ffff81003fc5d858 R10: ffff8100000be400 R11: ffff8100bfdeb8b0 R12: ffff81003fc5d800 R13: ffff81003fc40400 R14: 000000000000000b R15: ffff81003fc5d840 FS: 0000000000000000(0000) GS:ffffffff807d9a00(0000) knlGS:0000000000000000 CS: 0010 DS: 0018 ES: 0018 CR0: 000000008005003b CR2: 0000007800000020 CR3: 0000000000201000 CR4: 00000000000006e0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400 Process swapper (pid: 1, threadinfo ffff8100bfdea000, task ffff81007fdea040) Stack: 000000d00000003f ffff8100bfe19780 000000000000000b 0000000000000246 ffff81003fc40400 00000000000000d0 ffff8100bfdebda0 ffffffff8029d813 ffff810081c13ca0 ffff8100bfe19780 ffff8100bfdebdf8 0000000000000004 Call Trace: [<ffffffff8029d813>] kmem_cache_alloc_node+0xc6/0x10e [<ffffffff8022fbb4>] __build_sched_domains+0x51d/0x7bd [<ffffffff80254a6a>] ? trace_hardirqs_on+0xd/0xf [<ffffffff80230299>] arch_init_sched_domains+0x63/0x70 [<ffffffff807fe908>] sched_init_smp+0x4c/0x107 [<ffffffff807eb916>] kernel_init+0xf9/0x2be [<ffffffff80254a32>] ? trace_hardirqs_on_caller+0xf9/0x124 [<ffffffff80254a6a>] ? trace_hardirqs_on+0xd/0xf [<ffffffff805a9ad7>] ? _spin_unlock_irq+0x2b/0x30 [<ffffffff805a9305>] ? trace_hardirqs_on_thunk+0x3a/0x3f [<ffffffff80254a32>] ? trace_hardirqs_on_caller+0xf9/0x124 [<ffffffff8020c158>] child_rip+0xa/0x12 [<ffffffff8020b86f>] ? restore_args+0x0/0x30 [<ffffffff807eb81d>] ? kernel_init+0x0/0x2be [<ffffffff8020c14e>] ? child_rip+0x0/0x12 Code: f4 b9 30 00 49 8b 1c 24 4c 39 e3 75 1e 48 8b 53 20 48 8d 43 20 c7 83 90 00
00 00 01 00 00 00 48 39 c2 0f 84 91 00 00 00 48 89 d3 <8b> 43 20 41 3b 85 18 01 00 00 75 04 0f 0b eb fe 44 89 f2 4c 89
RIP [<ffffffff8029dd04>] ____cache_alloc_node+0x62/0x133
RSP <ffff8100bfdebd30>
CR2: 0000007800000020
Signature · 4 lines
Warm Regards, Balbir Singh Linux Technology Center IBM, ISTL
Quoted 6 lines · Balbir Singh
Hi, Andrew,
I have an
x86_64system with 4 CPUs and 4GB memory and I see the following panic, when I boot with fake NUMA nodes. I am still investigating the problem. I was trying to use this setup to verify KAMEZAWA's fix for the memcgroup page migration problem.
Hi :)
This is already fixed. Actually, it was just caused by a missing patch.
You need a953e4597abd51b74c99e0e3b7074532a60fd031 from the -tip tree.
Vegard
Signature · 4 lines
"The animistic metaphor of the bug that maliciously sneaked in while the programmer was not looking is intellectually dishonest as it disguises that the error is the programmer's own creation." -- E. W. Dijkstra, EWD1036
Quoted 8 lines · Vegard Nossum
Quoted 6 lines · Balbir Singh
Hi, Andrew,
I have an
x86_64system with 4 CPUs and 4GB memory and I see the following panic, when I boot with fake NUMA nodes. I am still investigating the problem. I was trying to use this setup to verify KAMEZAWA's fix for the memcgroup page migration problem.
Quoted 5 lines
Hi :)
This is already fixed. Actually, it was just caused by a missing patch.
You need
a953e4597abd51b74c99e0e3b7074532a60fd031from the -tip tree.
Thanks for the update!
Signature · 4 lines
Warm Regards, Balbir Singh Linux Technology Center IBM, ISTL