From: Peter Zijlstra <peterz@infradead.org>
To: Stefan Richter <stefanr@s5r6.in-berlin.de>
Cc: Ingo Molnar <mingo@redhat.com>, linux-kernel@vger.kernel.org
Subject: Re: "BUG: MAX_STACK_TRACE_ENTRIES too low!" - reason for concern?
Date: Sun, 14 Dec 2008 13:41:25 +0100 [thread overview]
Message-ID: <1229258485.17130.8.camel@lappy.programming.kicks-ass.net> (raw)
In-Reply-To: <tkrat.7ea353e737215fa2@s5r6.in-berlin.de>
On Sun, 2008-12-14 at 02:38 +0100, Stefan Richter wrote:
> Is the following anything that anybody should do something about?
>
> # unloading IEEE 1394 drivers (as slightly before linux1394-2.6.git)
>
> Dec 14 01:23:24 stein ieee1394: Node removed: ID:BUS[3-00:1023] GUID[00d0f5200800613d]
> Dec 14 01:23:24 stein ieee1394: Node removed: ID:BUS[2-00:1023] GUID[0010dc5600fed2d4]
> Dec 14 01:23:24 stein ieee1394: Node removed: ID:BUS[1-01:1023] GUID[0030bd051800064f]
> Dec 14 01:23:24 stein ieee1394: Node removed: ID:BUS[1-00:1023] GUID[0012870035000f94]
> Dec 14 01:23:24 stein ieee1394: Node removed: ID:BUS[0-08:1023] GUID[080028560000319b]
>
> # reloading IEEE 1394 drivers (as in linux1394-2.6.git)
>
> Dec 14 01:23:29 stein BUG: MAX_STACK_TRACE_ENTRIES too low!
lockdep resource allocation is pretty simple wrt to modules, it will not
re-use anything, therefore cycling modules will let it run out of its
resources pretty quickly.
I suppose one could go add all kinds of smart and complicate the whole
thing, but I'm not sure its worth it.
next prev parent reply other threads:[~2008-12-14 12:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-14 1:38 Stefan Richter
2008-12-14 12:41 ` Peter Zijlstra [this message]
2008-12-14 12:54 ` Stefan Richter
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=1229258485.17130.8.camel@lappy.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=stefanr@s5r6.in-berlin.de \
/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
all inboxes | Powered by JetHome®