From: Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>
To: Jovi Zhangwei <jovi.zhangwei@gmail.com>,
Steven Rostedt <rostedt@goodmis.org>
Cc: Oleg Nesterov <oleg@redhat.com>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [BUG] 3.13-rc1 kernel crash when enable all tracepoints
Date: Tue, 26 Nov 2013 15:33:03 +0900 [thread overview]
Message-ID: <5294409F.70508@hitachi.com> (raw)
In-Reply-To: <CAGdX0WFeEuy+DtpsJzyzn0343qEEjLX97+o1VREFkUEhndC+5Q@mail.gmail.com>
(2013/11/26 13:38), Jovi Zhangwei wrote:
> Hi,
>
> I'm not sure this issue already be fixed or not, it can be reproduced
> permanently.
>
> (I didn't use git-bisect yet, you guys might can understand it quickly)
>
> #echo 1 > /sys/kernel/debug/tracing/events/enable
Thanks for reporting. I could reproduce it.
To narrow this down, I tried to run the below command
[tracing]# for i in events/*/*/enable ; do echo $i; echo 1 > $i; done
And it ran through the end without any problem.
Hm, next I checked the difference of available_events and set_event.
[tracing]# diff available_events set_event
283d282
< ftrace:function
So, I guess it was caused by enabling ftrace:function, and
it is unable to do that via set_event, nor events/ftrace/enable
I'm not sure how, but it seems that ftrace:function can be
enabled by the events/enable.
Thank you,
--
Masami HIRAMATSU
IT Management Research Dept. Linux Technology Center
Hitachi, Ltd., Yokohama Research Laboratory
E-mail: masami.hiramatsu.pt@hitachi.com
next prev parent reply other threads:[~2013-11-26 6:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-26 4:38 Jovi Zhangwei
2013-11-26 6:33 ` Masami Hiramatsu [this message]
2013-11-26 7:20 ` Jovi Zhangwei
2013-11-26 8:57 ` Masami Hiramatsu
2013-11-26 10:27 ` Masami Hiramatsu
2013-11-26 7:26 ` (ltc-kernel 7837) " Masami Hiramatsu
2013-11-26 12:58 ` Steven Rostedt
2013-11-26 14:32 ` Shuah Khan
2013-11-26 14:44 ` Steven Rostedt
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=5294409F.70508@hitachi.com \
--to=masami.hiramatsu.pt@hitachi.com \
--cc=jovi.zhangwei@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oleg@redhat.com \
--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
Powered by JetHome