[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1234355070.23438.133.camel@twins>
Date: Wed, 11 Feb 2009 13:24:30 +0100
From: Peter Zijlstra <peterz@...radead.org>
To: Alexander Beregalov <a.beregalov@...il.com>
Cc: "linux-next@...r.kernel.org" <linux-next@...r.kernel.org>,
LKML <linux-kernel@...r.kernel.org>, Ingo Molnar <mingo@...e.hu>
Subject: Re: next-20090211: BUG: MAX_LOCKDEP_SUBCLASSES too low!
On Wed, 2009-02-11 at 13:23 +0100, Peter Zijlstra wrote:
> 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?
Sorry, not playing attention, its SUB classes.. let me look at that,
that smells like a rotten annotation.
--
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