Hi Simon,

On Tue, Aug 19, 2008 at 12:28 AM, Simon Arlott <simon@fire.lp0.eu> wrote:
quoted text
>>> http://img169.imageshack.us/img169/1170/1005548cp9.jpg
>>>
>>> 2.6.27-rc3 09873-gb08c7f5
>>>
>>> (Tainted with fglrx, but X hadn't been run...)

On 18/08/08 22:37, Pekka Enberg wrote:
quoted text
>> 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. :-)

On Tue, Aug 19, 2008 at 12:42 AM, Simon Arlott <simon@fire.lp0.eu> wrote:
quoted text
> 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...

Aww, apparently the fglrx driver creates tons of SLAB caches with
really funky names for no good reason... Oh well, one more reason to
stay away from that crap and help out the nouveau folks instead ;-).

                         Pekka
--
unsubscribe notice
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/