Re: 2.6.24-rc3-mm1 - Kernel Panic on IO-APIC

Rik van Riel
2007-11-26T20:55:28Z

On Mon, 26 Nov 2007 12:33:19 -0800
Andrew Morton <akpm@linux-foundation.org> wrote:

> > Unable to handle kernel NULL pointer dereference at 0000000000000021 RIP:
> > [<ffffffff8108382a>] refresh_zone_stat_thresholds+0x6d/0x90
> > PGD 0
> > Oops: 0002 [1] SMP
> > last sysfs file:
> > CPU 0
> > Modules linked in:
> > Pid: 1, comm: swapper Not tainted 2.6.24-rc3-mm1 #2
> > RIP: 0010:[<ffffffff8108382a>] [<ffffffff8108382a>] refresh_zone_stat_thresholds+0x6d/0x90
> > RSP: 0000:ffff81007fb59ec0 EFLAGS: 00010293
> > RAX: 0000000000000000 RBX: 0000000000000004 RCX: 0000000000000001
> > RDX: 0000000000000001 RSI: ffffffff8146fb38 RDI: 0000000000000001
> > RBP: ffff81000000c000 R08: 0000000000000000 R09: 0000000000000000
> > R10: ffff81007fb59e60 R11: 0000000000000028 R12: ffffffff814d4558
> > R13: 0000000000000000 R14: ffffffff814b62c0 R15: 0000000000000000
> > FS: 0000000000000000(0000) GS:ffffffff813d9000(0000) knlGS:0000000000000000
> > CS: 0010 DS: 0018 ES: 0018 CR0: 000000008005003b
> > CR2: 0000000000000021 CR3: 0000000000201000 CR4: 00000000000006a0
> > DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
> > DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
> > Process swapper (pid: 1, threadinfo FFFF81007FB58000, task FFFF81007FB56000)
> > Stack: 0000000000000000 0000000000000000 0000000000000000 ffffffff814a3839
> > 0000000000000000 ffffffff8148e626 ffff81007fb56000 ffffffff8126d36a
> > 0000000000000000 ffffffffffffffff ffffffff8105786b 0000000000000000
> > Call Trace:
> > [<ffffffff814a3839>] setup_vmstat+0x6/0x40
> > [<ffffffff8148e626>] kernel_init+0x169/0x2d8
> > [<ffffffff8126d36a>] trace_hardirqs_on_thunk+0x35/0x3a
> > [<ffffffff8105786b>] trace_hardirqs_on+0x115/0x138
> > [<ffffffff8100ce48>] child_rip+0xa/0x12
> > [<ffffffff8100c55f>] restore_args+0x0/0x30
> > [<ffffffff8148e4bd>] kernel_init+0x0/0x2d8
> > [<ffffffff8100ce3e>] child_rip+0x0/0x12
> >
> > INFO: lockdep is turned off.
>
> hm. This smells like a startup ordering problem, but everything which
> refresh_zone_stat_thresholds() should be set up by the time we run
> initcalls. Maybe the zone lists are bad?

Or the CPU array. Look at the oops Kamalesh got a few mails upthread...

I guess I'll have to start a bisect - can't port the VM code to a kernel
that doesn't boot...

--
All Rights Reversed