linux-kernel - Re: Crash in msm serial on dragonboard with ftrace bootargs

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20181016144123.24c47b38@gandalf.local.home>
Date:   Tue, 16 Oct 2018 14:41:23 -0400
From:   Steven Rostedt <rostedt@...dmis.org>
To:     Sai Prakash Ranjan <saiprakash.ranjan@...eaurora.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 Tue, 16 Oct 2018 23:55:14 +0530
Sai Prakash Ranjan <saiprakash.ranjan@...eaurora.org> wrote:

> On 10/16/2018 11:46 PM, Steven Rostedt wrote:
> > 
> > [ Removed ivan.ivanov@...aro.org due to getting mail delivery errors ]
> > 
> > On Tue, 16 Oct 2018 23:35:00 +0530
> > Sai Prakash Ranjan <saiprakash.ranjan@...eaurora.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*"

Does it crash with just "f*" or "g*" or any singularity of the above?

Hmm, I wonder if it is from tracing msm_read?

-- Steve


> 
> 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)
>