Re: 2.6.21-mm1 and now 2.6.21-git: SLUB Crashes on boot

[Christoph Lameter]

On Tue, 8 May 2007, Kevin Winchester wrote:

> [    1.376783]  [<ffffffff8067d664>] kernel_init+0xc4/0x2a0
> [    1.376857]  [<ffffffff802080aa>] __switch_to+0x2a/0x2d0
> [    1.376932]  [<ffffffff8020a5d8>] child_rip+0xa/0x12
> [    1.377006]  [<ffffffff8067d5a0>] kernel_init+0x0/0x2a0
> [    1.377080]  [<ffffffff8020a5ce>] child_rip+0x0/0x12
> [    1.377151]
> [    1.377221] @@@ SLUB kmalloc-256: Restoring Poison (0x6b) from
> 0xffff810001bdecd0-0xffff810001bdedce
> [    1.377326] @@@ SLUB kmalloc-256: Restoring Poison (0xa5) from
> 0xffff810001bdedcf-0xffff810001bdedcf
> [    1.377430] @@@ SLUB: kmalloc-256 slab 0xffff810001061890. Marking all
> objects used.


There is more... The above describes the repair actions that were taken by 
SLUB. Poison was restored and then the slab was taken out of circulation 
since pointers may still exist that may damage additional objects if used 
to store more data.


-
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/