public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>, Joerg Roedel <joerg.roedel@amd.com>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Steven Rostedt <rostedt@goodmis.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: bug in tty ldisc and friends
Date: Tue, 16 Jun 2009 12:29:10 +0200	[thread overview]
Message-ID: <20090616102910.GA11011@elte.hu> (raw)
In-Reply-To: <20090616102509.GA32717@elte.hu>


* Ingo Molnar <mingo@elte.hu> wrote:

> * Ingo Molnar <mingo@elte.hu> wrote:
> 
> > > On bootup with a totally generic Fedora 11, thinkpad setup 
> > > with the kernel swapped for current git head. Will send the 
> > > .config off list and build it with a 1M entry stack trace 
> > > again.
> > 
> > Nah, dont waste your time on that for now - if it's reproducible 
> > on simple bootup then i will be able to trigger it once i have 
> > your config.
> 
> update: i do trigger it too with your config:
> 
> BUG: MAX_STACK_TRACE_ENTRIES too low!

I have a potential workaround, please disable:

  CONFIG_DMA_API_DEBUG

does it get you below the limit? Here it gives:

 lock-classes:                          549 [max: 8191]
 direct dependencies:                  3288 [max: 16384]
 indirect dependencies:                6753
 all direct dependencies:             49282
 dependency chains:                    3384 [max: 32768]
 dependency chain hlocks:              9901 [max: 163840]
 in-hardirq chains:                      21
 in-softirq chains:                     243
 in-process chains:                    3120
 stack-trace entries:                 81205 [max: 262144]
 combined max dependencies:        16753528

We are now well below the limit for stack-trace entries.

This is something we noticed recently: dma-debug uses a lot of lock 
classes and thus creates a really large lock-graph, depleting the 
reserves quickly.

	Ingo

  reply	other threads:[~2009-06-16 10:29 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-16  5:45 bug in tty ldisc and friends Steven Rostedt
2009-06-16  8:37 ` Alan Cox
2009-06-16  8:50   ` Ingo Molnar
2009-06-16  8:57     ` Alan Cox
2009-06-16  9:09       ` Ingo Molnar
2009-06-16 10:00       ` Ingo Molnar
2009-06-16 10:04         ` Alan Cox
2009-06-16 10:12           ` Ingo Molnar
2009-06-16 10:25             ` Ingo Molnar
2009-06-16 10:29               ` Ingo Molnar [this message]
2009-06-16 10:34                 ` Joerg Roedel
2009-06-16 10:45                   ` Ingo Molnar
2009-06-16 10:36                 ` Ingo Molnar
2009-06-16 11:39                   ` Joerg Roedel
2009-06-16 12:11                     ` Ingo Molnar
2009-06-16 15:24                   ` Joerg Roedel
2009-06-17  8:32                   ` Peter Zijlstra
2009-06-17 14:10                     ` Ingo Molnar
2009-06-17 14:28                       ` Joerg Roedel

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=20090616102910.GA11011@elte.hu \
    --to=mingo@elte.hu \
    --cc=a.p.zijlstra@chello.nl \
    --cc=akpm@linux-foundation.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=joerg.roedel@amd.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rostedt@goodmis.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox