In the next master is this going to be included?
3 Likes
Thanks sppmaster for spreading the good news! Finally some light at the end of the tunnel...
Yep! I’ll watch master closely and build when it is officially committed.
3 Likes
Is this the commit?
https://git.openwrt.org/?p=openwrt/openwrt.git;a=commit;h=958785508cc802de75698607670f9a236883d24d
quarky said the patch did not seem to work for him at all when back-ported to his 21.02.x build.
1 Like
For now it seems that Felix single-handedly handles all attempts to fix these wireless issues. He also included the original authors of VTBA scheduler in his commit emails but nobody made any comment. I hope better coordination between quarky and Felix would help Felix come up with a working solution. According to Felix, using the round-robin scheduler is pretty much the same as disabling or bypassing ATF.
1 Like
I can finally get back gigabit. Godspeed wifidude! 
1 Like
Our hero needs to change his username to AXwifidude 
5 Likes
Updated master build. Has that commit. Let me know how it works!
3 Likes
Hmmmmm while my wired performance is good now, my wireless performance dropped to an inexcusable 20mbps down/40mbps up. I tried both the at10k and the other version. Device is a Netgear Nighthawk X4S R7800.
I’m getting 570mbps+ speed testing an iPhone on 5ghz (same room). Having issues on 2.4ghz or 5ghz or both?
Look at the System and Kernel logs for any ath10k errors.
See my post here. I've had similar issue with previous master build.
Now I try the latest master but let's wait several days to see if the same issue will come up again.
@ACwifidude Do we really use QSDK 11.2r1 release in master.
The drivers are from the QSDK 11.2r1 release. The entire QSDK 11.2r1 release
can be found in the link below:
https://source.codeaurora.org/quic/qsdk/releases/manifest/qstak/tree/caf_AU_LINUX_QSDK_NHSS.QSDK.11.2.R1_TARGET_ALL.12.0.4540.030.xml?h=release
With greatest regret I report that since this commit the Wi-Fi 5GHz is completely unusable
Fri Jun 17 17:13:55 2022 kern.warn kernel: [35612.980044] ath10k_pci 0000:01:00.0: failed to lookup txq for peer_id 27 tid 0
Fri Jun 17 17:13:55 2022 kern.warn kernel: [35612.980080] ath10k_pci 0000:01:00.0: failed to lookup txq for peer_id 27 tid 0
Fri Jun 17 17:13:55 2022 kern.warn kernel: [35612.986241] ath10k_pci 0000:01:00.0: failed to lookup txq for peer_id 27 tid 0
Fri Jun 17 17:13:55 2022 kern.warn kernel: [35612.993376] ath10k_pci 0000:01:00.0: failed to lookup txq for peer_id 27 tid 0
Fri Jun 17 17:13:55 2022 kern.warn kernel: [35613.000634] ath10k_pci 0000:01:00.0: failed to lookup txq for peer_id 27 tid 0
Fri Jun 17 17:13:55 2022 kern.warn kernel: [35613.008484] ath10k_pci 0000:01:00.0: failed to lookup txq for peer_id 27 tid 0
Fri Jun 17 17:13:55 2022 kern.warn kernel: [35613.015003] ath10k_pci 0000:01:00.0: failed to lookup txq for peer_id 27 tid 0
Fri Jun 17 17:13:55 2022 kern.warn kernel: [35613.022271] ath10k_pci 0000:01:00.0: failed to lookup txq for peer_id 27 tid 0
Fri Jun 17 17:13:55 2022 kern.warn kernel: [35613.029470] ath10k_pci 0000:01:00.0: failed to lookup txq for peer_id 27 tid 0
Fri Jun 17 17:13:55 2022 kern.warn kernel: [35613.036655] ath10k_pci 0000:01:00.0: failed to lookup txq for peer_id 27 tid 0
Huge latency, very low throughput and frequent errors "no connection" for all 5GHz clients.
Same as reported here.
I've reverted to the master build from 20220519.
@ACwifidude There is a new patch. Can you put it in master?
1 Like
Can't reproduce the issue here so far.
1 Like
I've put the latest master on five R7800 - on three of them the above errors showed up after several hours or days. They all have more than 3 WLAN clients on 5GHz. But with master builds before the recent mac80211 patches I've never observed issues.
For the other two R7800s that have 1-2 and 3 Wi-Fi devices (only 1 or 2 are connected to 5GHz) the error still doesn't show up.
I changed some security options and someone I can get good speed now. Maybe it was the radio restart that changed something. Either way it works now.
1 Like
Not only 5GHz but also 2.4GHz, on ipq4018 (ea6350v3 device)... (commit and commit rework)
[62568.981836] ath10k_ahb a000000.wifi: Invalid peer id 70 or peer stats buffer, peer: 00000000 sta: 00000000
[68483.284323] ath10k_ahb a000000.wifi: fetch-ind: failed to lookup txq for peer_id 65 tid 4
[68483.284502] ath10k_ahb a000000.wifi: fetch-ind: failed to lookup txq for peer_id 65 tid 4
[68483.291611] ath10k_ahb a000000.wifi: fetch-ind: failed to lookup txq for peer_id 65 tid 4
[68483.299882] ath10k_ahb a000000.wifi: fetch-ind: failed to lookup txq for peer_id 65 tid 4
[68483.308637] ath10k_ahb a000000.wifi: fetch-ind: failed to lookup txq for peer_id 65 tid 4
[68483.316206] ath10k_ahb a000000.wifi: fetch-ind: failed to lookup txq for peer_id 65 tid 4
[68483.324332] ath10k_ahb a000000.wifi: fetch-ind: failed to lookup txq for peer_id 65 tid 4
[68483.332493] ath10k_ahb a000000.wifi: fetch-ind: failed to lookup txq for peer_id 65 tid 4
[68483.340570] ath10k_ahb a000000.wifi: fetch-ind: failed to lookup txq for peer_id 65 tid 4
[68483.348813] ath10k_ahb a000000.wifi: fetch-ind: failed to lookup txq for peer_id 65 tid 4
[68681.760868] device wlan0 left promiscuous mode
[68681.761027] br-lan: port 2(wlan0) entered disabled state
[68681.849405] net_ratelimit: 98 callbacks suppressed
[68681.849429] ath10k_ahb a000000.wifi: fetch-ind: failed to lookup txq for peer_id 407 tid 4
[68681.853156] ath10k_ahb a000000.wifi: fetch-ind: failed to lookup txq for peer_id 407 tid 4
[68681.861421] ath10k_ahb a000000.wifi: fetch-ind: failed to lookup txq for peer_id 407 tid 4
[68681.869662] ath10k_ahb a000000.wifi: fetch-ind: failed to lookup txq for peer_id 407 tid 4
[68681.877945] ath10k_ahb a000000.wifi: could not get mac80211 beacon, vdev_id: 0 addr: 60:38:e0:7c:5b:b1
[68681.886239] ath10k_ahb a000000.wifi: fetch-ind: failed to lookup txq for peer_id 175 tid 4
[68681.895456] ath10k_ahb a000000.wifi: fetch-ind: failed to lookup txq for peer_id 407 tid 4
[68681.903699] ath10k_ahb a000000.wifi: fetch-ind: failed to lookup txq for peer_id 175 tid 4
[68681.911933] ath10k_ahb a000000.wifi: fetch-ind: failed to lookup txq for peer_id 407 tid 4
[68681.920179] ath10k_ahb a000000.wifi: fetch-ind: failed to lookup txq for peer_id 175 tid 4
[68681.928432] ath10k_ahb a000000.wifi: fetch-ind: failed to lookup txq for peer_id 407 tid 4
[68682.082293] ath10k_ahb a000000.wifi: could not get mac80211 beacon, vdev_id: 0 addr: 60:38:e0:7c:5b:b1
[68682.140533] ath10k_ahb a000000.wifi: mac flush null vif, drop 0 queues 0xffff
[68682.141786] ath10k_ahb a000000.wifi: peer-unmap-event: unknown peer id 1
[68682.146710] ath10k_ahb a000000.wifi: peer-unmap-event: unknown peer id 1
[68684.425232] ath10k_ahb a000000.wifi: 10.4 wmi init: vdevs: 16 peers: 528 tid: 102
[68684.425311] ath10k_ahb a000000.wifi: msdu-desc: 2500 skid: 32
[68684.580004] ath10k_ahb a000000.wifi: rts threshold 2347
[68684.580340] ath10k_ahb a000000.wifi: Firmware lacks feature flag indicating a retry limit of > 2 is OK, requested limit: 4
[68684.585964] br-lan: port 2(wlan0) entered blocking state
[68684.595289] br-lan: port 2(wlan0) entered disabled state
[68684.601046] device wlan0 entered promiscuous mode
[68684.896024] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[68684.896299] br-lan: port 2(wlan0) entered blocking state
[68684.901514] br-lan: port 2(wlan0) entered forwarding state
[77080.383325] net_ratelimit: 529 callbacks suppressed
[77080.383493] ath10k_ahb a000000.wifi: fetch-ind: failed to lookup txq for peer_id 2 tid 0
[77080.387188] ath10k_ahb a000000.wifi: fetch-ind: failed to lookup txq for peer_id 2 tid 0
[77080.395510] ath10k_ahb a000000.wifi: fetch-ind: failed to lookup txq for peer_id 2 tid 0
[77080.403628] ath10k_ahb a000000.wifi: fetch-ind: failed to lookup txq for peer_id 2 tid 0
[77080.412080] ath10k_ahb a000000.wifi: fetch-ind: failed to lookup txq for peer_id 2 tid 0
[77080.419793] ath10k_ahb a000000.wifi: fetch-ind: failed to lookup txq for peer_id 2 tid 0
[77080.427774] ath10k_ahb a000000.wifi: fetch-ind: failed to lookup txq for peer_id 2 tid 0
[77080.435860] ath10k_ahb a000000.wifi: fetch-ind: failed to lookup txq for peer_id 2 tid 0
[77080.443936] ath10k_ahb a000000.wifi: fetch-ind: failed to lookup txq for peer_id 2 tid 0
[77080.451994] ath10k_ahb a000000.wifi: fetch-ind: failed to lookup txq for peer_id 2 tid 0
2 Likes
The nss .bin files are version 10. That is the most recent publicly released version. All the patches and supporting files have had multiple updates including many 11.2 files that are backwards compatible.
As far as I know 11.2 is the actual most recent version for ipq806x devices (I believe ipq807x has 11.4). Unfortunately it is not fully publicly available. I’d love for Qualcomm to allow us to use it and provide some open source friendly documentation.
3 Likes
@ACwifidude You will need to remove the encap offload patch because there's now a upstreamed version in master.
2 Likes
Saw that. Very nice!
2 Likes