From: Pedro Ribeiro <pedrib@gmail.com>
To: Pekka Enberg <penberg@cs.helsinki.fi>
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: Tue, 26 Jan 2010 23:31:11 +0000 [thread overview]
Message-ID: <74fd948d1001261531v7a09e1e8t54a7a5a5a2df277b@mail.gmail.com> (raw)
In-Reply-To: <74fd948d1001261350n2f26c057ubbe056d11d19abf2@mail.gmail.com>
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.
Do you know if/where I can get patches for KDB in .33?
Regards,
Pedro
--
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-26 23:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <74fd948d1001261121r7e6d03a4i75ce40705abed4e0@mail.gmail.com>
2010-01-26 20:39 ` BUG at mm/slab.c:2990 with 2.6.33-rc5-tuxonice Nigel Cunningham
2010-01-26 20:50 ` Matt Mackall
2010-01-26 20:59 ` Pekka Enberg
2010-01-26 21:35 ` Christoph Lameter
2010-01-26 21:50 ` Pedro Ribeiro
2010-01-26 23:31 ` Pedro Ribeiro [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=74fd948d1001261531v7a09e1e8t54a7a5a5a2df277b@mail.gmail.com \
--to=pedrib@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).