qca6174 hw3.2 target 0x05030000 chip_id 0x00340aff: firmware crashed!

Baochen Qiang quic_bqiang at quicinc.com
Sun Mar 23 20:29:44 PDT 2025 


On 3/23/2025 7:41 PM, Paul Menzel wrote:
> Dear Linux folks,
> 
> 
> Am 08.12.24 um 23:21 schrieb Paul Menzel:
> 
>> Today the Wi-Fi connection stopped working, and the logs contained:
>>
>>      [44177.000699] ath10k_pci 0000:3a:00.0: firmware crashed! (guid
>> 1b4a40c5-4495-4c5b-9df9-b7395848239c)
>>      [44177.000720] ath10k_pci 0000:3a:00.0: qca6174 hw3.2 target 0x05030000 chip_id
>> 0x00340aff sub 1a56:1535
>>      [44177.000731] ath10k_pci 0000:3a:00.0: kconfig debug 0 debugfs 0 tracing 0 dfs 0
>> testmode 0
>>      [44177.002450] ath10k_pci 0000:3a:00.0: firmware ver WLAN.RM.4.4.1-00309- api 6
>> features wowlan,ignore-otp,mfp crc32 0793bcf2
>>      [44177.004168] ath10k_pci 0000:3a:00.0: board_file api 2 bmi_id N/A crc32 d2863f91
>>      [44177.004176] ath10k_pci 0000:3a:00.0: htt-ver 3.87 wmi-op 4 htt- op 3 cal otp
>> max-sta 32 raw 0 hwcrypto 1
>>      [44177.014494] ath10k_pci 0000:3a:00.0: failed to get memcpy hi address for
>> firmware address 4: -16
>>      [44177.014498] ath10k_pci 0000:3a:00.0: failed to read firmware dump area: -16
>>      [44177.014500] ath10k_pci 0000:3a:00.0: Copy Engine register dump:
>>      [44177.014508] ath10k_pci 0000:3a:00.0: [00]: 0x00034400  12  12 3   3
>>      [44177.014517] ath10k_pci 0000:3a:00.0: [01]: 0x00034800  19  19 64  65
>>      [44177.014525] ath10k_pci 0000:3a:00.0: [02]: 0x00034c00  39  37 36  37
>>      [44177.014532] ath10k_pci 0000:3a:00.0: [03]: 0x00035000  20  20 22  20
>>      [44177.014540] ath10k_pci 0000:3a:00.0: [04]: 0x00035400 6457 6457 222 158
>>      [44177.014548] ath10k_pci 0000:3a:00.0: [05]: 0x00035800   0   0 64   0
>>      [44177.014556] ath10k_pci 0000:3a:00.0: [06]: 0x00035c00  29  29 0   0
>>      [44177.014563] ath10k_pci 0000:3a:00.0: [07]: 0x00036000   1   0 1   0
>>      [44177.109219] ieee80211 phy0: Hardware restart was requested
>>      [44177.429445] ath10k_pci 0000:3a:00.0: device successfully recovered
>>
>> Please find the output of `dmesg` with two firmware crashes attached. Looking through my
>> logs since September 20th with Linux 6.11-rcX, this is not the first firmware crash. The
>> `guid` value differs pairwaise between each of them.
> 
> Since my message in December I found two more crashes in the logs:
> 
>     Jan 20 13:11:11 abreu kernel: ath10k_pci 0000:3a:00.0: firmware crashed! (guid
> 0290afa9-63d2-4d66-b355-de2e12f96f4b)
> 
>     Feb 02 20:34:20 abreu kernel: ath10k_pci 0000:3a:00.0: firmware crashed! (guid
> 4c1fb23a-8d0e-4c03-8dfb-a5fa9ad3d2bc)
> 
> I am now in a WLAN with Cisco access points, and get a few crashes:
> 
>     Mär 21 14:01:36 abreu kernel: ath10k_pci 0000:3a:00.0: firmware crashed! (guid
> bc05fa56-0033-4fca-bfc0-660568f560fd)
>     Mär 23 11:54:24 abreu kernel: ath10k_pci 0000:3a:00.0: firmware crashed! (guid
> b6eb8244-0e48-4785-8247-901e833ed59a)
> 
>     [42307.272046] ath10k_pci 0000:3a:00.0: firmware crashed! (guid bc05fa56-0033-4fca-
> bfc0-660568f560fd)
>     [42307.272078] ath10k_pci 0000:3a:00.0: qca6174 hw3.2 target 0x05030000 chip_id
> 0x00340aff sub 1a56:1535
>     [42307.272094] ath10k_pci 0000:3a:00.0: kconfig debug 0 debugfs 0 tracing 0 dfs 0
> testmode 0
>     [42307.272452] ath10k_pci 0000:3a:00.0: firmware ver WLAN.RM.4.4.1-00309- api 6
> features wowlan,ignore-otp,mfp crc32 0793bcf2
>     [42307.272825] ath10k_pci 0000:3a:00.0: board_file api 2 bmi_id N/A crc32 d2863f91
>     [42307.272834] ath10k_pci 0000:3a:00.0: htt-ver 3.87 wmi-op 4 htt-op 3 cal otp max-sta
> 32 raw 0 hwcrypto 1
>     [42307.283011] ath10k_pci 0000:3a:00.0: failed to get memcpy hi address for firmware
> address 4: -16
>     [42307.283024] ath10k_pci 0000:3a:00.0: failed to read firmware dump area: -16
>     [42307.283034] ath10k_pci 0000:3a:00.0: Copy Engine register dump:
>     [42307.283050] ath10k_pci 0000:3a:00.0: [00]: 0x00034400  12  12 3   3
>     [42307.283070] ath10k_pci 0000:3a:00.0: [01]: 0x00034800   5   5 82  83
>     [42307.283088] ath10k_pci 0000:3a:00.0: [02]: 0x00034c00  53  47 45  46
>     [42307.283104] ath10k_pci 0000:3a:00.0: [03]: 0x00035000  13  13 14  12
>     [42307.283120] ath10k_pci 0000:3a:00.0: [04]: 0x00035400  67  67 98  34
>     [42307.283135] ath10k_pci 0000:3a:00.0: [05]: 0x00035800   0   0 64   0
>     [42307.283151] ath10k_pci 0000:3a:00.0: [06]: 0x00035c00  22  22 24  24
>     [42307.283167] ath10k_pci 0000:3a:00.0: [07]: 0x00036000   1   1 1   0
>     [42307.371777] ieee80211 phy0: Hardware restart was requested
>     [42309.383940] ath10k_pci 0000:3a:00.0: timed out waiting peer stats info
>     [42309.690205] ath10k_pci 0000:3a:00.0: device successfully recovered
>     [43924.050746] wlp58s0: deauthenticating from 48:2f:6b:7a:61:54 by local choice
> (Reason: 3=DEAUTH_LEAVING)
> 
> Baochen, do you have an idea? Also how to fix the dump errors?

