What's new

RT-AX55 Running Out of Memory

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

maxnl

Occasional Visitor
Hi all, hoping someone might be able to provide some guidance to resolve a recurring issue.

I have 3x RT-AX55 routers, 2 are setup as AiMesh nodes. All were purchased in April 2022. For the first 6-8 months we had no issues, everything was completely stable and I never needed to manually reboot the router due to connectivity issues. However, over the last few months I've noticed that about weekly everything starts loading really slow and some devices start significantly lagging with loading pages/apps, to the point that some devices aren't even able to complete DNS lookups. A reboot of the main router completely clears up any connectivity issues for about a week.

When this happens, if I log into the router and look at the logs I see it's filled with similar to the following 3 lines:

Code:
Jan 15 11:19:30 dnsmasq[18686]: failed to allocate 66573 bytes
Jan 15 17:42:03 dnsmasq-dhcp[1784]: failed to write /var/lib/misc/dnsmasq.leases: No space left on device (retry in 7s)
Jan 15 17:42:04 out of memory [23676]

However the system status in the web UI shows I should still have free memory.

Screenshot 2023-01-15 at 5.27.02 PM.png

Which seems aligned with when I log into the router through SSH and run top
Code:
Mem: 202736K used, 47884K free, 3688K shrd, 864K buff, 10360K cached
CPU:  0.8% usr 15.3% sys  0.0% nic 82.2% idle  1.4% io  0.0% irq  0.0% sirq
Load average: 4.45 5.26 5.24 2/337 13257
  PID  PPID USER     STAT   VSZ %VSZ CPU %CPU COMMAND
1412     1 admin    S    11348  4.5   1  7.8 /sbin/wanduck
1801     1 admin    S    11288  4.4   0  1.8 httpds -s -i br0 -p 8443
7047     2 admin    SW       0  0.0   0  1.0 [kworker/0:29]
6950     2 admin    SW       0  0.0   1  0.4 [kworker/1:14]
6996     2 admin    SW       0  0.0   2  0.4 [kworker/2:35]
2719     1 admin    S     6320  2.5   2  0.4 /usr/sbin/stubby -g -C /etc/stubby/stubby.yml
1618     1 admin    S     6096  2.4   2  0.3 /usr/sbin/bsd
7581     2 admin    SW       0  0.0   2  0.3 [kworker/2:63]
12500 11859 admin    S    13264  5.2   1  0.3 networkmap
13240  8727 admin    R     3180  1.2   1  0.2 top
  682     2 admin    SW       0  0.0   1  0.2 [wl1-kthrd]
1451     1 admin    S    12300  4.8   0  0.2 nt_center
29909     1 admin    S     2484  0.9   2  0.2 miniupnpd -f /etc/upnp/config
   37     2 admin    SWN      0  0.0   0  0.2 [kswapd0]
7143     2 admin    SW       0  0.0   1  0.2 [kworker/1:47]
1918     1 admin    S    11708  4.6   1  0.1 mastiff
  674     2 admin    SW       0  0.0   0  0.1 [wl0-kthrd]
1423     1 admin    S    13064  5.1   1  0.1 nt_monitor
  262     2 admin    SW       0  0.0   2  0.1 [bcmsw_rx]
6952     2 admin    SW       0  0.0   1  0.1 [kworker/1:16]
8705  2442 admin    S     2432  0.9   0  0.1 dropbear -p 192.168.1.1:54321 -a
  259     2 admin    SW       0  0.0   3  0.1 [bcm_archer_us]
1360     1 admin    S    11348  4.5   2  0.0 /sbin/PS_pod
  252     2 admin    SW       0  0.0   0  0.0 [fc_timer]
7042     2 admin    SW       0  0.0   0  0.0 [kworker/0:24]
1827     1 admin    S    11348  4.5   2  0.0 sw_devled
11859     1 admin    S    11348  4.5   1  0.0 watchdog
1417     1 admin    S     2000  0.7   0  0.0 /usr/sbin/jitterentropy-rngd -p /var/run/jitterentropy-rngd.pid
  342     1 admin    S     1584  0.6   0  0.0 {wdtctl} wdtd
   34     2 admin    SW       0  0.0   2  0.0 [skb_free_task]
