Re: btqca: crash with linux-next on bt power down

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



#regzbot: introduced:
973dd9c4db4746200f88fe46e30eada7054fdbea..84f9288208dfcd955446060a53add15b9e01af4e

On Mon, 29 Jul 2024 at 13:21, Paul Menzel <pmenzel@xxxxxxxxxxxxx> wrote:
> Am 29.07.24 um 04:11 schrieb Dmitry Baryshkov:
>
> > On Qualcomm Dragonboard 820c (APQ8096, QCA6174) soon after the boot I
> > observe the following crash:
> >
> > Unable to handle kernel NULL pointer dereference at virtual address 0000000000000018
> > Mem abort info:
> >    ESR = 0x0000000096000006
> >    EC = 0x25: DABT (current EL), IL = 32 bits
> >    SET = 0, FnV = 0
> >    EA = 0, S1PTW = 0
> >    FSC = 0x06: level 2 translation fault
> > Data abort info:
> >    ISV = 0, ISS = 0x00000006, ISS2 = 0x00000000
> >    CM = 0, WnR = 0, TnD = 0, TagAccess = 0
> >    GCS = 0, Overlay = 0, DirtyBit = 0, Xs = 0
> > user pgtable: 4k pages, 48-bit VAs, pgdp=000000010da63000
> > [0000000000000018] pgd=080000010da62003, p4d=080000010da62003, pud=080000010da61003, pmd=0000000000000000
> > Internal error: Oops: 0000000096000006 [#1] PREEMPT SMP
> > Modules linked in: hci_uart btqca
> > CPU: 2 UID: 0 PID: 66 Comm: kworker/u19:0 Not tainted 6.10.0-next-20240726-13923-gd3ce7ebd61f9-dirty #2722
>
> I am unable to find the commit. Your tree also seems dirty. What is the
> last working commit?

Checked the commit range on the linux-bluetooth branch, hope this helps.

>
> > Hardware name: Qualcomm Technologies, Inc. DB820c (DT)
> > Workqueue: hci0 hci_power_off
> > pstate: 60000005 (nZCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)
> > pc : qca_power_shutdown+0x8c/0x210 [hci_uart]
> > lr : qca_power_shutdown+0x7c/0x210 [hci_uart]
> > sp : ffff8000836f3c50
> > x29: ffff8000836f3c50 x28: ffff00008337b900 x27: ffff000084085000
> > x26: 0000000000000000 x25: 0000000000000000 x24: ffff00009276f800
> > x23: ffff00009276f918 x22: ffff000081e1fc80 x21: 0000000000000001
> > x20: ffff000081e1fc80 x19: ffff00009276f800 x18: ffff0000de422170
> > x17: 0000000000061d88 x16: 0000000000000000 x15: 0000000000000001
> > x14: ffff0000813b3580 x13: 0000000000000000 x12: 00000000000001a0
> > x11: 0000000000000001 x10: 00000000000013f0 x9 : 0000000000000000
> > x8 : ffff8000836f3b40 x7 : 0000000000000000 x6 : ffff800080d52e88
> > x5 : 0000000000000000 x4 : ffff8000836f0000 x3 : 0000000000000000
> > x2 : 0000000000000000 x1 : ffff00008f56d000 x0 : 0000000000000000
> > Call trace:
> >   qca_power_shutdown+0x8c/0x210 [hci_uart]
> >   qca_power_off+0x70/0xfb8 [hci_uart]
> >   hci_dev_close_sync+0x4b0/0x6d8
> >   hci_power_off+0x2c/0x44
> >   process_one_work+0x20c/0x62c
> >   worker_thread+0x1bc/0x36c
> >   kthread+0x120/0x124
> >   ret_from_fork+0x10/0x20
> > Code: f9400681 b4000441 f9403c36 f94102c0 (f9400c00)
> > ---[ end trace 0000000000000000 ]---
> If you can reproduce this, bisecting this would be great.
>
>
> Kind regards,
>
> Paul



-- 
With best wishes
Dmitry




[Index of Archives]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [Linux for Sparc]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux MIPS]     [ECOS]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux