I've been having a problem with radio1 (2.4GHz wifi). Devices start connecting, but are unable to. I see the following in the log.
Fri May 23 00:34:23 2025 daemon.notice hostapd: wlan0: STA 00:00:00:00:00:00 IEEE 802.11: did not acknowledge authentication response
I've tried rebooting the router. The 5GHz band continues to work fine. The only thing which resolves the problem is resetting the firmware and restoring from backup. Its fine for a few hours and happens again requiring a firmware reset.
I'm using v4.6.11. I was intending to upgrade to 4.7 this weekend. I have a Slate ATX1800 router.
Looking into the logs I can see:
Thu May 22 22:56:58 2025 daemon.notice procd: /etc/rc.d/S15lvm2: File descriptor 12 (pipe:[6997]) leaked on lvm invocation. Parent PID 1884: /bin/sh
Thu May 22 22:56:58 2025 daemon.notice procd: /etc/rc.d/S15lvm2: Device open /dev/ram0 1:0 failed errno 22
Thu May 22 22:56:58 2025 daemon.notice procd: /etc/rc.d/S15lvm2: Device open /dev/ram0 1:0 failed errno 22
followed by many more messages.
I've turned off lvm as I don't use it. The pvs, vgs & lvs commands generate similar messages.
Further into the log I can see:
Thu May 22 22:56:59 2025 daemon.notice procd: /etc/rc.d/S16qca-ssdk:
Thu May 22 22:56:59 2025 daemon.notice procd: /etc/rc.d/S16qca-ssdk: starting
Thu May 22 22:56:59 2025 daemon.info gl-repeater[2032]: (gl-repeater.lua:348) lua-eco version: 3.6.0
Thu May 22 22:56:59 2025 daemon.info gl-repeater[2032]: (gl-repeater.lua: 16) load repeater config...
Thu May 22 22:56:59 2025 daemon.info gl-repeater[2032]: (gl-repeater.lua:115) wait wifi config ready...
Thu May 22 22:56:59 2025 daemon.info gl-repeater[2032]: (gl-repeater.lua: 95) radio0 wait wifi config ready...
Thu May 22 22:56:59 2025 daemon.info gl-repeater[2032]: (gl-repeater.lua: 95) radio1 wait wifi config ready...
Thu May 22 22:56:59 2025 daemon.info gl-repeater[2032]: (gl-repeater.lua:140) load wifi config...
Thu May 22 22:56:59 2025 daemon.notice procd: /etc/rc.d/S18dnscrypt-proxy: mkdir: can't create directory '/etc/dnscrypt-proxy2-vpn/': File exists
Thu May 22 22:56:59 2025 daemon.notice procd: /etc/rc.d/S18dnscrypt-proxy-vpn: mkdir: can't create directory '/etc/dnscrypt-proxy2-vpn/': File exists
Thu May 22 22:56:59 2025 daemon.notice procd: /etc/rc.d/S18vpnpolicy: uci: Entry not found
Thu May 22 22:57:00 2025 daemon.info gl-repeater[2032]: (repeater.lua:1011) no saved network
Thu May 22 22:57:00 2025 daemon.err procd: Could not find firmware /lib/firmware/ath11k/IPQ6018/hw1.0/qdss_trace_config.bin: No such file or directory
Thu May 22 22:57:00 2025 daemon.err procd: failed to write to /sys//devices/platform/soc/c000000.wifi/firmware/ath11k!IPQ6018!hw1.0!qdss_trace_config.bin/loading: Out of memory
Thu May 22 22:57:00 2025 kern.err kernel: [ 26.652373] firmware ath11k!IPQ6018!hw1.0!qdss_trace_config.bin: firmware_loading_store: map pages failed
Thu May 22 22:57:00 2025 kern.warn kernel: [ 26.652671] ath11k c000000.wifi: Direct firmware load for qdss_trace_config.bin failed with error -2
Thu May 22 22:57:00 2025 kern.warn kernel: [ 26.661303] ath11k c000000.wifi: Falling back to user helper
Thu May 22 22:57:00 2025 daemon.err procd: Could not find firmware /lib/firmware/qdss_trace_config.bin: No such file or directory
Thu May 22 22:57:00 2025 kern.err kernel: [ 26.717172] firmware qdss_trace_config.bin: firmware_loading_store: map pages failed
Thu May 22 22:57:00 2025 kern.warn kernel: [ 26.717297] ath11k c000000.wifi: qmi failed to load QDSS config: qdss_trace_config.bin
Thu May 22 22:57:00 2025 kern.warn kernel: [ 26.723994] ath11k c000000.wifi: Failed to download QDSS config to FW: -11
Thu May 22 22:57:00 2025 daemon.err procd: failed to write to /sys//devices/platform/soc/c000000.wifi/firmware/qdss_trace_config.bin/loading: Out of memory
Thu May 22 22:57:00 2025 daemon.info dnsmasq[2747]: Connected to system UBus
Thu May 22 22:57:00 2025 daemon.info dnsmasq[2747]: started, version 2.85 cachesize 1
Thu May 22 22:57:00 2025 daemon.info dnsmasq[2747]: compile time options: IPv6 GNU-getopt no-DBus UBus no-i18n no-IDN DHCP DHCPv6 no-Lua TFTP conntrack ipset auth cryptohash DNSSEC no-ID loop-detect inotify dumpfile
Thu May 22 22:57:00 2025 daemon.info dnsmasq[2747]: UBus support enabled: connected to system bus
Thu May 22 22:57:00 2025 daemon.info dnsmasq[2747]: using only locally-known addresses for domain test
Thu May 22 22:57:00 2025 daemon.info dnsmasq[2747]: using only locally-known addresses for domain onion
Thu May 22 22:57:00 2025 daemon.info dnsmasq[2747]: using only locally-known addresses for domain localhost
Thu May 22 22:57:00 2025 daemon.info dnsmasq[2747]: using only locally-known addresses for domain local
Thu May 22 22:57:00 2025 daemon.info dnsmasq[2747]: using only locally-known addresses for domain invalid
Thu May 22 22:57:00 2025 daemon.info dnsmasq[2747]: using only locally-known addresses for domain bind
Thu May 22 22:57:00 2025 daemon.info dnsmasq[2747]: using nameserver 127.0.0.1#5453
Thu May 22 22:57:00 2025 daemon.info dnsmasq[2747]: using only locally-known addresses for domain lan
Thu May 22 22:57:00 2025 daemon.info dnsmasq[2747]: read /etc/hosts - 4 addresses
Thu May 22 22:57:00 2025 daemon.info dnsmasq[2747]: read /tmp/hosts/dhcp.cfg01411c - 14 addresses
Thu May 22 22:57:00 2025 daemon.err dnscrypt-proxy[2140]: [2025-05-22 22:57:00] [NOTICE] dnscrypt-proxy 2.1.1
Thu May 22 22:57:00 2025 daemon.err dnscrypt-proxy[2158]: [2025-05-22 22:57:00] [NOTICE] dnscrypt-proxy 2.1.1
Thu May 22 22:57:01 2025 authpriv.info dropbear[2813]: Not backgrounding
Thu May 22 22:57:01 2025 daemon.err dnscrypt-proxy[2158]: [2025-05-22 22:57:01] [NOTICE] Network not available yet -- waiting...
I'm guessing the out of memory is the issue. I've recently started running Wireguard Client all the time. I wonder if this is part of the problem.
In the meantime I've started to keep an eye on memory usage. Memory usage (cached & used) was almost 100%, cached being ~50% which shouldn't be a problem. I flushed the cache memory and memory usage has stayed around 52% for a couple of hours. I've also set the fan to come on at a lower temperature. However I suspect neither of these things are going to fix the issue and its probably related to the VPN on reboot.
Have I struck a bug or am I asking too much of the router?