7148     2 admin    SW       0  0.0   1  0.0 [kworker/1:51]
6978     2 admin    SW       0  0.0   2  0.0 [kworker/2:16]
7542     2 admin    SW       0  0.0   2  0.0 [kworker/2:60]
7433     2 admin    SW       0  0.0   1  0.0 [kworker/1:63]
6933     2 admin    SW       0  0.0   1  0.0 [kworker/1:0]
7144     2 admin    SW       0  0.0   1  0.0 [kworker/1:48]
7308     2 admin    SW       0  0.0   1  0.0 [kworker/1:59]
7008     2 admin    SW       0  0.0   2  0.0 [kworker/2:47]
6937     2 admin    SW       0  0.0   1  0.0 [kworker/1:4]
8516     2 admin    SW       0  0.0   0  0.0 [kworker/0:8]
7050     2 admin    SW       0  0.0   0  0.0 [kworker/0:32]
6953     2 admin    SW       0  0.0   1  0.0 [kworker/1:17]
5617     2 admin    SW       0  0.0   2  0.0 [kworker/2:3]
6958     2 admin    SW       0  0.0   1  0.0 [kworker/1:24]
7133     2 admin    SW       0  0.0   1  0.0 [kworker/1:37]
6507     2 admin    SW       0  0.0   2  0.0 [kworker/2:0]
7049     2 admin    SW       0  0.0   0  0.0 [kworker/0:31]
7033     2 admin    SW       0  0.0   0  0.0 [kworker/0:15]
7320     2 admin    SW       0  0.0   0  0.0 [kworker/0:59]
7314     2 admin    SW       0  0.0   2  0.0 [kworker/2:59]
12087     2 admin    SW       0  0.0   2  0.0 [kworker/2:30]
1960     1 admin    S    61572 24.4   0  0.0 conn_diag
1939     1 admin    S    20612  8.1   0  0.0 roamast
2416     1 admin    S    18688  7.4   0  0.0 amas_lib
1589     1 admin    S    16824  6.6   0  0.0 wps_pbcd
21148     1 admin    S    14640  5.8   0  0.0 cfg_server
1817     1 admin    S    14200  5.6   0  0.0 ahs
    1     0 admin    S    13408  5.3   2  0.0 /sbin/init
1425     1 admin    S    13396  5.3   2  0.0 /sbin/netool
1829     1 admin    S    11348  4.5   0  0.0 amas_lanctrl
1928     1 admin    S    11348  4.5   2  0.0 pctime
1820     1 admin    S    11348  4.5   2  0.0 check_watchdog
2697     1 admin    S    11348  4.5   0  0.0 ntp
1581     1 admin    S    11348  4.5   1  0.0 wpsaide

Not sure if it's relevant, but if i check disk space using df -h it does show the root directly has no space.
Code:
Filesystem                Size      Used Available Use% Mounted on
/dev/root                28.6M     28.6M         0 100% /
devtmpfs                122.3M         0    122.3M   0% /dev
tmpfs                   122.4M    288.0K    122.1M   0% /var
tmpfs                   122.4M      3.0M    119.4M   2% /tmp/mnt
ubi1:data                 1.0M     68.0K    876.0K   7% /data
tmpfs                   122.4M      3.0M    119.4M   2% /tmp/mnt
tmpfs                   122.4M      3.0M    119.4M   2% /tmp
/dev/mtdblock9           15.0M      2.6M     12.4M  17% /jffs

I have AiProtection, Guest Wifi, Parental Controls, and QOS disabled (never been enabled). Firewall is enabled but DoS protection is disabled and there's no URL/Keyword/Network Service filters enabled and I haven't added any inbound firewall rules. Logged Packets type is set to none. This model doesn't have USB ports or a file server option I can disable, as far as I can tell. I'm using stock firmware, current version 3.0.0.4.386_50460-g5174ed0.

I've tried factory resetting on all units, manually reinstalling the firmware after downloading direct from Asus, and manually reconfiguring everything in hope that would make a difference, but it did not.

From this point, I'm not sure where to look or what my next step would be. Any help is greatly appreciated!
 
Last edited:
Hi,
I have the same problem as you on my gtaxe11000 in 388.1 the logs display the same message: out of memory.

I was 840 used and 180 free. I restarted my router. But every day, I see that the ram is increasing.
I was at +/- 19 days without restarting.
 
Mine seems to be around the 6-7 day mark.

Today I happened to catch some more errors, that appear to indicate a firmware issue if I had to guess.
This is just an excerpt:

