public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: "Michael S. Tsirkin" <mst@mellanox.co.il>
Cc: Roland Dreier <roland.list@gmail.com>,
	Roland Dreier <rdreier@cisco.com>,
	general@lists.openfabrics.org,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: lockdep question (was Re: IPoIB caused a kernel: BUG: soft lockup detected on CPU#0!)
Date: Sun, 11 Mar 2007 20:19:20 +0100	[thread overview]
Message-ID: <20070311191920.GA7049@elte.hu> (raw)
In-Reply-To: <20070311150431.GE31985@mellanox.co.il>


* Michael S. Tsirkin <mst@mellanox.co.il> wrote:

> After adding some printks, I started getting these:
> 
> [  597.036720] BUG: MAX_STACK_TRACE_ENTRIES too low!

this should go away if you double the size of MAX_STACK_TRACE_ENTRIES in 
kernel/lockdep_internals.h. (keep it a power of two) If it doesnt go 
away then it might signal some sort of leak.

	Ingo

  parent reply	other threads:[~2007-03-11 19:20 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <45E552FC.4040305@mellanox.co.il>
     [not found] ` <f8ca0a150703030937u61bcd9aj200415b76c00d151@mail.gmail.com>
2007-03-11 13:50   ` lockdep question (was Re: IPoIB caused a kernel: BUG: soft lockup detected on CPU#0!) Michael S. Tsirkin
2007-03-11 15:04     ` Michael S. Tsirkin
2007-03-11 15:22       ` Michael S. Tsirkin
2007-03-11 19:19       ` Ingo Molnar [this message]
2007-03-11 15:25     ` Peter Zijlstra
2007-03-11 16:12       ` lockdep question (was Re: IPoIB caused a kernel: BUG: softlockup " Michael S. Tsirkin
2007-03-11 18:48         ` Ingo Molnar
2007-03-12 13:29           ` Michael S. Tsirkin
2007-03-12 13:51             ` Ingo Molnar
2007-03-12 14:20               ` Michael S. Tsirkin

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=20070311191920.GA7049@elte.hu \
    --to=mingo@elte.hu \
    --cc=general@lists.openfabrics.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mst@mellanox.co.il \
    --cc=rdreier@cisco.com \
    --cc=roland.list@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox