[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.64.0705212026080.5442@blonde.wat.veritas.com>
Date: Mon, 21 May 2007 20:29:30 +0100 (BST)
From: Hugh Dickins <hugh@...itas.com>
To: Christoph Lameter <clameter@....com>
cc: Jens Axboe <jens.axboe@...cle.com>,
Srihari Vijayaraghavan <sriharivijayaraghavan@...oo.com.au>,
Oliver Xymoron <oxymoron@...te.org>,
Andrew Morton <akpm@...ux-foundation.org>,
linux-kernel@...r.kernel.org
Subject: Re: [PROBLEM] 2.6.22-rc2 panics on x86-64 with slub
On Mon, 21 May 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.
Are you sure? If CONFIG_EMBEDDED=y then -rc1 and -rc2 give you the
choice to turn it off.
> 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?)
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists