I got an issue with my archer c7 where the 2.4GHz wifi band drops and it won't connect anymore, would like to share a see if anyone has had this issue.
the dmesg message shows this issues;
[ 2358.961065] ath10k_pci 0000:01:00.0: SWBA overrun on vdev 0, skipped old beacon
[ 2358.968538] ath10k_pci 0000:01:00.0: SWBA overrun on vdev 0, skipped old beacon
[ 2358.975992] ath10k_pci 0000:01:00.0: SWBA overrun on vdev 0, skipped old beacon
[ 2358.983438] ath10k_pci 0000:01:00.0: SWBA overrun on vdev 0, skipped old beacon
[ 2358.990885] ath10k_pci 0000:01:00.0: SWBA overrun on vdev 0, skipped old beacon
[ 2358.998327] ath10k_pci 0000:01:00.0: SWBA overrun on vdev 0, skipped old beacon
[ 2359.005771] ath10k_pci 0000:01:00.0: SWBA overrun on vdev 0, skipped old beacon
[ 2359.013215] ath10k_pci 0000:01:00.0: SWBA overrun on vdev 0, skipped old beacon
[ 2359.020658] ath10k_pci 0000:01:00.0: SWBA overrun on vdev 0, skipped old beacon
[ 2359.028096] ath10k_pci 0000:01:00.0: SWBA overrun on vdev 0, skipped old beacon
I have created an work around to get it fix temporarly until the driver it's updated because it looks like a driver issue to be fair and it shows up when the router is under a high load, I got a lot of devices dependent on the 2.4Ghz band.
A simple bash script will fix this;
##########################################################################
root@JUPITER:~# cat wififix.sh
if dmesg -e |grep -q "ath10k_pci 0000:01:00.0: SWBA overrun on vdev 0, skipped old beacon"; then
echo "issue"
/sbin/wifi
dmesg -C
else
exit
fi
root@JUPITER:~# crontab -l
0/5 /root/wififix.sh
##########################################################################
The best about this script it will not do anything unless it has the issue and this on it's own alleviated my issue.
I got an issue with my archer c7 where the 2.4GHz wifi band drops and it won't connect anymore, would like to share a see if anyone has had this issue.
the dmesg message shows this issues; [ 2358.961065] ath10k_pci 0000:01:00.0: SWBA overrun on vdev 0, skipped old beacon [ 2358.968538] ath10k_pci 0000:01:00.0: SWBA overrun on vdev 0, skipped old beacon [ 2358.975992] ath10k_pci 0000:01:00.0: SWBA overrun on vdev 0, skipped old beacon [ 2358.983438] ath10k_pci 0000:01:00.0: SWBA overrun on vdev 0, skipped old beacon [ 2358.990885] ath10k_pci 0000:01:00.0: SWBA overrun on vdev 0, skipped old beacon [ 2358.998327] ath10k_pci 0000:01:00.0: SWBA overrun on vdev 0, skipped old beacon [ 2359.005771] ath10k_pci 0000:01:00.0: SWBA overrun on vdev 0, skipped old beacon [ 2359.013215] ath10k_pci 0000:01:00.0: SWBA overrun on vdev 0, skipped old beacon [ 2359.020658] ath10k_pci 0000:01:00.0: SWBA overrun on vdev 0, skipped old beacon [ 2359.028096] ath10k_pci 0000:01:00.0: SWBA overrun on vdev 0, skipped old beacon
I have created an work around to get it fix temporarly until the driver it's updated because it looks like a driver issue to be fair and it shows up when the router is under a high load, I got a lot of devices dependent on the 2.4Ghz band.
A simple bash script will fix this; ########################################################################## root@JUPITER:~# cat wififix.sh if dmesg -e |grep -q "ath10k_pci 0000:01:00.0: SWBA overrun on vdev 0, skipped old beacon"; then echo "issue" /sbin/wifi dmesg -C else exit fi root@JUPITER:~# crontab -l 0/5 /root/wififix.sh ##########################################################################
The best about this script it will not do anything unless it has the issue and this on it's own alleviated my issue.