Re: [BUG][Resend] 2.6.12-rc3-mm3: Kernel BUG at "mm/slab.c":1219

[Jens Axboe <axboe@suse.de>]

On Tue, May 10 2005, Alexander Nyberg wrote:
> tis 2005-05-10 klockan 08:18 +0200 skrev Jens Axboe:
> > On Mon, May 09 2005, Andi Kleen wrote:
> > > On Mon, May 09, 2005 at 10:39:37PM +0200, Rafael J. Wysocki wrote:
> > > > Hi,
> > > > 
> > > > I get this from 2.6.12-rc3-mm3 on a UP AMD64 box (Asus L5D), 100% of the time:
> > > 
> > > Probably a generic bug. Block layer is passing some slab flag slab
> > > doesn't like.
> > 
> > Some slab change, perhaps? There's nothing special about the init_bio()
> > slab call:
> > 
> >         bio_slab = kmem_cache_create("bio", sizeof(struct bio), 0,
> >                             SLAB_HWCACHE_ALIGN|SLAB_PANIC, NULL, NULL);
> > 
> > 
> > Hmm, this looks strange. That bug happens if:
> > 
> >         if ((!name) ||
> >                 in_interrupt() ||
> >                 (size < BYTES_PER_WORD) ||
> >                 (size > (1<<MAX_OBJ_ORDER)*PAGE_SIZE) ||
> >                 (dtor && !ctor)) {
> >                         printk(KERN_ERR "%s: Early error in slab %s\n",
> >                                         __FUNCTION__, name);
> >                         BUG();
> >                 }
> > 
> > It must be in_interrupt() triggering, perhaps something change in the
> > boot sequence?
> > 
> 
> The funny thing is that it seems to be the name being NULL, from the
> original post:
> kmem_cache_create: Early error in slab <NULL>
> 
> When looking at the code I really can't see how that can be. Rafael,
> what setup is this compiled under?

Huh indeed, smells like bad code generation or hardware.

-- 
Jens Axboe

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