Code:
Jan 28 11:51:05 kernel: Division by zero in kernel.
Jan 28 11:51:05 kernel: CPU: 1 PID: 677 Comm: wl1-kthrd Tainted: P                4.1.52 #2
Jan 28 11:51:05 kernel: Hardware name: Generic DT based system
Jan 28 11:51:05 kernel: [<c0026030>] (unwind_backtrace) from [<c0022128>] (show_stack+0x10/0x14)
Jan 28 11:51:05 kernel: [<c0022128>] (show_stack) from [<c045e98c>] (dump_stack+0x7c/0x9c)
Jan 28 11:51:05 kernel: [<c045e98c>] (dump_stack) from [<c01dfae4>] (Ldiv0+0x8/0x10)
Jan 28 11:51:05 kernel: [<c01dfae4>] (Ldiv0) from [<bf445e7c>] (wlc_ampdu_taf_release+0x1bc/0x19f0 [wl])
Jan 28 11:51:05 kernel: [<bf445e7c>] (wlc_ampdu_taf_release [wl]) from [<bf51b140>] (taf_ias_sched_scb+0x1680/0x1840 [wl])
Jan 28 11:51:05 kernel: [<bf51b140>] (taf_ias_sched_scb [wl]) from [<bf51be60>] (taf_ias_schedule+0x90c/0x1028 [wl])
Jan 28 11:51:05 kernel: [<bf51be60>] (taf_ias_schedule [wl]) from [<bf5174f0>] (wlc_taf_schedule+0x17c/0x254 [wl])
Jan 28 11:51:05 kernel: [<bf5174f0>] (wlc_taf_schedule [wl]) from [<bf43dda4>] (wlc_ampdu_txeval+0x8c/0x157c [wl])
Jan 28 11:51:05 kernel: [<bf43dda4>] (wlc_ampdu_txeval [wl]) from [<bf2cb928>] (wl_pktfwd_pktlist_xmit+0x1b4/0x2cc [wl])
Jan 28 11:51:05 kernel: [<bf2cb928>] (wl_pktfwd_pktlist_xmit [wl]) from [<bf2cbbe8>] (wl_pktfwd_dnstream+0x1a8/0x31c [wl])
Jan 28 11:51:05 kernel: [<bf2cbbe8>] (wl_pktfwd_dnstream [wl]) from [<bf2cbfb0>] (wl_worker_thread_func+0x128/0x160 [wl])
Jan 28 11:51:05 kernel: [<bf2cbfb0>] (wl_worker_thread_func [wl]) from [<c0043a70>] (kthread+0xd8/0xec)
Jan 28 11:51:05 kernel: [<c0043a70>] (kthread) from [<c001eca8>] (ret_from_fork+0x14/0x2c)
Jan 28 11:51:06 kernel: Division by zero in kernel.
Jan 28 11:51:06 kernel: CPU: 1 PID: 677 Comm: wl1-kthrd Tainted: P                4.1.52 #2
Jan 28 11:51:06 kernel: Hardware name: Generic DT based system
Jan 28 11:51:06 kernel: [<c0026030>] (unwind_backtrace) from [<c0022128>] (show_stack+0x10/0x14)
Jan 28 11:51:06 kernel: [<c0022128>] (show_stack) from [<c045e98c>] (dump_stack+0x7c/0x9c)
Jan 28 11:51:06 kernel: [<c045e98c>] (dump_stack) from [<c01dfae4>] (Ldiv0+0x8/0x10)
Jan 28 11:51:06 kernel: [<c01dfae4>] (Ldiv0) from [<bf445e7c>] (wlc_ampdu_taf_release+0x1bc/0x19f0 [wl])
Jan 28 11:51:06 kernel: [<bf445e7c>] (wlc_ampdu_taf_release [wl]) from [<bf51b140>] (taf_ias_sched_scb+0x1680/0x1840 [wl])
Jan 28 11:51:06 kernel: [<bf51b140>] (taf_ias_sched_scb [wl]) from [<bf51be60>] (taf_ias_schedule+0x90c/0x1028 [wl])
Jan 28 11:51:06 kernel: [<bf51be60>] (taf_ias_schedule [wl]) from [<bf5174f0>] (wlc_taf_schedule+0x17c/0x254 [wl])
Jan 28 11:51:06 kernel: [<bf5174f0>] (wlc_taf_schedule [wl]) from [<bf43dda4>] (wlc_ampdu_txeval+0x8c/0x157c [wl])
Jan 28 11:51:06 kernel: [<bf43dda4>] (wlc_ampdu_txeval [wl]) from [<bf2cb928>] (wl_pktfwd_pktlist_xmit+0x1b4/0x2cc [wl])
Jan 28 11:51:06 kernel: [<bf2cb928>] (wl_pktfwd_pktlist_xmit [wl]) from [<bf2cbbe8>] (wl_pktfwd_dnstream+0x1a8/0x31c [wl])
Jan 28 11:51:06 kernel: [<bf2cbbe8>] (wl_pktfwd_dnstream [wl]) from [<bf2cbfb0>] (wl_worker_thread_func+0x128/0x160 [wl])
Jan 28 11:51:06 kernel: [<bf2cbfb0>] (wl_worker_thread_func [wl]) from [<c0043a70>] (kthread+0xd8/0xec)
Jan 28 11:51:06 kernel: [<c0043a70>] (kthread) from [<c001eca8>] (ret_from_fork+0x14/0x2c)
Jan 28 11:51:06 kernel: Division by zero in kernel.
Jan 28 11:51:06 kernel: CPU: 1 PID: 677 Comm: wl1-kthrd Tainted: P                4.1.52 #2
Jan 28 11:51:06 kernel: Hardware name: Generic DT based system
Jan 28 11:51:06 kernel: [<c0026030>] (unwind_backtrace) from [<c0022128>] (show_stack+0x10/0x14)
Jan 28 11:51:06 kernel: [<c0022128>] (show_stack) from [<c045e98c>] (dump_stack+0x7c/0x9c)
Jan 28 11:51:06 kernel: [<c045e98c>] (dump_stack) from [<c01dfae4>] (Ldiv0+0x8/0x10)
Jan 28 11:51:06 kernel: [<c01dfae4>] (Ldiv0) from [<bf445e7c>] (wlc_ampdu_taf_release+0x1bc/0x19f0 [wl])
Jan 28 11:51:06 kernel: [<bf445e7c>] (wlc_ampdu_taf_release [wl]) from [<bf51b140>] (taf_ias_sched_scb+0x1680/0x1840 [wl])
Jan 28 11:51:06 kernel: [<bf51b140>] (taf_ias_sched_scb [wl]) from [<bf51be60>] (taf_ias_schedule+0x90c/0x1028 [wl])
Jan 28 11:51:06 kernel: [<bf51be60>] (taf_ias_schedule [wl]) from [<bf5174f0>] (wlc_taf_schedule+0x17c/0x254 [wl])
Jan 28 11:51:06 kernel: [<bf5174f0>] (wlc_taf_schedule [wl]) from [<bf43dda4>] (wlc_ampdu_txeval+0x8c/0x157c [wl])
Jan 28 11:51:06 kernel: [<bf43dda4>] (wlc_ampdu_txeval [wl]) from [<bf441e98>] (wlc_ampdu_dotxstatus_aqm_complete+0xfe4/0x1c68 [wl])
Jan 28 11:51:06 kernel: [<bf441e98>] (wlc_ampdu_dotxstatus_aqm_complete [wl]) from [<bf442e30>] (wlc_ampdu_dotxstatus+0x88/0x1834 [wl])
Jan 28 11:51:06 kernel: [<bf442e30>] (wlc_ampdu_dotxstatus [wl]) from [<bf53fbc4>] (wlc_dotxstatus+0xb10/0x1fa4 [wl])
Jan 28 11:51:06 kernel: [<bf53fbc4>] (wlc_dotxstatus [wl]) from [<bf46e6e0>] (wlc_bmac_txstatus+0x2f8/0x378 [wl])
Jan 28 11:51:06 kernel: [<bf46e6e0>] (wlc_bmac_txstatus [wl]) from [<bf4b68e4>] (wlc_worklet+0x218/0x4e8 [wl])
Jan 28 11:51:06 kernel: [<bf4b68e4>] (wlc_worklet [wl]) from [<bf41462c>] (wl_dpc_rxwork+0x80/0x16c [wl])
Jan 28 11:51:06 kernel: [<bf41462c>] (wl_dpc_rxwork [wl]) from [<bf2cbf80>] (wl_worker_thread_func+0xf8/0x160 [wl])
Jan 28 11:51:06 kernel: [<bf2cbf80>] (wl_worker_thread_func [wl]) from [<c0043a70>] (kthread+0xd8/0xec)
Jan 28 11:51:06 kernel: [<c0043a70>] (kthread) from [<c001eca8>] (ret_from_fork+0x14/0x2c)
Jan 28 11:51:06 kernel: Division by zero in kernel.
Jan 28 11:51:06 kernel: CPU: 1 PID: 677 Comm: wl1-kthrd Tainted: P                4.1.52 #2
Jan 28 11:51:06 kernel: Hardware name: Generic DT based system
Jan 28 11:51:06 kernel: [<c0026030>] (unwind_backtrace) from [<c0022128>] (show_stack+0x10/0x14)
Jan 28 11:51:06 kernel: [<c0022128>] (show_stack) from [<c045e98c>] (dump_stack+0x7c/0x9c)
Jan 28 11:51:06 kernel: [<c045e98c>] (dump_stack) from [<c01dfae4>] (Ldiv0+0x8/0x10)
Jan 28 11:51:06 kernel: [<c01dfae4>] (Ldiv0) from [<bf445e7c>] (wlc_ampdu_taf_release+0x1bc/0x19f0 [wl])
Jan 28 11:51:06 kernel: [<bf445e7c>] (wlc_ampdu_taf_release [wl]) from [<bf51b140>] (taf_ias_sched_scb+0x1680/0x1840 [wl])
Jan 28 11:51:06 kernel: [<bf51b140>] (taf_ias_sched_scb [wl]) from [<bf51be60>] (taf_ias_schedule+0x90c/0x1028 [wl])
Jan 28 11:51:06 kernel: [<bf51be60>] (taf_ias_schedule [wl]) from [<bf5174f0>] (wlc_taf_schedule+0x17c/0x254 [wl])
Jan 28 11:51:06 kernel: [<bf5174f0>] (wlc_taf_schedule [wl]) from [<bf43dda4>] (wlc_ampdu_txeval+0x8c/0x157c [wl])
Jan 28 11:51:06 kernel: [<bf43dda4>] (wlc_ampdu_txeval [wl]) from [<bf441e98>] (wlc_ampdu_dotxstatus_aqm_complete+0xfe4/0x1c68 [wl])
Jan 28 11:51:06 kernel: [<bf441e98>] (wlc_ampdu_dotxstatus_aqm_complete [wl]) from [<bf442e30>] (wlc_ampdu_dotxstatus+0x88/0x1834 [wl])
Jan 28 11:51:06 kernel: [<bf442e30>] (wlc_ampdu_dotxstatus [wl]) from [<bf53fbc4>] (wlc_dotxstatus+0xb10/0x1fa4 [wl])
Jan 28 11:51:06 kernel: [<bf53fbc4>] (wlc_dotxstatus [wl]) from [<bf46e6e0>] (wlc_bmac_txstatus+0x2f8/0x378 [wl])
Jan 28 11:51:06 kernel: [<bf46e6e0>] (wlc_bmac_txstatus [wl]) from [<bf4b68e4>] (wlc_worklet+0x218/0x4e8 [wl])
Jan 28 11:51:06 kernel: [<bf4b68e4>] (wlc_worklet [wl]) from [<bf41462c>] (wl_dpc_rxwork+0x80/0x16c [wl])
Jan 28 11:51:06 kernel: [<bf41462c>] (wl_dpc_rxwork [wl]) from [<bf2cbf80>] (wl_worker_thread_func+0xf8/0x160 [wl])
Jan 28 11:51:06 kernel: [<bf2cbf80>] (wl_worker_thread_func [wl]) from [<c0043a70>] (kthread+0xd8/0xec)
Jan 28 11:51:06 kernel: [<c0043a70>] (kthread) from [<c001eca8>] (ret_from_fork+0x14/0x2c)
Jan 28 11:51:06 kernel: Division by zero in kernel.
Jan 28 11:51:06 kernel: CPU: 1 PID: 677 Comm: wl1-kthrd Tainted: P                4.1.52 #2
Jan 28 11:51:06 kernel: Hardware name: Generic DT based system
Jan 28 11:51:06 kernel: [<c0026030>] (unwind_backtrace) from [<c0022128>] (show_stack+0x10/0x14)
Jan 28 11:51:06 kernel: [<c0022128>] (show_stack) from [<c045e98c>] (dump_stack+0x7c/0x9c)
Jan 28 11:51:06 kernel: [<c045e98c>] (dump_stack) from [<c01dfae4>] (Ldiv0+0x8/0x10)
Jan 28 11:51:06 kernel: [<c01dfae4>] (Ldiv0) from [<bf445e7c>] (wlc_ampdu_taf_release+0x1bc/0x19f0 [wl])
Jan 28 11:51:06 kernel: [<bf445e7c>] (wlc_ampdu_taf_release [wl]) from [<bf51b140>] (taf_ias_sched_scb+0x1680/0x1840 [wl])
Jan 28 11:51:06 kernel: [<bf51b140>] (taf_ias_sched_scb [wl]) from [<bf51be60>] (taf_ias_schedule+0x90c/0x1028 [wl])
Jan 28 11:51:06 kernel: [<bf51be60>] (taf_ias_schedule [wl]) from [<bf5174f0>] (wlc_taf_schedule+0x17c/0x254 [wl])
Jan 28 11:51:06 kernel: [<bf5174f0>] (wlc_taf_schedule [wl]) from [<bf43dda4>] (wlc_ampdu_txeval+0x8c/0x157c [wl])
Jan 28 11:51:06 kernel: [<bf43dda4>] (wlc_ampdu_txeval [wl]) from [<bf442e7c>] (wlc_ampdu_dotxstatus+0xd4/0x1834 [wl])
Jan 28 11:51:06 kernel: [<bf442e7c>] (wlc_ampdu_dotxstatus [wl]) from [<bf53fbc4>] (wlc_dotxstatus+0xb10/0x1fa4 [wl])
Jan 28 11:51:06 kernel: [<bf53fbc4>] (wlc_dotxstatus [wl]) from [<bf46e6e0>] (wlc_bmac_txstatus+0x2f8/0x378 [wl])
Jan 28 11:51:06 kernel: [<bf46e6e0>] (wlc_bmac_txstatus [wl]) from [<bf4b68e4>] (wlc_worklet+0x218/0x4e8 [wl])
Jan 28 11:51:06 kernel: [<bf4b68e4>] (wlc_worklet [wl]) from [<bf41462c>] (wl_dpc_rxwork+0x80/0x16c [wl])
Jan 28 11:51:06 kernel: [<bf41462c>] (wl_dpc_rxwork [wl]) from [<bf2cbf80>] (wl_worker_thread_func+0xf8/0x160 [wl])
Jan 28 11:51:06 kernel: [<bf2cbf80>] (wl_worker_thread_func [wl]) from [<c0043a70>] (kthread+0xd8/0xec)
Jan 28 11:51:06 kernel: [<c0043a70>] (kthread) from [<c001eca8>] (ret_from_fork+0x14/0x2c)
 
