From: Nigel Cunningham <ncunningham@crca.org.au>
To: Pedro Ribeiro <pedrib@gmail.com>
Cc: linux-kernel@vger.kernel.org,
Christoph Lameter <cl@linux-foundation.org>,
Pekka Enberg <penberg@cs.helsinki.fi>,
Matt Mackall <mpm@selenic.com>,
"linux-mm@kvack.org >> linux-mm" <linux-mm@kvack.org>
Subject: Re: BUG at mm/slab.c:2990 with 2.6.33-rc5-tuxonice
Date: Wed, 27 Jan 2010 07:39:26 +1100 [thread overview]
Message-ID: <4B5F52FE.5000201@crca.org.au> (raw)
In-Reply-To: <74fd948d1001261121r7e6d03a4i75ce40705abed4e0@mail.gmail.com>
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.
Regards,
Nigel
--
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 parent reply other threads:[~2010-01-26 20:37 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 ` Nigel Cunningham [this message]
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
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=4B5F52FE.5000201@crca.org.au \
--to=ncunningham@crca.org.au \
--cc=cl@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mpm@selenic.com \
--cc=pedrib@gmail.com \
--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