I'm running an Archer C7 V2 as a wireless AP (WDS link to my main router not a cable) and I was able to run iperf3 for over 5 hours no problem (2.4 and 5 ghz radios running at the same time). I installed ath10k-ct-full-htt firmware and wpad-wolfssl for 802.11r/k/v support. No idea if these drivers would help you or not but it would be an easy test for you to run.
@Catfriend1 I saw in this topic that you try to reach devel list for talking about this issue. Did you find any reply about it ?
Maybe we can open a bug for this ath10k wifi problems ? Looks like ct firmware is a open-source version, so will be better try to find a solution for this firmware problems instead of replacing it with a closed version ?
@csantz I some time later did unsubscribe because of all those mails about other things after I reported the problem. So maybe there was a reply and I didn't get it - else no. I feel better staying on the forum and swinging by to check new posts from day to day.
If I would know more about wifi drivers etc. I'd make a bug report.
There seem to be notable differences between the 3 firmware options:
ath10k-firmware-qca988x: closed source firmware, seems to be stable and supports Mesh networks. does not seem to be maintained all that well.
ath10k-firmware-qca988x-ct: more actively maintained. enables additional features like IBSS. Seems to be unstable.
ath10k-firmware-qca988x-ct-full-htt: Improved stability for busy networks, fixes .11r authentication and enables 802.11k/v.
There is also a section at the bottom of this page talking about know bugs. Sounds like there is a way to trigger the firmware to crash but also a way to enable more verbose messaging.
CT firmware has a WMI message watchdog feature that can be enabled when using the CT patched drivers/kernels. The driver will send no-operation (NOP) message every second to the firmware. After the firmware receives one of these messages, if it ever does NOT receive the message for 5 seconds in a row after that, it will assert and crash. This allows the host to take recovery actions instead of just having the system effectively hang forever.