DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
  s=s1024; d=yahoo.com.au;
  h=X-YMail-OSG:Received:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID;
  b=06ucUcfXGdWgsOpXu7833ci45c9cfa8xXwrRdVR7/NyNLqdMdB1oBNSbORZCSlqOkMc4ZPSgBZffLqlL+5aE2WR/J3e0gJkwQOePwGx4ut+cJc6yDxz/PQfEK2ZIEFNV7xIvISgm9gFrqlIX5pop2kfUJrYiM+OGLSN91MMXWyw=;
Date: Tue, 22 May 2007 21:26:40 +1000 (EST)
From: Srihari Vijayaraghavan <sriharivijayaraghavan@yahoo.com.au>
Subject: Re: [PROBLEM] 2.6.22-rc2 panics on x86-64 with slub
To: Ingo Molnar <mingo@elte.hu>
Cc: Christoph Lameter <clameter@sgi.com>, Hugh Dickins <hugh@veritas.com>,
       Oliver Xymoron <oxymoron@waste.org>,
       Andrew Morton <akpm@linux-foundation.org>,
       Jens Axboe <jens.axboe@oracle.com>, linux-kernel@vger.kernel.org
In-Reply-To: <20070522112008.GA16308@elte.hu>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7BIT
Message-ID: <441137.33501.qm@web52606.mail.re2.yahoo.com>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1012
Lines: 23

--- Ingo Molnar <mingo@elte.hu> wrote:
[...]
> yes - PROVE_LOCKING reactivates spinlocks even on UP. At least this 
> suggests that you'd have gotten the hang even with maxcpus=1 - i.e. the 
> spinlock corruption is not caused by some genuine SMP race.
 
You're right on the mark there: even with maxcpus=1 or nosmp (or with both),
with PROVE_LOCKING it hung with slub. I didn't mention that so not to confuse
the matter, but you rightly figured that out too.

Thanks


      ___________________________________________________________________________________
How would you spend $50,000 to create a more sustainable environment in Australia?  Go to Yahoo!7 Answers and share your idea.
http://advision.webevents.yahoo.com/aunz/lifestyle/answers/y7ans-babp_reg.html

-
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/