Ath10k Firmware crashed when connecting

Ath10k firmware crashes instantly when connecting using wlan since the latest updates.

[   64.025237] ath10k_pci 0000:07:00.0: firmware crashed! (guid c61c7c16-0d7a-4b5d-858a-1487aada5b27)
[   64.025244] ath10k_pci 0000:07:00.0: qca6174 hw2.1 target 0x05010000 chip_id 0x003405ff sub 105b:e08e
[   64.025246] ath10k_pci 0000:07:00.0: kconfig debug 0 debugfs 1 tracing 0 dfs 0 testmode 0
[   64.025561] ath10k_pci 0000:07:00.0: firmware ver SW_RM.1.1.1-00157-QCARMSWPZ-1 api 5 features ignore-otp,no-4addr-pad crc32 10bf8e08
[   64.025725] ath10k_pci 0000:07:00.0: board_file api 2 bmi_id N/A crc32 ae2e275a
[   64.025729] ath10k_pci 0000:07:00.0: htt-ver 3.1 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1
[   64.027758] ath10k_pci 0000:07:00.0: firmware register dump:
[   64.027764] ath10k_pci 0000:07:00.0: [00]: 0x05010000 0x00000000 0x0092E4DC 0xF8397212
[   64.027766] ath10k_pci 0000:07:00.0: [04]: 0x0092E4DC 0x00060130 0x00000018 0x0041A760
[   64.027769] ath10k_pci 0000:07:00.0: [08]: 0xF83971FE 0x00400000 0x00000000 0x000A5C88
[   64.027772] ath10k_pci 0000:07:00.0: [12]: 0x00000009 0x00000000 0x0096C09C 0x0096C0A7
[   64.027774] ath10k_pci 0000:07:00.0: [16]: 0x0096BDBC 0x009287BD 0x00000000 0x009287BD
[   64.027776] ath10k_pci 0000:07:00.0: [20]: 0x4092E4DC 0x0041A710 0x00000000 0x0F000000
[   64.027779] ath10k_pci 0000:07:00.0: [24]: 0x809432A7 0x0041A770 0x0040D400 0xC092E4DC
[   64.027782] ath10k_pci 0000:07:00.0: [28]: 0x80942BC4 0x0041A790 0xF83971FE 0x00400000
[   64.027784] ath10k_pci 0000:07:00.0: [32]: 0x80947BA7 0x0041A7B0 0x004050A8 0x0040E074
[   64.027787] ath10k_pci 0000:07:00.0: [36]: 0x809BDECC 0x0041A7D0 0x004050A8 0x0040E074
[   64.027789] ath10k_pci 0000:07:00.0: [40]: 0x8099638C 0x0041A7F0 0x004050A8 0x00000000
[   64.027792] ath10k_pci 0000:07:00.0: [44]: 0x80992076 0x0041A810 0x0044FD68 0x0046FFE8
[   64.027795] ath10k_pci 0000:07:00.0: [48]: 0x80996BD3 0x0041A830 0x0044FD68 0x00000000
[   64.027797] ath10k_pci 0000:07:00.0: [52]: 0x800B4405 0x0041A850 0x00422318 0x00005002
[   64.027800] ath10k_pci 0000:07:00.0: [56]: 0x809A6C34 0x0041A8E0 0x0042932C 0x0042CA20
[   64.027802] ath10k_pci 0000:07:00.0: Copy Engine register dump:
[   64.027816] ath10k_pci 0000:07:00.0: [00]: 0x00034400   1   1   3   3
[   64.027830] ath10k_pci 0000:07:00.0: [01]: 0x00034800   8   8 139 140
[   64.027844] ath10k_pci 0000:07:00.0: [02]: 0x00034c00   3   3  66  67
[   64.027858] ath10k_pci 0000:07:00.0: [03]: 0x00035000   8   8   9   8
[   64.027871] ath10k_pci 0000:07:00.0: [04]: 0x00035400  65  65  98  34
[   64.027885] ath10k_pci 0000:07:00.0: [05]: 0x00035800   0   0   0   0
[   64.027900] ath10k_pci 0000:07:00.0: [06]: 0x00035c00  15  15  15  15
[   64.027914] ath10k_pci 0000:07:00.0: [07]: 0x00036000   1   1   1   1
[   64.027947] ath10k_pci 0000:07:00.0: failed to create WMI vdev 0: -108
[   64.114825] ieee80211 phy0: Hardware restart was requested
[   65.529046] ath10k_pci 0000:07:00.0: device successfully recovered

Any ideas how to fix this?

Which were?

Ensure all packages are up-to-date and reboot. Try a different kernel.

I updates today after I was away for 2 weeks.

Already done. This is not fixing the problem

Btw: I saw firmware crashes before but I was still able to use WLAN, now I'm not.

I figured out it's somehow an issue in NetworkManager. I downgraded it and now it's working again.

Please report your working version

pacman -Q networkmanager

I used the downgrader aur package which downgraded to networkmanager 1.8.5dev+22+g5f2855fad-1

Just a guess here, since i also had some issues with some connections, a bit different, but yet once i edited the /etc/dhcpcd.conf on this section from:

# Use the hardware address of the interface for the Client ID.
#clientid
# or
# Use the same DUID + IAID as set in DHCPv6 for DHCPv4 ClientID as per RFC4361.
# Some non-RFC compliant DHCP servers do not reply with this set.
# In this case, comment out duid and enable clientid above.
duid

to

# Use the hardware address of the interface for the Client ID.
clientid
# or
# Use the same DUID + IAID as set in DHCPv6 for DHCPv4 ClientID as per RFC4361.
# Some non-RFC compliant DHCP servers do not reply with this set.
# In this case, comment out duid and enable clientid above.
#duid

my systems are hassle free regarding the connections

2 Likes

Fixed since latest stable updates.

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.

Forum kindly sponsored by