All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sasha Levin <sasha.levin@oracle.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Ingo Molnar <mingo@kernel.org>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: lockdep: BUG: MAX_LOCKDEP_ENTRIES too low!
Date: Thu, 19 Dec 2013 09:02:14 -0500	[thread overview]
Message-ID: <52B2FC66.9010309@oracle.com> (raw)
In-Reply-To: <20131219103401.GE30183@twins.programming.kicks-ass.net>

On 12/19/2013 05:34 AM, Peter Zijlstra wrote:
> On Thu, Dec 19, 2013 at 12:53:56AM -0500, Sasha Levin wrote:
>> Hi all,
>>
>> I think that my bloated kernel managed to create way too many entries in the
>> dependency table. If that sounds right, I can send a patch to increase those.
>>
>> Attached /proc/lock_stat as requested as well.
>
> /proc/lockdep_stats not lock_stat :-)
>
> Do you still happen to have that?

Is the BUG message intentional ("Please attach the output of /proc/lock_stat to the bug report")?

Here's /proc/lockdep_stats:

  lock-classes:                         2397 [max: 8191]
  direct dependencies:                 16384 [max: 16384]
  indirect dependencies:               60481
  all direct dependencies:            308079
  dependency chains:                   21162 [max: 32768]
  dependency chain hlocks:             67298 [max: 163840]
  in-hardirq chains:                      51
  in-softirq chains:                     430
  in-process chains:                   19782
  stack-trace entries:                235133 [max: 262144]
  combined max dependencies:       443376596
  hardirq-safe locks:                     59
  hardirq-unsafe locks:                 1285
  softirq-safe locks:                    156
  softirq-unsafe locks:                 1136
  irq-safe locks:                        168
  irq-unsafe locks:                     1285
  hardirq-read-safe locks:                 4
  hardirq-read-unsafe locks:             357
  softirq-read-safe locks:                 7
  softirq-read-unsafe locks:             337
  irq-read-safe locks:                     8
  irq-read-unsafe locks:                 357
  uncategorized locks:                   281
  unused locks:                            0
  max locking depth:                      12
  max bfs queue depth:                   663
  chain lookup misses:                 21432
  chain lookup hits:               490237032
  cyclic checks:                       20219
  find-mask forwards checks:           12353
  find-mask backwards checks:         128734
  hardirq on events:               372837372
  hardirq off events:              372837362
  redundant hardirq ons:                3467
  redundant hardirq offs:          361517382
  softirq on events:                 3688513
  softirq off events:                3688541
  redundant softirq ons:                   0
  redundant softirq offs:                  0
  debug_locks:                             0


Thanks,
Sasha

  reply	other threads:[~2013-12-19 14:02 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-19  5:53 lockdep: BUG: MAX_LOCKDEP_ENTRIES too low! Sasha Levin
2013-12-19 10:34 ` Peter Zijlstra
2013-12-19 14:02   ` Sasha Levin [this message]
2013-12-19 15:20     ` Peter Zijlstra
2013-12-19 15:39       ` Sasha Levin
2013-12-19 15:51         ` Peter Zijlstra
2013-12-19 15:59           ` Dave Jones
2013-12-19 16:01             ` Peter Zijlstra
2013-12-19 16:10               ` Dave Jones
2013-12-19 16:51             ` Sasha Levin
2013-12-20  4:05             ` Mike Galbraith
2013-12-19 15:49       ` Ingo Molnar

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=52B2FC66.9010309@oracle.com \
    --to=sasha.levin@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --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.