From: Pekka Enberg <penberg@cs.helsinki.fi>
To: Pedro Ribeiro <pedrib@gmail.com>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: BUG at mm/slab.c:2990 with 2.6.33-rc5-tuxonice
Date: Wed, 27 Jan 2010 10:02:15 +0200 [thread overview]
Message-ID: <4B5FF307.9080900@cs.helsinki.fi> (raw)
In-Reply-To: <74fd948d1001261531v7a09e1e8t54a7a5a5a2df277b@mail.gmail.com>
Pedro Ribeiro kirjoitti:
> 2010/1/26 Pedro Ribeiro <pedrib@gmail.com>:
>> 2010/1/26 Pekka Enberg <penberg@cs.helsinki.fi>:
>>> Matt Mackall wrote:
>>>> On Wed, 2010-01-27 at 07:39 +1100, Nigel Cunningham wrote:
>>>>> Hi.
>>>>>
>>>>> Pedro Ribeiro wrote:
>>>>>> Hi,
>>>>>>
>>>>>> I hit a bug at mm/slab.c:2990 with .33-rc5.
>>>>>> Unfortunately nothing more is available than a screen picture with a
>>>>>> crash dump, although it is a good one.
>>>>>> The bug was hit almost at the end of a hibernation cycle with
>>>>>> Tux-on-Ice, while saving memory contents to an encrypted swap
>>>>>> partition.
>>>>>>
>>>>>> The image is here http://img264.imageshack.us/img264/9634/mmslab.jpg
>>>>>> (150 kb)
>>>>>>
>>>>>> Hopefully it is of any use for you. Please let me know if you need any
>>>>>> more info.
>>>>> Looks to me to be completely unrelated to TuxOnIce - at least at a first
>>>>> glance.
>>>>>
>>>>> Ccing the slab allocator maintainers listed in MAINTAINERS.
>>>> Not sure if this will do us any good, it's the second oops.
>>> Looks like slab corruption to me which is usually not a slab bug but caused
>>> by buggy callers. Is CONFIG_DEBUG_SLAB enabled?
>>>
>> I have enabled it and compiled the kernel. As soon as I hit the bug, I
>> will send a photo here.
>>
>> Regards,
>> Pedro
>>
>
> The pic is here.
> http://img43.imageshack.us/img43/3644/dsc01061ko.jpg
>
> There was a buttload of output before that, which I tried capturing in
> video, but its too crappy to post.
Can you try passing "pause_on_oops=15" as kernel parameter? It should
delay the next oops for 15 seconds so there's enough time to take a
picture of the first one?
Also, you could try CONFIG_SLUB and passing "slub_debug" as kernel
parameter to get nicer diagnostics of the bug.
> Do you know if/where I can get patches for KDB in .33?
Nope, sorry.
Pekka
WARNING: multiple messages have this Message-ID (diff)
From: Pekka Enberg <penberg@cs.helsinki.fi>
To: Pedro Ribeiro <pedrib@gmail.com>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: BUG at mm/slab.c:2990 with 2.6.33-rc5-tuxonice
Date: Wed, 27 Jan 2010 10:02:15 +0200 [thread overview]
Message-ID: <4B5FF307.9080900@cs.helsinki.fi> (raw)
In-Reply-To: <74fd948d1001261531v7a09e1e8t54a7a5a5a2df277b@mail.gmail.com>
Pedro Ribeiro kirjoitti:
> 2010/1/26 Pedro Ribeiro <pedrib@gmail.com>:
>> 2010/1/26 Pekka Enberg <penberg@cs.helsinki.fi>:
>>> Matt Mackall wrote:
>>>> On Wed, 2010-01-27 at 07:39 +1100, Nigel Cunningham wrote:
>>>>> Hi.
>>>>>
>>>>> Pedro Ribeiro wrote:
>>>>>> Hi,
>>>>>>
>>>>>> I hit a bug at mm/slab.c:2990 with .33-rc5.
>>>>>> Unfortunately nothing more is available than a screen picture with a
>>>>>> crash dump, although it is a good one.
>>>>>> The bug was hit almost at the end of a hibernation cycle with
>>>>>> Tux-on-Ice, while saving memory contents to an encrypted swap
>>>>>> partition.
>>>>>>
>>>>>> The image is here http://img264.imageshack.us/img264/9634/mmslab.jpg
>>>>>> (150 kb)
>>>>>>
>>>>>> Hopefully it is of any use for you. Please let me know if you need any
>>>>>> more info.
>>>>> Looks to me to be completely unrelated to TuxOnIce - at least at a first
>>>>> glance.
>>>>>
>>>>> Ccing the slab allocator maintainers listed in MAINTAINERS.
>>>> Not sure if this will do us any good, it's the second oops.
>>> Looks like slab corruption to me which is usually not a slab bug but caused
>>> by buggy callers. Is CONFIG_DEBUG_SLAB enabled?
>>>
>> I have enabled it and compiled the kernel. As soon as I hit the bug, I
>> will send a photo here.
>>
>> Regards,
>> Pedro
>>
>
> The pic is here.
> http://img43.imageshack.us/img43/3644/dsc01061ko.jpg
>
> There was a buttload of output before that, which I tried capturing in
> video, but its too crappy to post.
Can you try passing "pause_on_oops=15" as kernel parameter? It should
delay the next oops for 15 seconds so there's enough time to take a
picture of the first one?
Also, you could try CONFIG_SLUB and passing "slub_debug" as kernel
parameter to get nicer diagnostics of the bug.
> Do you know if/where I can get patches for KDB in .33?
Nope, sorry.
Pekka
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2010-01-27 8:02 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-26 19:21 BUG at mm/slab.c:2990 with 2.6.33-rc5-tuxonice Pedro Ribeiro
2010-01-26 20:39 ` Nigel Cunningham
2010-01-26 20:39 ` Nigel Cunningham
2010-01-26 20:50 ` Matt Mackall
2010-01-26 20:50 ` Matt Mackall
2010-01-26 20:59 ` Pekka Enberg
2010-01-26 20:59 ` Pekka Enberg
2010-01-26 21:35 ` Christoph Lameter
2010-01-26 21:35 ` Christoph Lameter
2010-01-26 21:50 ` Pedro Ribeiro
2010-01-26 21:50 ` Pedro Ribeiro
2010-01-26 23:31 ` Pedro Ribeiro
2010-01-26 23:31 ` Pedro Ribeiro
2010-01-27 8:02 ` Pekka Enberg [this message]
2010-01-27 8:02 ` Pekka Enberg
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=4B5FF307.9080900@cs.helsinki.fi \
--to=penberg@cs.helsinki.fi \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=pedrib@gmail.com \
/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.