[IPQ4028] TCP sessions lock connected to some clients about ath10k-ct

[barhom]

after @greearb mentioned that I should try kmod-ath10k instead of kmod-ath10k-ct here are my results:

kmod-ath10k: issue does not present itself

root@OpenWrt:~# ethtool -i wlan0
driver: ath10k_ahb
version: 4.14.81
firmware-version: 10.4-3.6-00140
expansion-rom-version:
bus-info: a000000.wifi
supports-statistics: yes
supports-test: no
supports-eeprom-access: no
supports-register-dump: no
supports-priv-flags: no

kmod-ath10k-ct: issue easily reproduceable

[greearb]

Please try this new firmware. In the comment above, it shows that you were using upstream QCA firmware, not (just) upstream ath10k driver. This firmware attached is a rebase on newer QCA firmware, and if problems persist, then I can generate a series of binaries that can be used to bisect.

firmware-5-full-htt-mgt-community.bin.gz

[barhom]

Please try this new firmware. In the comment above, it shows that you were using upstream QCA firmware, not (just) upstream ath10k driver. This firmware attached is a rebase on newer QCA firmware, and if problems persist, then I can generate a series of binaries that can be used to bisect.

firmware-5-full-htt-mgt-community.bin.gz

Do you mean that I first compile openwrt with ath10k-ct again and then after booting the router replace some firmware file with the one you linked to?

[greearb]

You should not need to re-compile openwrt for this test. Just copy the firmware into place in /lib/firmware/ath10k/.... and reboot. You can check dmesg to make sure that the firmware version matches the hex bytes in the firmware image name (that is the git commit id).

[greearb]

Several bugs that might have caused this have been fixed, and no further comments in this bug for a while, so closing it. Please open new bugs if you find problems with latest firmware.