Re: 2.6.18-mm2 boot failure on x86-64 II

From: keith mannthey
Date: Thu Oct 05 2006 - 19:58:57 EST


On Fri, 2006-10-06 at 01:35 +0200, Andi Kleen wrote:
> > As of yet I haven't been able to recreate the hang. I am running
> > similar HW to Steve.

I ran into this with -mm3

Memory: 24150368k/26738688k available (1933k kernel code, 490260k
reserved, 978k data, 308k init)
------------[ cut here ]------------
kernel BUG in init_list at mm/slab.c:1334!
invalid opcode: 0000 [1] SMP
last sysfs file:
CPU 0
Modules linked in:
Pid: 0, comm: swapper Not tainted 2.6.18-mm3-smp #1
RIP: 0010:[<ffffffff8027f8fa>] [<ffffffff8027f8fa>] init_list+0x1d/0xfd
RSP: 0018:ffffffff80577f48 EFLAGS: 00010212
RAX: 0000000000000040 RBX: 0000000000000001 RCX: 0000000000000000
RDX: 0000000000000001 RSI: ffffffff805ba848 RDI: ffff810460700040
RBP: 0000000000000001 R08: 0000000000000001 R09: 0000000000000003
R10: 0000000000000000 R11: ffffffff805bc268 R12: ffff810460700040
R13: ffffffff805ba848 R14: 0000000000000000 R15: 0000000000000000
FS: 0000000000000000(0000) GS:ffffffff804d8000(0000)
knlGS:0000000000000000
CS: 0010 DS: 0018 ES: 0018 CR0: 000000008005003b
CR2: 0000000000000000 CR3: 0000000000201000 CR4: 00000000000006a0
Process swapper (pid: 0, threadinfo ffffffff80576000, task
ffffffff80455840)
Stack: 0000000000000000 0000000000000000 0000000100000000
0000000000000001
ffffffff805ba848 0000000000000000 0000000000000000 ffffffff80593aa8
00000000000002c0 0000000100000001 000000000008ef00 000000000008c000
Call Trace:
[<ffffffff80593aa8>] kmem_cache_init+0x344/0x406
[<ffffffff805805ef>] start_kernel+0x180/0x21b
[<ffffffff8058016a>] _sinittext+0x16a/0x16e


Code: 0f 0b 48 8b 3d 15 ab 1e 00 be d0 00 00 00 e8 c0 f5 ff ff 48
RIP [<ffffffff8027f8fa>] init_list+0x1d/0xfd
RSP <ffffffff80577f48>
<0>Kernel panic - not syncing: Attempted to kill the idle task!


I am going to revert the patch and see if it works. I ran -git22 just
fine.

Thanks,
Keith

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/