On Fri, Jun 04, 2004 at 03:08:16PM +0200, Krzysztof Rusocki wrote:
> > Process xfsbufd (pid: 12, threadinfo=c11b0000 task=c11b5130)
> > Stack: c7e8a680 00000000 00003a98 c7871ec0 c7e8ae80 00000000 c022c3b0
> > 00000000
> > 00000000 00000000 c0102091 00000000 00000000 00000000
> > Call Trace:
> > [<c022c3b0>] pagebuf_daemon+0x0/0x1c0
> > [<c0102091>] kernel_thread_helper+0x5/0x14
> >
>
Yet again - I got that on another machine, followed by:
<3>Slab corruption: start=dfdcd130, len=1408
000: 00 00 00 00 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b
Prev obj: start=dfdccbb0, len=1408
000: 01 00 00 00 00 e0 d8 df 07 00 00 00 40 00 00 00
010: 00 00 00 00 ff ff ff ff 73 00 00 00 78 00 00 00
Next obj: start=dfdcd6b0, len=1408
000: 01 00 00 00 00 00 d0 81 07 00 00 00 40 80 00 00
010: 00 00 00 00 ff ff ff ff 69 00 00 00 6e 00 00 00
Can it be CONFIG_SLAB_DEBUG which is doing harm here?
- it was =y in both .configs. I'm out of ideas
so maybe someone can shed some light on this?
I've just built 2.6.7 without CONFIG_SLAB_DEBUG and
will let you know how long it gets. What may be worth
mentioning - previous 2.6 kernels I used did not exhibit
such problems and I'm pretty sure that they had slab
debugging enabled.
Cheers,
Krzysztof
|