From: Andrew Watts <akwatts@ymail.com>
To: Jan Kara <jack@suse.cz>
Cc: linux-kernel@vger.kernel.org, linux-ext4@vger.kernel.org,
Christoph Lameter <cl@linux-foundation.org>,
linux-mm@kvack.org
Subject: Re: [OOPS]: Kernel 3.1 (ext3?)
Date: Mon, 14 Nov 2011 15:53:24 -0500 [thread overview]
Message-ID: <20111114205304.GA5542@zeus> (raw)
In-Reply-To: <20111114195352.GB17328@quack.suse.cz>
On Mon, Nov 14, 2011 at 08:53:52PM +0100, Jan Kara wrote:
> Hmm, the report is missing a line (top one) saying why the kernel
> actually crashed. Can you add that?
>
> Also it seems you are using SLUB allocator, right? This seems like a
> problem there so adding some CCs.
Hi Jan.
Unfortunately, the oops trace is a transcription of all that was left on
my screen. I hope that can provide enough clues into what is going on.
Yes, I use the SLUB allocator.
Thank you for your reply and for adding revelant cc's.
~ Andy
next prev parent reply other threads:[~2011-11-14 20:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-10 13:29 [OOPS]: Kernel 3.1 (ext3?) Andrew Watts
2011-11-14 19:53 ` Jan Kara
2011-11-14 20:53 ` Andrew Watts [this message]
2011-11-15 16:05 ` Christoph Lameter
2011-11-22 11:42 ` Andrew Watts
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=20111114205304.GA5542@zeus \
--to=akwatts@ymail.com \
--cc=cl@linux-foundation.org \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
/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).