linux-kernel - Re: qca6174 hw3.2 target 0x05030000 chip

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] [day] [month] [year] [list]

Message-ID: <aa30f484-7269-4fb9-bdd2-8b7ab75061a9@oss.qualcomm.com>
Date: Mon, 13 Oct 2025 09:49:52 +0800
From: Baochen Qiang <baochen.qiang@....qualcomm.com>
To: Paul Menzel <pmenzel@...gen.mpg.de>, Jeff Johnson <jjohnson@...nel.org>
Cc: ath10k@...ts.infradead.org, LKML <linux-kernel@...r.kernel.org>,
        jamie@...mulussoft.com
Subject: Re: qca6174 hw3.2 target 0x05030000 chip_id 0x00340aff: firmware
 crashed!



On 10/10/2025 9:12 PM, Paul Menzel wrote:
> Dear Baochen,
> 
> 
> Am 21.07.25 um 05:21 schrieb Baochen Qiang:
> 
>> On 7/20/2025 4:43 PM, Paul Menzel wrote:
> 
>>> Am 14.05.25 um 10:08 schrieb Paul Menzel:
> 
> […]
> 
>>>> Were you or the firmware team able to pinpoint the problem, and
>>>> come up with a fix? Is there any logging I can enable to help
>>>> with debugging?
>>>
>>> It also happens with a Telekom Speedport Smart 3 (Arcadyan
>>> Corporation) router. The firmware crashed five more times since
>>> June. A reliable Wi-Fi connection would be really appreciated.
>>> Could you send me a debug firmware, so the firmware developers
>>> have it easier to fix it?
>>
>> Paul, we are working on getting legal approval on collecting
>> necessary information, such as firmware dump etc, from community.
>> Once done we will share guides to collect them to debug further.
> 
> I just wanted to know, if there was a conclusion yet.
> 

unfortunately, not yet

> 
> Kind regards,
> 
> Paul
> 
> 
> PS: I set debug_mask to 0xffffffff a while back, and it logged so much, that my old boot
> logs are gone from the systemd journal now. ;-)
> 
>     echo 0xffffffff | sudo tee /sys/module/ath10k_core/parameters/debug_mask
> 
> Any hint on what to set, when the crashes happen?

to collect core dump, you need to load ath10k with coredump_mask = 0x7

	modprobe ath10k coredump_mask = 0x7
	modprobe ath10k_pci