From: Steven Rostedt <rostedt@goodmis.org>
To: Sai Prakash Ranjan <saiprakash.ranjan@codeaurora.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>, 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: Thu, 18 Oct 2018 09:17:06 -0400 [thread overview]
Message-ID: <20181018091706.62310b38@gandalf.local.home> (raw)
In-Reply-To: <58d2474c-53cd-e6cb-2d25-db38d1a88da6@codeaurora.org>
On Thu, 18 Oct 2018 10:51:18 +0530
Sai Prakash Ranjan <saiprakash.ranjan@codeaurora.org> wrote:
> > So something else is causing an issue besides just msm_read.
> >
> > Can you do an objdump -dr of the entire vmlinux binary and gzip it and
> > post it somewhere. Not sure if it would be too big to email. You could
> > try sending it to me privately. I'd like to see the binary that you are
> > using.
> >
>
> I have sent the objdump and dot config to you privately.
Thanks. I don't see anything that pops out, but then again, my arm asm
foo is very rusty (it has been literally decades since I did any arm
asm). I wonder if it could simply be a timing issue?
ffff0000086eb538 <msm_read.isra.1>:
ffff0000086eb538: a9be7bfd stp x29, x30, [sp,#-32]!
ffff0000086eb53c: 910003fd mov x29, sp
ffff0000086eb540: a90153f3 stp x19, x20, [sp,#16]
ffff0000086eb544: aa0003f4 mov x20, x0
ffff0000086eb548: 2a0103f3 mov w19, w1
ffff0000086eb54c: aa1e03e0 mov x0, x30
ffff0000086eb550: 97e6bae4 bl ffff00000809a0e0 <_mcount>
The above is changed to nop on boot, but then to:
bl ftrace_caller
When ftrace is enabled.
ffff0000086eb554: 8b334280 add x0, x20, w19, uxtw
ffff0000086eb558: b9400000 ldr w0, [x0]
ffff0000086eb55c: a94153f3 ldp x19, x20, [sp,#16]
ffff0000086eb560: a8c27bfd ldp x29, x30, [sp],#32
ffff0000086eb564: d65f03c0 ret
ffff00000809a0e4 <ftrace_caller>:
ffff00000809a0e4: a9bf7bfd stp x29, x30, [sp,#-16]!
ffff00000809a0e8: 910003fd mov x29, sp
ffff00000809a0ec: d10013c0 sub x0, x30, #0x4
ffff00000809a0f0: f94003a1 ldr x1, [x29]
ffff00000809a0f4: f9400421 ldr x1, [x1,#8]
ffff00000809a0f8: d1001021 sub x1, x1, #0x4
ffff00000809a0fc <ftrace_call>:
ffff00000809a0fc: d503201f nop
The above nop gets patched to:
bl ftrace_ops_no_ops
Which will iterate through all the registered functions.
ffff00000809a100 <ftrace_graph_call>:
ffff00000809a100: d503201f nop
The above only gets set when function graph tracer is enabled, which it
is not in this case.
ffff00000809a104: a8c17bfd ldp x29, x30, [sp],#16
ffff00000809a108: d65f03c0 ret
Anyone see any problems here?
-- Steve
next prev parent reply other threads:[~2018-10-18 13:17 UTC|newest]
Thread overview: 43+ 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
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-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 [this message]
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=20181018091706.62310b38@gandalf.local.home \
--to=rostedt@goodmis.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=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=saiprakash.ranjan@codeaurora.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).