> -----Original Message----- > From: Steven Rostedt [mailto:rost...@goodmis.org] > Sent: Mittwoch, 21. September 2016 20:17 > To: Jisheng Zhang <jszh...@marvell.com> > Cc: Bean Huo (beanhuo) <bean...@micron.com>; Zoltan Szubbocsev > (zszubbocsev) <zszubboc...@micron.com>; catalin.mari...@arm.com; > will.dea...@arm.com; r...@lists.rocketboards.org; linux- > ker...@vger.kernel.org; mi...@redhat.com; linux-arm- > ker...@lists.infradead.org > Subject: Re: ftrace function_graph causes system crash > > On Wed, 21 Sep 2016 17:13:07 +0800 > Jisheng Zhang <jszh...@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