could you share AP model? and any specific test steps you hit it?

regarding the dump error, I think it is due to unresponsive firmware since it crashes.
We'd better focus on the crash first.


> 
> Jamie (Cc:) also reported this this January 2025 *Ath10k firmware crash* [1].
> 
> 
> Kind regards,
> 
> Paul
> 
> 
>> PS: Other times:
>>
>> -- Boot caea92a03f6d4776926f451f8281ea31 --
>> Sep 26 12:12:01 abreu kernel: ath10k_pci 0000:3a:00.0: firmware crashed! (guid
>> 6eb9dc57-1295-4a53-b71d-a8aeba7281a1)
>> Sep 26 12:32:58 abreu kernel: ath10k_pci 0000:3a:00.0: firmware crashed! (guid
>> c4a6c6a2-3cf4-445e-b16b-2baa35d547f3)
>> Sep 26 12:46:02 abreu kernel: ath10k_pci 0000:3a:00.0: firmware crashed! (guid
>> b8c8a5f0-7ff7-45c3-8ecb-7ba8074ba6f7)
>>
>> -- Boot 26e7175e65254625bf58276e9532773e --
>> Okt 23 12:11:20 abreu kernel: ath10k_pci 0000:3a:00.0: firmware crashed! (guid
>> 1b3f438c-339c-4ad1-9d82-92a96a07c3c2)
>>
>> Earliest crash:
>>
>> Sep 26 10:41:36 abreu kernel: Linux version 6.11.0-07273-g1e7530883cd2
>> (build at bohemianrhapsody.molgen.mpg.de) (gcc (Debian 14.2.0-5) 14.2.0, GNU ld (GNU
>> Binutils for Debian) 2.43.1) #12 SMP PREEMPT_DYNAMIC Sun Sep 22 09:57:36 CEST 2024
>> […]
>> Sep 26 12:12:01 abreu kernel: ath10k_pci 0000:3a:00.0: firmware crashed! (guid
>> 6eb9dc57-1295-4a53-b71d-a8aeba7281a1)
>> Sep 26 12:12:01 abreu kernel: ath10k_pci 0000:3a:00.0: qca6174 hw3.2 target 0x05030000
>> chip_id 0x00340aff sub 1a56:1535
>> Sep 26 12:12:01 abreu kernel: ath10k_pci 0000:3a:00.0: kconfig debug 0 debugfs 0 tracing
>> 0 dfs 0 testmode 0
>> Sep 26 12:12:01 abreu kernel: ath10k_pci 0000:3a:00.0: firmware ver WLAN.RM.4.4.1-00309-
>> api 6 features wowlan,ignore-otp,mfp crc32 0793bcf2
>> Sep 26 12:12:01 abreu kernel: ath10k_pci 0000:3a:00.0: board_file api 2 bmi_id N/A crc32
>> d2863f91
>> Sep 26 12:12:01 abreu kernel: ath10k_pci 0000:3a:00.0: htt-ver 3.87 wmi-op 4 htt-op 3
>> cal otp max-sta 32 raw 0 hwcrypto 1
>> Sep 26 12:12:01 abreu kernel: ath10k_pci 0000:3a:00.0: failed to get memcpy hi address
>> for firmware address 4: -16
>> Sep 26 12:12:01 abreu kernel: ath10k_pci 0000:3a:00.0: failed to read firmware dump
>> area: -16
>> Sep 26 12:12:01 abreu kernel: ath10k_pci 0000:3a:00.0: Copy Engine register dump:
>> Sep 26 12:12:01 abreu kernel: ath10k_pci 0000:3a:00.0: [00]: 0x00034400 12  12   3   3
>> Sep 26 12:12:01 abreu kernel: ath10k_pci 0000:3a:00.0: [01]: 0x00034800 28  28 265 266
>> Sep 26 12:12:01 abreu kernel: ath10k_pci 0000:3a:00.0: [02]: 0x00034c00 29  27  90  91
>> Sep 26 12:12:01 abreu kernel: ath10k_pci 0000:3a:00.0: [03]: 0x00035000 15  15  17  15
>> Sep 26 12:12:01 abreu kernel: ath10k_pci 0000:3a:00.0: [04]: 0x00035400 3887 3887 217 153
>> Sep 26 12:12:01 abreu kernel: ath10k_pci 0000:3a:00.0: [05]: 0x00035800   0   0  64   0
>> Sep 26 12:12:01 abreu kernel: ath10k_pci 0000:3a:00.0: [06]: 0x00035c00 20  20  16  16
>> Sep 26 12:12:01 abreu kernel: ath10k_pci 0000:3a:00.0: [07]: 0x00036000   1   0   1   0
> 
> 
> [1]: https://lore.kernel.org/all/a5b15899-b214-403b-a1b2-84a948e776ef@stimulussoft.com/

More information about the ath10k mailing list