From: Peter Zijlstra <peterz@infradead.org>
To: Alexander Beregalov <a.beregalov@gmail.com>
Cc: "linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>
Subject: Re: next-20090211: BUG: MAX_LOCKDEP_SUBCLASSES too low!
Date: Wed, 11 Feb 2009 13:24:30 +0100 [thread overview]
Message-ID: <1234355070.23438.133.camel@twins> (raw)
In-Reply-To: <1234355010.23438.132.camel@twins>
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.
next prev parent reply other threads:[~2009-02-11 12:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-11 12:14 next-20090211: BUG: MAX_LOCKDEP_SUBCLASSES too low! Alexander Beregalov
2009-02-11 12:23 ` Peter Zijlstra
2009-02-11 12:24 ` Peter Zijlstra [this message]
2009-02-11 12:26 ` Peter Zijlstra
2009-02-11 12:52 ` Alexander Beregalov
2009-02-11 13:04 ` Peter Zijlstra
2009-02-11 14:00 ` Peter Zijlstra
2009-02-11 14:01 ` Chris Mason
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1234355070.23438.133.camel@twins \
--to=peterz@infradead.org \
--cc=a.beregalov@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mingo@elte.hu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox