Some ath10k errors in GL1300

Installing and Using OpenWrt
1

I am running the latest 19.7.6 on GL1300 seems very stable but on the kernel log, I have:

[   10.952889] ath10k_ahb a000000.wifi: Direct firmware load for ath10k/fwcfg-ahb-a000000.wifi.txt failed with error -2
[   10.952933] ath10k_ahb a000000.wifi: Falling back to user helper
[   11.027332] firmware ath10k!fwcfg-ahb-a000000.wifi.txt: firmware_loading_store: map pages failed
[   11.034172] ath10k_ahb a000000.wifi: Direct firmware load for ath10k/QCA4019/hw1.0/ct-firmware-5.bin failed with error -2
[   11.035203] ath10k_ahb a000000.wifi: Falling back to user helper
[   11.092900] firmware ath10k!QCA4019!hw1.0!ct-firmware-5.bin: firmware_loading_store: map pages failed
[   11.093284] ath10k_ahb a000000.wifi: Direct firmware load for ath10k/QCA4019/hw1.0/ct-firmware-2.bin failed with error -2
[   11.101175] ath10k_ahb a000000.wifi: Falling back to user helper
[   11.175962] firmware ath10k!QCA4019!hw1.0!ct-firmware-2.bin: firmware_loading_store: map pages failed
[   11.176273] ath10k_ahb a000000.wifi: Direct firmware load for ath10k/QCA4019/hw1.0/firmware-6.bin failed with error -2
[   11.184279] ath10k_ahb a000000.wifi: Falling back to user helper
[   11.260107] firmware ath10k!QCA4019!hw1.0!firmware-6.bin: firmware_loading_store: map pages failed
[   11.866832] ath10k_ahb a000000.wifi: qca4019 hw1.0 target 0x01000000 chip_id 0x003b00ff sub 0000:0000
[   11.866879] ath10k_ahb a000000.wifi: kconfig debug 0 debugfs 1 tracing 0 dfs 1 testmode 0
[   11.878461] ath10k_ahb a000000.wifi: firmware ver 10.4b-ct-4019-fW-13-8c5b2baa2 api 5 features mfp,peer-flow-ctrl,txstatus-noack,wmi-10.x-CT,ratemask-CT,regdump-CT,txrate-CT,flush-all-CT,pingpong-CT,ch-regs-CT,nop-CT,set-special-CT,tx-rc-CT,cust-stats-CT,txrate2-CT,beacon-cb-CT,wmi-block-ack-CT,wmi-bcn-rc-CT crc32 1f3ed50f
[   11.966610] ath10k_ahb a000000.wifi: board_file api 2 bmi_id 0:16 crc32 e2dfaa91
[   13.277097] ath10k_ahb a000000.wifi: 10.4 wmi init: vdevs: 16  peers: 48  tid: 96
[   13.277149] ath10k_ahb a000000.wifi: msdu-desc: 2500  skid: 32
[   13.312995] ath10k_ahb a000000.wifi: wmi print 'P 48/48 V 16 K 144 PH 176 T 186  msdu-desc: 2500  sw-crypt: 0 ct-sta: 0'
[   13.313939] ath10k_ahb a000000.wifi: wmi print 'free: 53252 iram: 13576 sram: 35752'
[   13.417631] ath10k_ahb a000000.wifi: htt-ver 2.2 wmi-op 6 htt-op 4 cal pre-cal-file max-sta 32 raw 0 hwcrypto 1
[   13.525365] ath: EEPROM regdomain: 0x0
[   13.525378] ath: EEPROM indicates default country code should be used
[   13.525383] ath: doing EEPROM country->regdmn map search
[   13.525394] ath: country maps to regdmn code: 0x3a
[   13.525400] ath: Country alpha2 being used: US
[   13.525407] ath: Regpair used: 0x3a

and on the end those three lines:

ath10k_ahb a800000.wifi: Invalid legacy rate 26 peer stats
[   47.523554] ath10k_ahb a800000.wifi: Invalid VHT mcs 15 peer stats
[111743.380008] ath10k_ahb a800000.wifi: Invalid peer id 0 or peer stats buffer, peer: ceb37800  sta:   (null)

Should I be worried or change some settings? Some help much appreciated as I am not so advance in that networking wifi stuff.

Cheers

2

The first (firmware related) messages are normal and expected, those are alternative firmware (ABI-) versions which are attempted to be loaded one by one, before it finds- and successfully loads the correct one.

The peer related warnings record weird conditions thrown at ath10k-ct over the air, from your clients. They may provide debugging assistance in case you actually experiences problems, but in homeopathic doses (like once every one and a half days) it's basically non-existent.

1 Like
3

Wow that was quick respond. Thank you very much. All works very good so indeed it was maybe just one off interference.

Cheers