From: Jens Axboe <jens.axboe@oracle.com>
To: Christoph Lameter <clameter@sgi.com>
Cc: Hugh Dickins <hugh@veritas.com>,
Srihari Vijayaraghavan <sriharivijayaraghavan@yahoo.com.au>,
Oliver Xymoron <oxymoron@waste.org>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PROBLEM] 2.6.22-rc2 panics on x86-64 with slub
Date: Mon, 21 May 2007 21:26:56 +0200 [thread overview]
Message-ID: <20070521192656.GC4705@kernel.dk> (raw)
In-Reply-To: <Pine.LNX.4.64.0705211208270.27129@schroedinger.engr.sgi.com>
On Mon, May 21 2007, Christoph Lameter wrote:
> On Mon, 21 May 2007, Jens Axboe wrote:
>
> > I can test whatever you want tomorrow morning, it was 100% repeatable
> > here. So which one, your patch or Hughs?
>
> This was an effect of me suggesting to switch off CONFIG_SLUB_DEBUG. If
> you did not run without CONFIG_SLUB_DEBUG then you were not affected by
> the problem. And the earlier case that you reported was a version of SLUB
> that did not have the capability to switch off SLUB_DEBUG.
>
> Is there any way we can boot with "slub_debug" on the kernel command line
> and get early printk output? Looks like an early failure that may have to
> do with other kernel debug options being on (lockdep or so?)
Sure, I will try that as well. For reference, the last kernel tested on
that box was HEAD 129a84de2347002f09721cda3155ccfd19fade40.
--
Jens Axboe
next prev parent reply other threads:[~2007-05-21 19:50 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-20 13:35 [PROBLEM] 2.6.22-rc2 panics on x86-64 with slub Srihari Vijayaraghavan
2007-05-21 16:30 ` Christoph Lameter
2007-05-21 17:41 ` Hugh Dickins
2007-05-21 18:25 ` Christoph Lameter
2007-05-21 18:44 ` Hugh Dickins
2007-05-21 18:48 ` Christoph Lameter
2007-05-21 19:00 ` Jens Axboe
2007-05-21 19:06 ` Hugh Dickins
2007-05-21 19:09 ` Jens Axboe
2007-05-21 19:13 ` Christoph Lameter
2007-05-21 19:26 ` Jens Axboe [this message]
2007-05-21 19:29 ` Hugh Dickins
2007-05-21 19:34 ` Christoph Lameter
2007-05-21 22:27 ` Christoph Lameter
2007-05-21 23:46 ` Christoph Lameter
2007-05-22 7:07 ` Jens Axboe
2007-05-22 8:26 ` Srihari Vijayaraghavan
2007-05-22 9:24 ` Ingo Molnar
2007-05-22 11:01 ` Srihari Vijayaraghavan
2007-05-22 11:20 ` Ingo Molnar
2007-05-22 11:26 ` Srihari Vijayaraghavan
2007-05-22 13:01 ` Hugh Dickins
2007-05-22 15:36 ` Jens Axboe
2007-05-22 18:30 ` Christoph Lameter
2007-05-22 20:10 ` Jens Axboe
2007-05-22 22:15 ` Srihari Vijayaraghavan
2007-05-22 22:25 ` Christoph Lameter
2007-05-23 7:11 ` Jens Axboe
2007-05-23 17:04 ` Christoph Lameter
2007-05-24 7:25 ` Jens Axboe
2007-05-24 16:55 ` Christoph Lameter
2007-05-25 6:12 ` Jens Axboe
2007-05-25 13:40 ` Christoph Lameter
2007-05-25 14:00 ` Jens Axboe
2007-05-26 1:52 ` Christoph Lameter
2007-05-26 2:49 ` Srihari Vijayaraghavan
2007-05-23 10:18 ` Srihari Vijayaraghavan
2007-05-23 17:10 ` Christoph Lameter
2007-05-23 17:19 ` Christoph Lameter
2007-05-23 22:23 ` Srihari Vijayaraghavan
2007-05-23 22:32 ` Christoph Lameter
2007-05-24 13:12 ` Srihari Vijayaraghavan
2007-05-24 16:58 ` Christoph Lameter
2007-05-24 21:30 ` Srihari Vijayaraghavan
2007-05-24 22:19 ` Christoph Lameter
2007-05-24 22:39 ` Srihari Vijayaraghavan
2007-05-21 19:04 ` Hugh Dickins
-- strict thread matches above, loose matches on Subject: below --
2007-05-20 3:09 Srihari Vijayaraghavan
2007-05-20 7:12 ` Christoph Lameter
2007-05-20 7:40 ` Srihari Vijayaraghavan
2007-05-20 13:24 ` Satyam Sharma
2007-05-20 13:37 ` Srihari Vijayaraghavan
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=20070521192656.GC4705@kernel.dk \
--to=jens.axboe@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=clameter@sgi.com \
--cc=hugh@veritas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oxymoron@waste.org \
--cc=sriharivijayaraghavan@yahoo.com.au \
/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