New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FS#2844 - ath10k on archer C7 v2: high latency #7630
Comments
zorxd: Doesn't seem to occur with the non-ct firmware and driver. |
por: Has been fixed in 19.07.1, so if you're still on 19.07.0 then please first upgrade to .1 and whether that fixes your problem. |
zorxd: I'm already on 19.07.1 and STILL have the issue, that's why I opened a new bug. It might not be related. |
blabla: I also see a quite unstable 5Ghz Wifi on a TP-Link Archer C6 v2, using 19.07.1. In my case, I see many packet loss (> 50%). Station is also very close to the AP (less than 2 meters, without any wall) |
zorxd: blabla, can you try with the ath10k kmod and firmware which doesn't end with -ct? I am using kmod-ath10k and ath10k-firmware-qca988x on my Archer C7 v2, and it seems to solve the issue. |
blabla: With ath10k-firmware-qca9888 and kmod-ath10k, my 5Ghz card is not working and even not recognized by the kernel. But after reinstalling -ct version, my 5Ghz card is still missing !
Am I missing something ?? Logs (with -ct version) Edit: after re-flashing with tplink_archer-c6-v2-squashfs-sysupgrade.bin official owrt image, my 5Ghz is working again... |
zorxd: Problem still occurs on 19.07.3. Makes my Google Chromecast unable to reliably stream music from Spotify. Switching to the non-CT module and firmware. |
zorxd: anybody noticed if this bug is still present on 21.02 series? |
zorxd:
On my Archer C7 v2, since the upgrade from 18.06 to 19.07, I sometimes get very high latency on my 5 GHz wifi network:
This is when pinging a wireless client from the router itself.
ping 192.168.12.167
PING 192.168.12.167 (192.168.12.167): 56 data bytes
64 bytes from 192.168.12.167: seq=0 ttl=64 time=1.334 ms
64 bytes from 192.168.12.167: seq=1 ttl=64 time=2.002 ms
64 bytes from 192.168.12.167: seq=2 ttl=64 time=1004.448 ms
64 bytes from 192.168.12.167: seq=3 ttl=64 time=4.342 ms
64 bytes from 192.168.12.167: seq=4 ttl=64 time=1.072 ms
64 bytes from 192.168.12.167: seq=5 ttl=64 time=2.074 ms
64 bytes from 192.168.12.167: seq=6 ttl=64 time=2.505 ms
64 bytes from 192.168.12.167: seq=7 ttl=64 time=1.059 ms
64 bytes from 192.168.12.167: seq=8 ttl=64 time=1.746 ms
64 bytes from 192.168.12.167: seq=9 ttl=64 time=1.176 ms
64 bytes from 192.168.12.167: seq=10 ttl=64 time=1.086 ms
64 bytes from 192.168.12.167: seq=11 ttl=64 time=1.072 ms
64 bytes from 192.168.12.167: seq=12 ttl=64 time=815.290 ms
64 bytes from 192.168.12.167: seq=13 ttl=64 time=1004.417 ms
64 bytes from 192.168.12.167: seq=14 ttl=64 time=4.294 ms
64 bytes from 192.168.12.167: seq=15 ttl=64 time=4.520 ms
64 bytes from 192.168.12.167: seq=16 ttl=64 time=1003.250 ms
64 bytes from 192.168.12.167: seq=17 ttl=64 time=3.125 ms
64 bytes from 192.168.12.167: seq=18 ttl=64 time=1.019 ms
64 bytes from 192.168.12.167: seq=19 ttl=64 time=2.066 ms
^C
--- 192.168.12.167 ping statistics ---
20 packets transmitted, 20 packets received, 0% packet loss
round-trip min/avg/max = 1.019/193.094/1004.448 ms
The upgrade to 19.07.1 didn't solve the issue. What (temporarily) seem to work is to restart the wlan0 interface. After a few hours the problem comes back. The client is very close to the AP (less than 3 meters, although there is a floor between). Signal quality is reported as very good.
Station 54:60:09:d3:e4:d6 (on wlan0)
inactive time: 540 ms
rx bytes: 1082546
rx packets: 6294
tx bytes: 15523400
tx packets: 11636
tx retries: 0
tx failed: 1
rx drop misc: 0
signal: -66 [-76, -68, -71] dBm
signal avg: -62 [-72, -64, -67] dBm
tx bitrate: 390.0 MBit/s VHT-MCS 8 80MHz short GI VHT-NSS 1
rx bitrate: 390.0 MBit/s VHT-MCS 8 80MHz short GI VHT-NSS 1
rx duration: 422088 us
last ack signal:-95 dBm
authorized: yes
authenticated: yes
associated: yes
preamble: long
WMM/WME: yes
MFP: no
TDLS peer: no
DTIM period: 2
beacon interval:100
short slot time:yes
connected time: 447 seconds
I am using stock 19.07.1 firmware. I also tried changing the regulatory domain from CA to US but it didn't help.
I will now try with the non-ct driver and firmware to see if it helps, as it worked fine on 18.06 which didn't include the -ct firmware by default.
cat /etc/config/wireless
config wifi-device 'radio0'
option type 'mac80211'
option hwmode '11a'
option path 'pci0000:00/0000:00:00.0'
option htmode 'VHT80'
option noscan '1'
option country 'US'
option channel '149'
config wifi-iface 'default_radio0'
option device 'radio0'
option key 'removed'
option network 'lan'
option mode 'ap'
option ssid 'myssid5'
option encryption 'psk2+ccmp'
config wifi-device 'radio1'
option type 'mac80211'
option channel '11'
option hwmode '11g'
option path 'platform/ahb/ahb:apb/18100000.wmac'
option noscan '1'
option country 'CA'
config wifi-iface 'default_radio1'
option device 'radio1'
option network 'lan'
option mode 'ap'
option ssid 'myssid'
option encryption 'psk2+ccmp'
option key 'removed'
option ieee80211w '1'
The text was updated successfully, but these errors were encountered: