[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <c94103d2-ed5d-bf43-fc71-c60e108f303e@codeaurora.org>
Date: Wed, 17 Oct 2018 00:36:05 +0530
From: Sai Prakash Ranjan <saiprakash.ranjan@...eaurora.org>
To: Steven Rostedt <rostedt@...dmis.org>
Cc: Stephen Boyd <sboyd@...nel.org>,
Bjorn Andersson <bjorn.andersson@...aro.org>,
Andy Gross <andy.gross@...aro.org>,
David Brown <david.brown@...aro.org>,
Jiri Slaby <jslaby@...e.com>,
Kees Cook <keescook@...omium.org>,
"Joel Fernandes (Google)" <joel@...lfernandes.org>,
Geliang Tang <geliangtang@...il.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Pramod Gurav <gpramod@...eaurora.org>,
linux-arm-msm@...r.kernel.org, linux-soc@...r.kernel.org,
linux-serial@...r.kernel.org, linux-kernel@...r.kernel.org,
Rajendra Nayak <rnayak@...eaurora.org>,
Vivek Gautam <vivek.gautam@...eaurora.org>,
Sibi Sankar <sibis@...eaurora.org>
Subject: Re: Crash in msm serial on dragonboard with ftrace bootargs
On 10/17/2018 12:33 AM, Steven Rostedt wrote:
> On Wed, 17 Oct 2018 00:31:03 +0530
> Sai Prakash Ranjan <saiprakash.ranjan@...eaurora.org> wrote:
>
>> Haa seems like you are right! With "ftrace=function
>> ftrace_filter=msm_read" , I can trigger the crash, but
>> sadly "ftrace_notrace=msm_read" also crashes.
>
> So there's more than one problem area.
>
> What about ftrace_notrace=m*
>
> ?
>
That too crashes.
--
QUALCOMM INDIA, on behalf of Qualcomm Innovation Center, Inc. is a member
of Code Aurora Forum, hosted by The Linux Foundation
Powered by blists - more mailing lists