From: Dave Jones <davej@redhat.com>
To: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: "Joao Correia" <joaomiguelcorreia@gmail.com>,
LKML <linux-kernel@vger.kernel.org>,
"Américo Wang" <xiyou.wangcong@gmail.com>
Subject: Re: [PATCH 1/3] Increase lockdep limits: MAX_STACK_TRACE_ENTRIES
Date: Wed, 8 Jul 2009 13:22:48 -0400 [thread overview]
Message-ID: <20090708172248.GB2521@redhat.com> (raw)
In-Reply-To: <1246982101.9777.15.camel@twins>
On Tue, Jul 07, 2009 at 05:55:01PM +0200, Peter Zijlstra wrote:
> On Tue, 2009-07-07 at 16:50 +0100, Joao Correia wrote:
>
> > >> Yes. Anything 2.6.31 forward triggers this immediatly during init
> > >> process, at random places.
> > >
> > > Not on my machines it doesn't.. so I suspect its something weird in
> > > your .config or maybe due to some hardware you have that I don't that
> > > triggers different drivers or somesuch.
> >
> > I am not the only one reporting this, and it happens, for example,
> > with a stock .config from a Fedora 11 install.
> >
> > It may, of course, be a funny driver interaction yes, but other than
> > stripping the box piece by piece, how would one go about debugging
> > this otherwise?
>
> One thing to do is stare (or share) at the output
> of /proc/lockdep_chains and see if there's some particularly large
> chains in there, or many of the same name or something.
I don't see any long chains, just lots of them.
29065 lines on my box that's hitting MAX_STACK_TRACE_ENTRIES
> /proc/lockdep_stats might also be interesting, mine reads like:
lock-classes: 1518 [max: 8191]
direct dependencies: 7142 [max: 16384]
indirect dependencies: 97905
all direct dependencies: 753706
dependency chains: 6201 [max: 32768]
dependency chain hlocks: 16665 [max: 163840]
in-hardirq chains: 1380
in-softirq chains: 589
in-process chains: 4232
stack-trace entries: 262144 [max: 262144]
combined max dependencies: 3449006070
hardirq-safe locks: 1008
hardirq-unsafe locks: 364
softirq-safe locks: 838
softirq-unsafe locks: 322
irq-safe locks: 1043
irq-unsafe locks: 364
hardirq-read-safe locks: 0
hardirq-read-unsafe locks: 48
softirq-read-safe locks: 0
softirq-read-unsafe locks: 48
irq-read-safe locks: 0
irq-read-unsafe locks: 48
uncategorized locks: 104
unused locks: 0
max locking depth: 9
max recursion depth: 10
debug_locks: 0
Dave
next prev parent reply other threads:[~2009-07-08 17:23 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-07 15:25 [PATCH 1/3] Increase lockdep limits: MAX_STACK_TRACE_ENTRIES Joao Correia
2009-07-07 15:33 ` Peter Zijlstra
[not found] ` <a5d9929e0907070838q7ed3306du3bb7880e47d7207b@mail.gmail.com>
2009-07-07 15:38 ` Fwd: " Joao Correia
[not found] ` <1246981444.9777.11.camel@twins>
2009-07-07 15:50 ` Joao Correia
2009-07-07 15:55 ` Peter Zijlstra
2009-07-07 15:59 ` Joao Correia
2009-07-08 17:22 ` Dave Jones [this message]
2009-07-08 18:36 ` Peter Zijlstra
2009-07-08 18:44 ` Dave Jones
2009-07-08 19:48 ` Joao Correia
2009-07-08 19:56 ` Peter Zijlstra
2009-07-09 4:39 ` Dave Jones
2009-07-09 8:02 ` Peter Zijlstra
2009-07-09 16:10 ` Dave Jones
2009-07-09 17:07 ` Peter Zijlstra
2009-07-10 15:50 ` Joao Correia
2009-07-09 9:06 ` Catalin Marinas
2009-07-09 9:09 ` Peter Zijlstra
2009-07-20 13:31 ` [PATCH] lockdep: fixup stacktrace wastage Peter Zijlstra
2009-08-02 13:14 ` [tip:core/locking] lockdep: Fix backtraces tip-bot for Peter Zijlstra
2009-08-02 13:51 ` tip-bot for Peter Zijlstra
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=20090708172248.GB2521@redhat.com \
--to=davej@redhat.com \
--cc=a.p.zijlstra@chello.nl \
--cc=joaomiguelcorreia@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=xiyou.wangcong@gmail.com \
/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.