All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sai Prakash Ranjan <saiprakash.ranjan@codeaurora.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Stephen Boyd <sboyd@kernel.org>,
	Bjorn Andersson <bjorn.andersson@linaro.org>,
	Andy Gross <andy.gross@linaro.org>,
	David Brown <david.brown@linaro.org>,
	Jiri Slaby <jslaby@suse.com>,
	"Ivan T. Ivanov" <ivan.ivanov@linaro.org>,
	Kees Cook <keescook@chromium.org>,
	"Joel Fernandes (Google)" <joel@joelfernandes.org>,
	Geliang Tang <geliangtang@gmail.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Pramod Gurav <gpramod@codeaurora.org>,
	linux-arm-msm@vger.kernel.org, linux-soc@vger.kernel.org,
	linux-serial@vger.kernel.org, linux-kernel@vger.kernel.org,
	Rajendra Nayak <rnayak@codeaurora.org>,
	Vivek Gautam <vivek.gautam@codeaurora.org>,
	Sibi Sankar <sibis@codeaurora.org>
Subject: Re: Crash in msm serial on dragonboard with ftrace bootargs
Date: Tue, 16 Oct 2018 23:35:00 +0530	[thread overview]
Message-ID: <472db11e-49a6-a1ee-e298-791ee1bbb10b@codeaurora.org> (raw)
In-Reply-To: <20181016134803.1b9260c1@gandalf.local.home>

On 10/16/2018 11:18 PM, Steven Rostedt wrote:
> On Tue, 16 Oct 2018 23:06:24 +0530
> Sai Prakash Ranjan <saiprakash.ranjan@codeaurora.org> wrote:
> 
>> On 10/16/2018 10:27 PM, Steven Rostedt wrote:
>>>
>>> OK, can you add to the command line:
>>>
>>>    ftrace=function ftrace_filter=*schedule*
>>>
>>> to see if it's a specific function that may be causing the issue (but
>>> hopefully it's not one of the scheduling functions that caused it).
>>>    
>>
>> Target boots fine with this. So its not scheduling functions that is
>> causing it. Also I tried with ftrace_filter=*msm* just to be sure if
>> tracing driver functions is causing any issue but its NOT.
> 
> OK, seems that something is being traced that shouldn't be.
> 
> When this happens after boot up, it's easy to bisect down to the
> problem function. But since it's at boot up, it will take a lot longer.
> 
> I would suggest to start by going down the alphabet.
> 
> 	ftrace_filter=a*
>   	ftrace_filter=b*
> 	ftrace_filter=c*
> 	[...]
> 
> And at least find the letter the bad function starts with.
> 
> Note, it could be more than one function (I've had that a couple of
> times), and to find that out, you can test with "ftrace_notrace". Say
> you find that the problem function starts with 'x'. You can do:
> 
> 	ftrace_notrace=x*
> 
> Which will trace all functions except those that start with an 'x', to
> make sure it still boots.
> 
> Remember, you still need to have ftrace=function for all of this.
> 
> Once you find the letter of the function, you can try the next letter,
> or perhaps come up with another method. I would say look at the
> functions in /sys/kernel/debug/tracing/available_filter_functions, but
> they don't list the init function (that can be traced). But you can
> use /proc/kallsyms instead.
> 

Ok got it, this sounds fun. I'll give it a try.

Thanks

-- 
QUALCOMM INDIA, on behalf of Qualcomm Innovation Center, Inc. is a member
of Code Aurora Forum, hosted by The Linux Foundation

  reply	other threads:[~2018-10-16 18:05 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-16 11:38 Crash in msm serial on dragonboard with ftrace bootargs Sai Prakash Ranjan
2018-10-16 11:44 ` Greg Kroah-Hartman
2018-10-16 11:58   ` Sai Prakash Ranjan
2018-10-16 15:29 ` Steven Rostedt
2018-10-16 16:35   ` Sai Prakash Ranjan
2018-10-16 16:57     ` Steven Rostedt
2018-10-16 17:36       ` Sai Prakash Ranjan
2018-10-16 17:48         ` Steven Rostedt
2018-10-16 18:05           ` Sai Prakash Ranjan [this message]
2018-10-16 18:16             ` Steven Rostedt
2018-10-16 18:25               ` Sai Prakash Ranjan
2018-10-16 18:41                 ` Steven Rostedt
2018-10-16 19:01                   ` Sai Prakash Ranjan
2018-10-16 19:03                     ` Steven Rostedt
2018-10-16 19:06                       ` Sai Prakash Ranjan
2018-10-16 19:15                         ` Steven Rostedt
2018-10-16 19:16                           ` Steven Rostedt
2018-10-16 19:37                             ` Sai Prakash Ranjan
2018-10-16 19:35                           ` Sai Prakash Ranjan
2018-10-16 20:51                             ` Stephen Boyd
2018-10-16 20:51                               ` Stephen Boyd
2018-10-17 11:27                               ` Sai Prakash Ranjan
2018-10-18  2:33                         ` Steven Rostedt
2018-10-18  5:21                           ` Sai Prakash Ranjan
2018-10-18 13:17                             ` Steven Rostedt
2018-10-19  4:17                               ` Joel Fernandes
2018-10-19  6:54                                 ` Sai Prakash Ranjan
2018-10-19 13:51                                   ` Steven Rostedt
2018-10-19 14:48                                     ` Sai Prakash Ranjan
2018-10-19 15:12                                       ` Steven Rostedt
2018-10-25 14:36                                         ` saiprakash.ranjan
2018-11-13  9:44                                           ` Srinivas Kandagatla
2018-11-15 10:33                                             ` Sai Prakash Ranjan
2018-11-15 10:53                                               ` Srinivas Kandagatla
2018-11-16  3:39                                                 ` Viresh Kumar
2018-11-16 10:49                                                   ` Sai Prakash Ranjan
2018-10-16 17:02   ` Kees Cook
2018-10-17 10:13     ` Joel Fernandes
2018-10-17 11:38       ` Sai Prakash Ranjan
2018-10-17 14:49         ` Sai Prakash Ranjan
2018-10-17 17:56           ` Joel Fernandes
2018-10-17 18:25             ` Kees Cook
2018-10-16 23:09 ` Joel Fernandes
2018-10-17 11:53   ` Sai Prakash Ranjan

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=472db11e-49a6-a1ee-e298-791ee1bbb10b@codeaurora.org \
    --to=saiprakash.ranjan@codeaurora.org \
    --cc=andy.gross@linaro.org \
    --cc=bjorn.andersson@linaro.org \
    --cc=david.brown@linaro.org \
    --cc=geliangtang@gmail.com \
    --cc=gpramod@codeaurora.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=ivan.ivanov@linaro.org \
    --cc=joel@joelfernandes.org \
    --cc=jslaby@suse.com \
    --cc=keescook@chromium.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=linux-soc@vger.kernel.org \
    --cc=rnayak@codeaurora.org \
    --cc=rostedt@goodmis.org \
    --cc=sboyd@kernel.org \
    --cc=sibis@codeaurora.org \
    --cc=vivek.gautam@codeaurora.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.