Had it happen again to me again yesterday, but uptime was less than 4 days. Now I'm starting to wonder if there's something happening on Sundays specifically
 
I also have this problem since upgraded to 386_50460, I wonder when there will be next firmware update. This is really frustrated.
 
Joining in here. I have this issue too on an RT-AX55.
I have more features activated then OP, but the result is the same.

Anyone happen to get it fixed?
 
Probably all you can do is to report the issue to Asus using the router's UI and then hope that they will fix it in the next firmware version.
 
Last edited:
I suppose you are right. Guess I'll do it, for the sake of doing it at least, but then also be looking for something else.
Internet in the home is just too much of required utility these days for it to be unstable
 
I have enabled the scheduled reboot feature on the router and scheduled a reboot for Monday and Thursday at a time in the middle of the night.

Since doing this, I haven’t needed to manually reboot at any point. All my devices seem to reconnect seamlessly, including a doorbell camera, wifi bulbs and switches, various hub devices, smart speakers, etc.. The only issue I have is that my Harmony remote’s smart light buttons don’t work after the wifi connection is lost until you open the harmony app on your phone. So I’ve basically just given up on using those buttons, which is fine for now, I rarely used them before.

I tried only rebooting once a week but would occasionally start to have issues just near the end of the week. Twice a week has been solid.

I haven’t gone through the effort of reporting to ASUS. I probably should but it seems like a lot of effort for little chance of reward
 
So far I'm at 6 days and 13 hours of uptime, everything seems to be working perfectly, and the system is showing less memory usage in the UI as well
1684186019927.png
 

Latest threads

Support SNBForums w/ Amazon

If you'd like to support SNBForums, just use this link and buy anything on Amazon. Thanks!

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top