From: Jesse Barnes
Date: Wed Mar 31 2004 - 19:01:06 EST
On Wednesday 31 March 2004 3:56 pm, Andrew Morton wrote:
> Jesse Barnes <jbarnes@xxxxxxx> wrote:
> > On Wednesday 31 March 2004 12:06 pm, Andrew Morton wrote:
> > > So are we to assume that this is the offending process? That the
> > > periodic slab reaping code has screwed up?
> > It looks like it. Disabling the slab cache reaping function allows it to
> > boot again.
> I suspect that the reap timer is innocent and what we have is simply
> scribbled-on slab metadata. Which means it could be anything at all.
That's what I thought too, I'm trying to track down exactly which slab is
having problems now.
> One last thing: could you please stick a
> printk(KERN_EMERG "destroying slab %s\n", cachep->name);
I'm already booting up something similar...
> at the start of slab_destroy()? That'll help narrow it down.
> Could you also punt me over the .config? If I can make it happen, the
> binary search will find it. But it probably won't happen here.
I'm using sn2_defconfig in arch/ia64/configs.
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/