From: Simon Arlott <simon@fire.lp0.eu>
To: Pekka Enberg <penberg@cs.helsinki.fi>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
akpm <akpm@linux-foundation.org>,
Christoph Lameter <cl@linux-foundation.org>
Subject: Re: BUG in free_block (tainted)
Date: Mon, 18 Aug 2008 22:42:42 +0100 [thread overview]
Message-ID: <48A9ECD2.8030801@simon.arlott.org.uk> (raw)
In-Reply-To: <84144f020808181437n34f3a339j3392ccccfdfd60f9@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 889 bytes --]
On 18/08/08 22:37, Pekka Enberg wrote:
> Hi Simon,
>
> On Tue, Aug 19, 2008 at 12:28 AM, Simon Arlott <simon@fire.lp0.eu> 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 #2: x.bz2 --]
[-- Type: application/x-bzip, Size: 3852 bytes --]
next prev parent reply other threads:[~2008-08-18 21:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-18 21:28 BUG in free_block (tainted) Simon Arlott
2008-08-18 21:37 ` Pekka Enberg
2008-08-18 21:42 ` Simon Arlott [this message]
2008-08-18 21:49 ` Pekka Enberg
2008-08-19 13:02 ` Christoph Lameter
2008-08-21 10:48 ` Peter Zijlstra
2008-08-21 10:51 ` Pekka Enberg
2008-08-22 15:21 ` Adrian Bunk
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=48A9ECD2.8030801@simon.arlott.org.uk \
--to=simon@fire.lp0.eu \
--cc=akpm@linux-foundation.org \
--cc=cl@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=penberg@cs.helsinki.fi \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.