Issues with ath12 wifi driver on WCN7850
Rahul Balakrishnan
rahulbal29 at gmail.com
Fri Nov 6 04:07:34 PST 2026
Hello Mr Johnson,
I have been encountering an issue with my Qualcomm Wi-Fi chipset. Here
is my currrent system configuration.
Environment
===========
Board: MSI PRO X870E-P WIFI (MS-7E70), BIOS 2.A52
Device: 17cb:1107, subsystem 105b:e0f7 (Foxconn)
"Wi-Fi 7 Hardware name: wcn7850 hw2.0"
chip_id 0x2 chip_family 0x4 board_id 0xff soc_id 0x40170200
Firmware: fw_version 0x1103006c fw_build_timestamp 2026-03-06 09:10
WLAN.HMT.1.1.c7-00108-QCAHMTSWPL_V1.0_V2.0_SILICONZ_UPSTREAM-3
(Arch linux-firmware 20261019)
Kernel: 7.2.11-arch1-1 (Arch distribution kernel, not yet
reproduced on mainline)
Userspace: iwd 3.12
AP: 5 GHz, 5240 MHz (channel 48), beacon interval 100 TU, PMF
in use
Symptoms
=========
The problem surfaces after S3 resume. The AP beacon is missed about
~12 seconds after establishing a link with the AP. At that point, the
AP disconnects. It then loops back into scanning for available
networks, and the cycle repeats. The issue is infrequent but it's
rather annoying, which is why I decided to investigate it.
Here is a Journal log of what I see with (debug_mask=0x1132)
03:16:32.917 keys installed, "connection done, update reg rules"
03:16:32.935 txpower fetched from firmware 1 dBm
03:16:44.567 wmi roam event vdev 0 reason 2 rssi -128 <- beacon miss
03:16:46.397 5x mgmt rx stype d0 (protected action, len 49), snr -44
03:16:46.575 scan started (iwd roam scan after CQM beacon loss)
03:16:46.586 mgmt rx stype 50 (probe response, len 708), 5240 MHz,
snr -44
03:16:47.574 wlan0: Connection to AP xx:xx:xx:xx:xx:xx lost
(deauth reason 4, from_ap: false)
I initially reduced the signal strength required to maintain a link.
Then I assumed the kernel was setting the module to low power mode. I
disabled low power mode. That didn't fix the issue. I noticed that we
still receive management messages from the AP. So I looked into the
driver code and saw that "no beacon forwarded" is treated as "AP
gone," which might be the issue.
I might try to get this to Qualcomm too just in case through a channel I know.
Regards,
Rahul
More information about the ath12k
mailing list