linux-kernel - Re: rt8000usb driver issue (maybe interaction with other drivers)

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: <c68ff294-0060-4621-82d9-61b6bbc12078@gmail.com>
Date:   Tue, 3 Oct 2023 07:01:25 +0700
From:   Bagas Sanjaya <bagasdotme@...il.com>
To:     Stanislaw Gruszka <stf_xl@...pl>
Cc:     enc0der <enc0der@...il.com>,
        Linux Regressions <regressions@...ts.linux.dev>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux Wireless <linux-wireless@...r.kernel.org>
Subject: Re: rt8000usb driver issue (maybe interaction with other drivers)

On 03/10/2023 01:50, Stanislaw Gruszka wrote:
> 
> (cc list is too big, I shrink it)
> 
> On Sun, Oct 01, 2023 at 12:12:02PM +0700, Bagas Sanjaya wrote:
>> On Sat, Sep 30, 2023 at 06:04:22PM -0400, enc0der wrote:
>>> [   28.071586] lr : arm_smmu_dma_sync+0x40/0x70
>>> [   28.075965] sp : ffff8000100231a0
>>> [   28.079365] x29: 0000000000001000 x28: ffff4655c01d0ec0
>>> [   28.084817] x27: ffffaced1f227000 x26: ffff4655c6ee32c0
>>> [   28.090270] x25: 0000000000000000 x24: ffffaced1e405858
>>> [   28.095718] x23: ffff46572e84ae00 x22: ffff4655c6ee2c40
>>> [   28.101165] x21: ffff4655c82c3480 x20: ffffaced1db49e08
>>> [   28.106618] x19: ffff8000100231c0 x18: 0000000000010101
>>> [   28.112073] x17: 0000000000cccccc x16: ffffaced1d23382c
>>> [   28.117520] x15: 0000000000000000 x14: 0000000000000000
>>> [   28.122970] x13: 0000000000000001 x12: 0000000000000000
>>> [   28.128421] x11: 0000000000000008 x10: 0000000000000ab0
>>> [   28.133863] x9 : ffff800010023180 x8 : ffff4655c6ee3750
>>> [   28.139309] x7 : 000000067eb29c20 x6 : 0000000000000238
>>> [   28.144763] x5 : 00000000410fd420 x4 : 0000000000f0000f
>>> [   28.150214] x3 : 0000000000001000 x2 : ffff4655c82c3480
>>> [   28.155658] x1 : ffffaced1db49e08 x0 : ffff465704c37558
>>> [   28.161107] Call trace:
>>> [   28.163620]  0x1000
>>> [   28.165777] Code: bad PC value
>>> [   28.168911] ---[ end trace 62dc42c98ec427ca ]---
>>> [   28.183964] Kernel panic - not syncing: Oops: Fatal exception
>>> [   28.189864] SMP: stopping secondary CPUs
>>> [   29.275883] SMP: failed to stop secondary CPUs 0-5
>>> [   29.280811] Kernel Offset: 0x2ced0d200000 from 0xffff800010000000
> 
> This actually suggest that the issue is somewhere in the core.
> But again, without full logs we can not be sure.
> 

The reason why I added RCU subsystem maintainers to the Cc: list
was because the log the reporter provided points warning to
kernel/rcu/tree_plugin.h.

Thanks.

-- 
An old man doll... just what I always wanted! - Clara