New warning `ath10k_pci 0000:3a:00.0: not found station for peer stats`

Paul Menzel pmenzel at molgen.mpg.de
Mon Feb 9 14:31:27 PST 2026


Dear Baochen,


Am 09.02.26 um 03:44 schrieb Baochen Qiang:

> On 2/7/2026 1:55 PM, Paul Menzel wrote:

>> Am 19.01.26 um 17:41 schrieb Paul Menzel:
>>
>>> Since January 10th, I have started seeing the warning below in
>>> my Linux logs, that reach back to September 24th, 2025:
>>>
>>>       [   37.108902] ath10k_pci 0000:3a:00.0: not found station for peer stats
>>>       [   37.108906] ath10k_pci 0000:3a:00.0: failed to parse stats info tlv: -22
>>>
>>> It started appearing with 6.19.0-rc4-00282-gb6151c4e60e5, the
>>> version running before is 6.19.0-rc4-00003-g3609fa95fb0f, but I
>>> do not see anything related in the commit list:>>>
>>>       git log --oneline 3609fa95fb0f...b6151c4e60e5
>>>
>>> The warning log from `drivers/net/wireless/ath/ath10k/wmi-tlv.c` has also been there
>>> since 2021.
>>> 
>>> Do you have an idea? Please find the output of `dmesg` attached.
>> 
>> Looking through the commit list from above again, commit
>> a203dbeeca15 (wifi: mac80211: collect station statistics earlier
>> when disconnect) probably introduced the new behavior.
> 
> is this error seen when disconnecting from AP?

I attached the logs in my first message. But yes, it looks like this:

     Feb 07 06:32:52 abreu kernel: wlp58s0: deauthenticating from 
74:1a:e0:e7:b4:c8 by local choice (Reason: 3=DEAUTH_LEAVING)
     Feb 07 06:32:52 abreu kernel: ath10k_pci 0000:3a:00.0: not found 
station for peer stats
     Feb 07 06:32:52 abreu kernel: ath10k_pci 0000:3a:00.0: failed to 
parse stats info tlv: -22
     Feb 07 06:32:52 abreu wpa_supplicant[846]: wlp58s0: 
CTRL-EVENT-DISCONNECTED bssid=74:1a:e0:e7:b4:c8 reason=3 locally_generated=1
     Feb 07 06:32:52 abreu wpa_supplicant[846]: BSSID 74:1a:e0:e7:b4:c8 
ignore list count incremented to 2, ignoring for 10 seconds

> did you try with that commit reverted?
Yes, I tried it now with Linux 6.19 and reverting the commit. The 
warnings are gone now.

Are you able to reproduce the issue? What devices are you testing with?


Kind regards,

Paul



More information about the ath10k mailing list