All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Jonathan Corbet <corbet@lwn.net>,
	LKML <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>
Subject: Re: 2.6.30-rc kills my box hard - and lockdep chains
Date: Sat, 16 May 2009 16:03:45 -0700	[thread overview]
Message-ID: <20090516160345.5bec42d7.akpm@linux-foundation.org> (raw)
In-Reply-To: <1242365555.26820.51.camel@twins>

On Fri, 15 May 2009 07:32:35 +0200 Peter Zijlstra <peterz@infradead.org> wrote:

> On Thu, 2009-05-14 at 09:49 -0600, Jonathan Corbet wrote:
> > First time gave me:
> > 
> >         BUG: MAX_LOCKDEP_ENTRIES too low!
> > 
> > So I doubled it.  Now I get:
> > 
> > May 14 01:06:55 bike kernel: [38730.804833] BUG: MAX_LOCKDEP_CHAINS
> > too low!
> 
> Ingo recently raised these numbers, from the -tip tree:
> 
> commit d80c19df5fcceb8c741e96f09f275c2da719efef
> Author: Ingo Molnar <mingo@elte.hu>
> Date:   Tue May 12 16:29:13 2009 +0200
> 
>     lockdep: increase MAX_LOCKDEP_ENTRIES and MAX_LOCKDEP_CHAINS
> 
> 
> This will likely make its way upstream soonish.

That patch isn't in linux-next and I can't be bothered going off and
finding it.

Jon said that doubling MAX_LOCKDEP_CHAINS didn't help.  How much did
the above patch increase things by?


  reply	other threads:[~2009-05-16 23:08 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-14 15:49 2.6.30-rc kills my box hard - and lockdep chains Jonathan Corbet
2009-05-15  5:32 ` Peter Zijlstra
2009-05-16 23:03   ` Andrew Morton [this message]
2009-05-16 23:13     ` Jonathan Corbet
2009-05-16 23:14 ` Andrew Morton
2009-05-17  0:38   ` Frederic Weisbecker
2009-05-17  1:23     ` Frederic Weisbecker
2009-05-17  1:48   ` Ming Lei
2009-05-18 19:02   ` Jonathan Corbet

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=20090516160345.5bec42d7.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=corbet@lwn.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=peterz@infradead.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.