Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S935836AbXEUTy5 (ORCPT ); Mon, 21 May 2007 15:54:57 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S933933AbXEUT3z (ORCPT ); Mon, 21 May 2007 15:29:55 -0400 Received: from extu-mxob-1.symantec.com ([216.10.194.28]:42453 "EHLO extu-mxob-1.symantec.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S934083AbXEUT3x (ORCPT ); Mon, 21 May 2007 15:29:53 -0400 Date: Mon, 21 May 2007 20:29:30 +0100 (BST) From: Hugh Dickins X-X-Sender: hugh@blonde.wat.veritas.com To: Christoph Lameter cc: Jens Axboe , Srihari Vijayaraghavan , Oliver Xymoron , Andrew Morton , linux-kernel@vger.kernel.org Subject: Re: [PROBLEM] 2.6.22-rc2 panics on x86-64 with slub In-Reply-To: Message-ID: References: <20070520133505.46147.qmail@web52609.mail.re2.yahoo.com> <20070521190043.GA4705@kernel.dk> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Brightmail-Verdict: VlJEQwAAAAIAAAABAAAAAAAAAAEAAAAAAAAABmluYm94AHNyaWhhcml2aWpheWFyYWdoYXZhbkB5YWhvby5jb20uYXUAb3h5bW9yb25Ad2FzdGUub3JnAGxpbnV4LWtlcm5lbEB2Z2VyLmtlcm5lbC5vcmcAY2xhbWV0ZXJAc2dpLmNvbQBqZW5zLmF4Ym9lQG9yYWNsZS5jb20AYWtwbUBsaW51eC1mb3VuZGF0aW9uLm9yZwA= X-Brightmail-Tracker: AAAAAA== Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1054 Lines: 22 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@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/