Re: BUG in free_block (tainted)

From: Simon Arlott
Date: Mon Aug 18 2008 - 17:42:59 EST


On 18/08/08 22:37, Pekka Enberg wrote:
Hi Simon,

On Tue, Aug 19, 2008 at 12:28 AM, Simon Arlott <simon@xxxxxxxxxxx> wrote:
http://img169.imageshack.us/img169/1170/1005548cp9.jpg

2.6.27-rc3 09873-gb08c7f5

(Tainted with fglrx, but X hadn't been run...)

Looks like SLAB corruption so fglrx could have caused this even if you
just loaded the module. Do you have CONFIG_DEBUG_SLAB enabled? If not,
you might want to try to reproduce this with it. Of course,
reproducing the oops without fglrx would be most helpful. :-)

In that case please disregard this completely. It's not yet happened again.

fglrx completely breaks slab in fantastic ways... I could show you my /proc/slabinfo... the start of it is badly corrupted - but only if X has been started (attached).

I might try enabling CONFIG_DEBUG_SLAB, perhaps it can detect that bug...

--
Simon Arlott

Attachment: x.bz2
Description: application/bzip