From: "Bean Huo (beanhuo)" <beanhuo@micron.com>
To: Steven Rostedt <rostedt@goodmis.org>,
Jisheng Zhang <jszhang@marvell.com>
Cc: "Zoltan Szubbocsev (zszubbocsev)" <zszubbocsev@micron.com>,
"catalin.marinas@arm.com" <catalin.marinas@arm.com>,
"will.deacon@arm.com" <will.deacon@arm.com>,
"rfi@lists.rocketboards.org" <rfi@lists.rocketboards.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"mingo@redhat.com" <mingo@redhat.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: RE: ftrace function_graph causes system crash
Date: Thu, 22 Sep 2016 08:36:41 +0000 [thread overview]
Message-ID: <baf9aa64cc5e479ca21e30c176062f20@SIWEX5A.sing.micron.com> (raw)
In-Reply-To: <20160921141705.6ab0be03@gandalf.local.home>
> -----Original Message-----
> From: Steven Rostedt [mailto:rostedt@goodmis.org]
> Sent: Mittwoch, 21. September 2016 20:17
> To: Jisheng Zhang <jszhang@marvell.com>
> Cc: Bean Huo (beanhuo) <beanhuo@micron.com>; Zoltan Szubbocsev
> (zszubbocsev) <zszubbocsev@micron.com>; catalin.marinas@arm.com;
> will.deacon@arm.com; rfi@lists.rocketboards.org; linux-
> kernel@vger.kernel.org; mingo@redhat.com; linux-arm-
> kernel@lists.infradead.org
> Subject: Re: ftrace function_graph causes system crash
>
> On Wed, 21 Sep 2016 17:13:07 +0800
> Jisheng Zhang <jszhang@marvell.com> wrote:
>
> > I'm not sure whether the commit d6df3576e6b4
> ("clocksource/drivers/arm_global_timer
> > : Prevent ftrace recursion") can fix this issue.
> >
> > this commit is merged since v4.3, I noticed your kernel version is v4.0
>
> BTW, yes, that would be the fix.
>
> -- Steve
>
> >
> > Thanks,
> > Jisheng
> >
> > > Do you know now how to deeply debug and trace which line is wrong
> through Ftrace?
> > >
Hi, Steven and Jisheng
Thanks to both warm-hearted guys. I merged d6df3576e6b4 patch into my kernel 4.0.
Then it is true, no cash appears again.
I have one more question that current ftrace can trace DMA latency, include mapping and unmapping?
Means I want to know when one BIO request be completed. Just like blktrace.
But blktrace can not tell me the function calling sequence.
--Bean
next prev parent reply other threads:[~2016-09-22 8:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-20 13:10 Bean Huo (beanhuo)
2016-09-20 14:07 ` Steven Rostedt
2016-09-21 7:50 ` Bean Huo (beanhuo)
2016-09-21 9:13 ` Jisheng Zhang
2016-09-21 18:17 ` Steven Rostedt
2016-09-22 8:36 ` Bean Huo (beanhuo) [this message]
2016-09-21 13:45 ` 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=baf9aa64cc5e479ca21e30c176062f20@SIWEX5A.sing.micron.com \
--to=beanhuo@micron.com \
--cc=catalin.marinas@arm.com \
--cc=jszhang@marvell.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rfi@lists.rocketboards.org \
--cc=rostedt@goodmis.org \
--cc=will.deacon@arm.com \
--cc=zszubbocsev@micron.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
all inboxes | Powered by JetHome®