[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160921094529.6802e97e@gandalf.local.home>
Date: Wed, 21 Sep 2016 09:45:29 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: "Bean Huo (beanhuo)" <beanhuo@...ron.com>
Cc: "Zoltan Szubbocsev (zszubbocsev)" <zszubbocsev@...ron.com>,
"catalin.marinas@....com" <catalin.marinas@....com>,
"will.deacon@....com" <will.deacon@....com>,
"rfi@...ts.rocketboards.org" <rfi@...ts.rocketboards.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"mingo@...hat.com" <mingo@...hat.com>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>
Subject: Re: ftrace function_graph causes system crash
On Wed, 21 Sep 2016 07:50:58 +0000
"Bean Huo (beanhuo)" <beanhuo@...ron.com> wrote:
>
> Hi, Steve
> Thanks very much! This is a very useful trace tool, I now know the problem function,
> It is gt_counter_read, if not trace this function, ftrace function_graph work well.
> Do you know now how to deeply debug and trace which line is wrong through Ftrace?
Hmm, maybe I should add this into the scripts directory. Yeah, I should
do that.
-- Steve
Powered by blists - more mailing lists