linux-rt-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Yang Shi <yang.shi@windriver.com>
To: Steven Rostedt <rostedt@goodmis.org>, He Zhe <zhe.he@windriver.com>
Cc: <tglx@linutronix.de>, <linux-rt-users@vger.kernel.org>
Subject: Re: 4.8.6-rt5 ftrace function_graph hangs
Date: Fri, 18 Nov 2016 10:36:49 -0800	[thread overview]
Message-ID: <4315c9ac-47cb-7218-027c-039a0cbfa548@windriver.com> (raw)
In-Reply-To: <20161118113524.43f6ff3c@gandalf.local.home>

On 11/18/2016 8:35 AM, Steven Rostedt wrote:
> On Fri, 18 Nov 2016 14:23:24 +0800
> He Zhe <zhe.he@windriver.com> wrote:
>
>> Hi,
>>
>> I'm using 4.8.6-rt5 and find the following issue on nxp-t4xxx board/qemuppc/qemux86-64.
>> When executing "echo function_graph > /sys/kernel/debug/tracing/current_tracer" the system hangs.
>> I traced the kernel to where it dies but don't know how to fix. Please help. Thank you.
>>
>> (gdb) b ftrace_startup
>>
>> ...
>>
>> Run till exit from #0 ftrace_startup (ops=0xc0cf1704 <graph_ops>, command=8) at /PATH/TO/kernel/trace/ftrace.c:2653
>> 0xc00eb768 in register_ftrace_graph (retfunc=0xc010186c <trace_graph_return>, entryfunc=0xc01014c4 <trace_graph_entry>)
>>      at /PATH/TO/kernel-source/kernel/trace/ftrace.c:5908
>> 5908 ret = ftrace_startup(&graph_ops, FTRACE_START_FUNC_RET);
>> Value returned is $1 = 0
>> (gdb) l
>> 5903 */
>> 5904 __ftrace_graph_entry = entryfunc;
>> 5905 ftrace_graph_entry = ftrace_graph_entry_test;
>> 5906 update_function_graph_func();
>> 5907
>> 5908 ret = ftrace_startup(&graph_ops, FTRACE_START_FUNC_RET);
>> 5909 out:
>> 5910 mutex_unlock(&ftrace_lock);
>> 5911 return ret;
>> 5912 }
>> (gdb) n
>> 5910 mutex_unlock(&ftrace_lock);
>> (gdb) n
>>
>> hangs...
>>

Hi Steve,

> Can't you get a backtrace from this? It's running under qemu right? So
> it should be able to break it and see where it is at.
>
> Note, my PowerPC box has just died, so I'm no longer able to work on
> it, and don't have time to set up a qemu ppc image at the moment.

We found this issue on x86 too. It is not PPC specific problem.

Thanks,
Yang

>
> -- Steve



  reply	other threads:[~2016-11-18 18:37 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-18  6:23 4.8.6-rt5 ftrace function_graph hangs He Zhe
2016-11-18 16:35 ` Steven Rostedt
2016-11-18 18:36   ` Yang Shi [this message]
2016-11-18 22:32     ` Steven Rostedt
2016-11-21  8:26   ` He Zhe
2016-11-21  8:30     ` He Zhe
2016-11-21 14:45       ` Steven Rostedt
2016-11-28 14:33       ` Sebastian Andrzej Siewior
2016-12-02 21:42         ` Yang Shi
2016-12-06 11:07           ` Sebastian Andrzej Siewior

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=4315c9ac-47cb-7218-027c-039a0cbfa548@windriver.com \
    --to=yang.shi@windriver.com \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=tglx@linutronix.de \
    --cc=zhe.he@windriver.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;
as well as URLs for NNTP newsgroup(s).