From mboxrd@z Thu Jan 1 00:00:00 1970 From: Peter Zijlstra Subject: Re: next-20090211: BUG: MAX_LOCKDEP_SUBCLASSES too low! Date: Wed, 11 Feb 2009 13:23:30 +0100 Message-ID: <1234355010.23438.132.camel@twins> References: Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Return-path: Received: from casper.infradead.org ([85.118.1.10]:50600 "EHLO casper.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750920AbZBKMVj (ORCPT ); Wed, 11 Feb 2009 07:21:39 -0500 In-Reply-To: Sender: linux-next-owner@vger.kernel.org List-ID: To: Alexander Beregalov Cc: "linux-next@vger.kernel.org" , LKML , Ingo Molnar On Wed, 2009-02-11 at 15:14 +0300, Alexander Beregalov wrote: > Hi > > Full dmesg is attached. > > Lock dependency validator: Copyright (c) 2006 Red Hat, Inc., Ingo Molnar > .... MAX_LOCKDEP_SUBCLASSES: 8 > .... MAX_LOCK_DEPTH: 48 > .... MAX_LOCKDEP_KEYS: 8191 > .... CLASSHASH_SIZE: 4096 > .... MAX_LOCKDEP_ENTRIES: 8192 > .... MAX_LOCKDEP_CHAINS: 16384 > .... CHAINHASH_SIZE: 8192 > memory used by lock dependency info: 4351 kB > per task-struct memory footprint: 2688 bytes > <..> > BUG: MAX_LOCKDEP_SUBCLASSES too low! > turning off the locking correctness validator. Is this an allyesconfig or something other massive bloated?