From: Andrew Watts <akwatts@ymail.com>
To: Christoph Lameter <cl@linux.com>
Cc: Jan Kara <jack@suse.cz>,
linux-kernel@vger.kernel.org, linux-ext4@vger.kernel.org,
linux-mm@kvack.org
Subject: Re: [OOPS]: Kernel 3.1 (ext3?)
Date: Tue, 22 Nov 2011 06:42:49 -0500 [thread overview]
Message-ID: <20111122114247.GB20081@zeus> (raw)
In-Reply-To: <alpine.DEB.2.00.1111151004050.22502@router.home>
On Tue, Nov 15, 2011 at 10:05:25AM -0600, Christoph Lameter wrote:
> On Mon, 14 Nov 2011, Jan Kara wrote:
>
> > On Thu 10-11-11 08:29:37, Andrew Watts wrote:
> > > I had the following kernel panic today on 3.1 (machine was compiling code
> > > unattended). It would appear to be a bug/regression introduced sometime
> > > between 2.6.39.4 and 3.1.
> > 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.
>
> Likely some data corruption. Enable slub debugging by passing
>
> slub_debug
>
> on the kernel commandline please to get some information as to where and
> when this happens.
>
Hi Christoph.
Thank you for your reply. I'll enable slub debugging and post anything of
interest.
~ Andy
--
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/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2011-11-22 11:42 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
2011-11-15 16:05 ` Christoph Lameter
2011-11-22 11:42 ` Andrew Watts [this message]
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=20111122114247.GB20081@zeus \
--to=akwatts@ymail.com \
--cc=cl@linux.com \
--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).