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>, 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:55:14 +0530	[thread overview]
Message-ID: <accdce6d-8fd2-9f15-d4cd-704cbf0b32eb@codeaurora.org> (raw)
In-Reply-To: <20181016141610.639b9000@gandalf.local.home>

On 10/16/2018 11:46 PM, Steven Rostedt wrote:
> 
> [ Removed ivan.ivanov@linaro.org due to getting mail delivery errors ]
> 
> On Tue, 16 Oct 2018 23:35:00 +0530
> Sai Prakash Ranjan <saiprakash.ranjan@codeaurora.org> wrote:
> 
>> Ok got it, this sounds fun. I'll give it a try.
> 
> Awesome, I'm looking forward to seeing what you come up with.
> 

Now, I can trigger this crash reboot with "ftrace=function 
ftrace_filter=f*,g*,h*,i*,j*,k*,l*,m*,n*,o*,p*,q*"

And pstore dmesg log gives slightly different backtrace than 
before(i.e., uart_add_one_port+0x374/0x4c8):

<4>[    1.976945] EINJ: ACPI disabled.
<6>[    2.070011] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
<6>[    2.087353] SuperH (H)SCI(F) driver initialized
<6>[    2.093708] msm_serial 78af000.serial: msm_serial: detected port #1
<6>[    2.093901] msm_serial 78af000.serial: uartclk = 19200000
<6>[    2.099078] 78af000.serial: ttyMSM1 at MMIO 0x78af000 (irq = 9, 
base_baud = 1200000) is a MSM
<6>[    2.108386] msm_serial 78b0000.serial: msm_serial: detected port #0
<6>[    2.113076] msm_serial 78b0000.serial: uartclk = 7372800
<6>[    2.119300] 78b0000.serial: ttyMSM0 at MMIO 0x78b0000 (irq = 10, 
base_baud = 460800) is a MSM
<0>[    2.119769] Internal error: synchronous external abort: 96000010 
[#1] PREEMPT SMP
<4>[    2.119772] Modules linked in:
<4>[    2.119780] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 
4.19.0-rc8-00008-ge033b9909fff-dirty #2
<4>[    2.119785] Hardware name: Qualcomm Technologies, Inc. APQ 8016 
SBC (DT)
<4>[    2.119789] pstate: 40000085 (nZcv daIf -PAN -UAO)
<4>[    2.119792] pc : msm_read.isra.2+0x20/0x50
<4>[    2.119796] lr : msm_read.isra.2+0x1c/0x50
<4>[    2.119799] sp : ffff000008033760
<4>[    2.119802] x29: ffff000008033760 x28: ffff000009486018
<4>[    2.119809] x27: 0000000000000001 x26: ffff7dfffe7ff070
<4>[    2.119816] x25: 0000000000000062 x24: ffff000009486000
<4>[    2.119824] x23: 0000000000000000 x22: ffff00000978e190
<4>[    2.119831] x21: ffff0000095e8228 x20: 0000000000000062
<4>[    2.119838] x19: ffff7dfffe7ff008 x18: ffffffffffffffff
<4>[    2.119845] x17: 0000000000000000 x16: 0000000000000000
<4>[    2.119852] x15: ffff0000094a96c8 x14: 3d20647561625f65
<4>[    2.119859] x13: 736162202c303120 x12: 3d20717269282030
<4>[    2.119866] x11: 3030306238377830 x10: 0000000000000134
<4>[    2.119874] x9 : ffff80003c356400 x8 : ffff000008033680
<4>[    2.119881] x7 : ffff80003c354100 x6 : 00000000000d9b72
<4>[    2.119888] x5 : 0000000000000150 x4 : ffff80003bc8f000
<4>[    2.119895] x3 : ffff80003c356498 x2 : 0000000000000000
<4>[    2.119902] x1 : ffff80003bf10000 x0 : 0000000000000800
<0>[    2.119911] Process swapper/0 (pid: 1, stack limit = 
0x(____ptrval____))
<4>[    2.119914] Call trace:
<4>[    2.119917]  msm_read.isra.2+0x20/0x50
<4>[    2.119920]  msm_reset_dm_count+0x44/0x80
<4>[    2.119924]  __msm_console_write+0x1c8/0x1d0
<4>[    2.119928]  msm_serial_early_write_dm+0x3c/0x50
<4>[    2.119931]  console_unlock.part.6+0x468/0x528
<4>[    2.119935]  vprintk_emit+0x210/0x218
<4>[    2.119938]  vprintk_default+0x48/0x58
<4>[    2.119942]  vprintk_func+0xf0/0x1c0
<4>[    2.119945]  printk+0x74/0x94
<4>[    2.119949]  uart_add_one_port+0x374/0x4c8
<4>[    2.119952]  msm_serial_probe+0x140/0x1c8
<4>[    2.119955]  platform_drv_probe+0x58/0xb0
<4>[    2.119959]  really_probe+0x1f4/0x3c8
<4>[    2.119963]  driver_probe_device+0x12c/0x150
<4>[    2.119966]  __driver_attach+0x144/0x148
<4>[    2.119969]  bus_for_each_dev+0x78/0xe0
<4>[    2.119973]  driver_attach+0x30/0x40
<4>[    2.119976]  bus_add_driver+0x1c8/0x2a8
<4>[    2.119979]  driver_register+0x68/0x118
<4>[    2.119983]  __platform_driver_register+0x54/0x60
<4>[    2.119987]  msm_serial_init+0x40/0x70
<4>[    2.119990]  do_one_initcall+0x54/0x248
<4>[    2.119993]  kernel_init_freeable+0x210/0x378
<4>[    2.119997]  kernel_init+0x18/0x118
<4>[    2.120000]  ret_from_fork+0x10/0x1c
<0>[    2.120004] Code: aa1e03e0 8b214273 97e61727 d503201f (b9400260)

-- 
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:25 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
2018-10-16 18:16             ` Steven Rostedt
2018-10-16 18:25               ` Sai Prakash Ranjan [this message]
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=accdce6d-8fd2-9f15-d4cd-704cbf0b32eb@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=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.