Hi, I'm trying AVM Fritz!Box 4040 (OpenWrt 18.06 snapshot) and Zyxel NBG6617 (OpenWrt master branch) and with both I have hundreds of these messages in the log:
kern.warn kernel: [87771.917049] ath10k_ahb a000000.wifi: Invalid VHT mcs 15 peer stats
Everything seems to work properly, even the wifi!
Where can I report this problem?
Thanks
It's the firmware for the 2.4 GHz QCA4019 radio.
The file is located at "lib/firmware/ath10k/QCA4019/hw1.0/firmware-5.bin"
The version used by OpenWRT is 3.4/firmware-5.bin_10.4-3.4-00104
I replaced the file by 3.5.3/firmware-5.bin_10.4-3.5.3-00057
and the messages are gone.
Now, I only receive this message once a day:
[100573.985666] ath10k_ahb a000000.wifi: Invalid peer id 18 peer stats buffer
There are more firmware versions if the one I linked doesn't work for you.
@luaraneda many thanks for your help, now it's much better!
You've also tried 3.6/firmware-5.bin_10.4-3.6-00140 ?
If I remember correctly, I tried that firmware not for a long time, because I flashed a new image to my router.
OK now I'm trying 3.6/firmware-5.bin_10.4-3.6-00140, I'll let you know if there are any problems.
On log I see firmware-6.bin failed with error -2 
[ 19.755076] ath10k_ahb a000000.wifi: Direct firmware load for ath10k/QCA4019/hw1.0/firmware-6.bin failed with error -2
[ 19.755156] ath10k_ahb a000000.wifi: Falling back to user helper
[ 20.301583] firmware ath10k!QCA4019!hw1.0!firmware-6.bin: firmware_loading_store: map pages failed
[ 20.838052] ath10k_ahb a000000.wifi: qca4019 hw1.0 target 0x01000000 chip_id 0x003b00ff sub 0000:0000
[ 20.838413] ath10k_ahb a000000.wifi: kconfig debug 0 debugfs 1 tracing 0 dfs 1 testmode 1
[ 20.895929] ath10k_ahb a000000.wifi: firmware ver 10.4-3.6-00140 api 5 features no-p2p,mfp,peer-flow-ctrl,btcoex-param,allows-mesh-bcast,no-ps crc32 ba79b746
[ 20.957360] ath10k_ahb a000000.wifi: board_file api 2 bmi_id 0:16 crc32 83549421
[ 22.354774] ath10k_ahb a000000.wifi: htt-ver 2.2 wmi-op 6 htt-op 4 cal pre-cal-file max-sta 512 raw 0 hwcrypto 1
[ 22.384724] ath: EEPROM regdomain: 0x0
[ 22.384801] ath: EEPROM indicates default country code should be used
[ 22.384847] ath: doing EEPROM country->regdmn map search
With 3.5.3/firmware-5.bin_10.4-3.5.3-00057 do you have same features?
no-p2p,mfp,peer-flow-ctrl,btcoex-param,allows-mesh-bcast,no-ps
Thanks
I see now that @nbd is the package maintainer, please can you update the firmware before 18.06 release?
Thanks
For 10.4-3.4-00104, which is the current version on OpenWRT:
[ 27.503487] ath10k_ahb a000000.wifi: firmware ver 10.4-3.4-00104 api 5 features no-p2p,mfp,peer-flow-ctrl,btcoex-param,allows-mesh-bcast,no-ps crc32 6c332c67
For 10.4-3.5.3-00057
[ 24.697672] ath10k_ahb a000000.wifi: firmware ver 10.4-3.5.3-00057 api 5 features no-p2p,mfp,peer-flow-ctrl,btcoex-param,allows-mesh-bcast,no-ps crc32 6a15d64d
So yes, I have the same firmware features.
24h with firmware 3.6/firmware-5.bin_10.4-3.6-00140, 62GB trasfered over 2.4 GHz (12 clients) and 5 GHz (3 clients), no kernel warning!
Really stable, I do not understand why in 7 months it has not been updated yet.
Thanks againg @luaraneda
I think the "do not understand why..." part has been answered in the PR that was sent to OpenWrt's github page:
Specifically in this post from Sven Eckelmann:
https://github.com/openwrt/openwrt/pull/1138#issuecomment-403192221
Warning: you must also merge the newest DFS host confirmation mis-feature support for this firmware:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=f40105e6747892e8edab94020567c158c9bec0df
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit?id=6f6eb1bcbeff48c875617b800f00f1c5d1b12290This mis-feature will break the wifi-tx whenever the QCA internal matcher has a false-positive. But without these changes, it will break the wifi-tx on each match.
These changes have to be applied to the mac80211 package and to the ath10k-ct package.
Thanks @chunkeey, now I understand.
I'm trying the 10.4-3.5.3-00057 and it seems stable
But I have only few clients.
I only have these alerts once a day but everything works perfectly.
[649571.634993] ath10k_ahb a000000.wifi: Invalid peer id 89 peer stats buffer
Credits go to Sven for write-up.
Was the same error present in previous firmware releases as well? Or was it working fine with the 3.6 firmware and this Is now just happening with the 3.5.3 firmware?
Because @Ansuel made a PR (see updates!) with the necessary changes to support 3.6:
So, it's 3.5.3 specific it would make sense to skip the FW.
It happens with both the firmware...
from what i can see... i notice this with 5ghz in 20mhz band....
anyway nobody reported this to ath10k mailing list?
I do not know...
@Ansuel
After 10 days on kernel log there are also two warnings
[895769.805975] ath10k_ahb a000000.wifi: received unexpected tx_fetch_ind event: in push mode
I had never seen before
Fritz!Box 4040 OpenWrt 18.06 snapshot r7106 ath10k firmware 10.4-3.5.3-00057
yeah, the "invalid VHT mcs" messages were a blessing in disguise... they drowned out all other messages 
.
From looking at the code, this could be either harmless or really nasty (ie. a slow descriptor leak - that could cause the WIFI to degrade over time and even shutdown one day when the driver has finally ran out of descriptors).
Since you can (re-)produce the bug, could you please email your findings to the ath10k-devel - ath10k@lists.infradead.org ML (plain-text email) ? Thank you!
Thea the real problem of this warning is that it's hard to reproduce...
@chunkeey @Ansuel
I do not know why but my 4040 can reproduce it too many times 
[96438.552358] ath10k_ahb a000000.wifi: Invalid peer id 14 peer stats buffer
[131439.527370] ath10k_ahb a000000.wifi: received unexpected tx_fetch_ind event: in push mode
[131439.527709] ath10k_ahb a000000.wifi: received unexpected tx_fetch_ind event: in push mode
[132036.188659] ath10k_ahb a000000.wifi: received unexpected tx_fetch_ind event: in push mode
[132036.188709] ath10k_ahb a000000.wifi: received unexpected tx_fetch_ind event: in push mode
[132036.195871] ath10k_ahb a000000.wifi: received unexpected tx_fetch_ind event: in push mode
[132036.204113] ath10k_ahb a000000.wifi: received unexpected tx_fetch_ind event: in push mode
[194619.298165] ath10k_ahb a000000.wifi: Invalid peer id 21 peer stats buffer
[214540.478860] ath10k_ahb a000000.wifi: received unexpected tx_fetch_ind event: in push mode
[302691.452861] ath10k_ahb a000000.wifi: Invalid peer id 38 peer stats buffer
[302750.503109] ath10k_ahb a000000.wifi: Invalid peer id 37 peer stats buffer
[395035.371422] ath10k_ahb a000000.wifi: Invalid peer id 45 peer stats buffer
[649571.634993] ath10k_ahb a000000.wifi: Invalid peer id 89 peer stats buffer
[837906.946895] ath10k_ahb a000000.wifi: Invalid peer id 115 peer stats buffer
[895769.805975] ath10k_ahb a000000.wifi: received unexpected tx_fetch_ind event: in push mode
[896666.298360] ath10k_ahb a000000.wifi: received unexpected tx_fetch_ind event: in push mode
How can I find other useful information?
Thank you
you should really post this to atk10k mailing list!
also wifi channel mhz band?
Sure, done!