From: Ingo Molnar <mingo@elte.hu>
To: Frederic Weisbecker <fweisbec@gmail.com>
Cc: Steven Rostedt <rostedt@goodmis.org>,
linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Thomas Gleixner <tglx@linutronix.de>,
Peter Zijlstra <peterz@infradead.org>,
Arnaldo Carvalho de Melo <acme@redhat.com>,
"Luis Claudio R. Goncalves" <lclaudio@uudg.org>
Subject: Re: [PATCH 0/6] [git pull] updates for tip/tracing/ftrace
Date: Thu, 19 Feb 2009 09:17:28 +0100 [thread overview]
Message-ID: <20090219081728.GA15452@elte.hu> (raw)
In-Reply-To: <20090218163524.GA5858@nowhere>
* Frederic Weisbecker <fweisbec@gmail.com> wrote:
> > the function-graph-tracer started locking up since the last
> > batch of changes:
> >
> > Testing tracer sysprof: .. no entries found ..FAILED!
> > initcall 0xffffffff812e91d1 returned -1 after 101562 usecs
> > initcall 0xffffffff812e91d1 returned with error code -1
> > calling 0xffffffff812e91e3 @ 1
> > Testing tracer function: PASSED
> > Testing dynamic ftrace:
> > [hard lockup]
>
> I've successfully reproduced it with your config.
> Note that I didn't built the function graph tracer.
>
> I also tried to set ftrace=nop as a parameter to avoid the selftests and then
> enabled the function tracer after the boot. And then I had no problem.
>
> Looks like it happens during dynamic ftrace initialization.
> Perhaps a problem with the recent mutex conversion and kstopmachine, which
> could result in a hardlockup in case of a deadlock.
>
> But lockdep didn't say anything.
> I'm reverting some of the last patches and will see.
Frederic, Steve, any progress on this bug? It's blocking all new
tracing patches.
Ingo
next prev parent reply other threads:[~2009-02-19 8:18 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-17 18:20 [PATCH 0/6] [git pull] updates for tip/tracing/ftrace Steven Rostedt
2009-02-17 18:20 ` [PATCH 1/6] ftrace: clean up coding style Steven Rostedt
2009-02-17 18:20 ` [PATCH 2/6] ftrace: rename _hook to _probe Steven Rostedt
2009-02-17 18:20 ` [PATCH 3/6] tracing: use the more proper parameter Steven Rostedt
2009-02-17 18:20 ` [PATCH 4/6] tracing: fix the return value of trace selftest Steven Rostedt
2009-02-17 18:20 ` [PATCH 5/6] tracing: fix typing mistake in hint message and comments Steven Rostedt
2009-02-17 18:20 ` [PATCH 6/6] ftrace: show unlimited when traceon or traceoff has no counter Steven Rostedt
2009-02-18 1:29 ` Steven Rostedt
2009-02-18 0:09 ` [PATCH 0/6] [git pull] updates for tip/tracing/ftrace Ingo Molnar
2009-02-18 8:40 ` Ingo Molnar
2009-02-18 8:57 ` Ingo Molnar
2009-02-18 9:30 ` Ingo Molnar
2009-02-18 17:06 ` Steven Rostedt
2009-02-18 18:19 ` Ingo Molnar
2009-02-18 14:20 ` Frederic Weisbecker
2009-02-18 16:35 ` Frederic Weisbecker
2009-02-19 8:17 ` Ingo Molnar [this message]
2009-02-19 9:16 ` Ingo Molnar
2009-02-19 11:15 ` 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=20090219081728.GA15452@elte.hu \
--to=mingo@elte.hu \
--cc=acme@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=fweisbec@gmail.com \
--cc=lclaudio@uudg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.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 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.