What's new
  • 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!

Asus RT-AX88U Pro stopped working occasionally

David Cavalli

Regular Contributor
Saw a similar thread with an RT-AX86U with Merlin, but that seemed to resolve to a USB issue. My RT-AX88U Pro is a few months old, but has been relatively stable along the way. For the past few weeks, I've had stability issues. At first, I thought it was related to my cable modem. I replaced it, when ChatGPT said my CM1100 values were heat related, so bought an Arris S33 to resolve the problem. It didn't. My internet unreliability issues look much more likely to be my 88U Pro now. I just had another outage now at 4:24 PM. No ping, ssh, http or any other access to the router. The Wifi light on the router seemed to be off. No deviced wired or wifi had connection to the router. Local connections (i.e. NAS) access was gone. *NOT* an internet issue (i.e. Arris, Cox, w/e). Looking at the log, there seem to be "Invalid device mode -1" lines which looks like something internally is failing.

I saw the other user copy/paste the system log to request help. I'm posting my own fresh down / reboot syslog here to ask for any feedback and/or help. All URL and addresses for VNC were globally replaced for privacy, but can be sent directly if that is somehow necessary. (i.e. Update forced for alias myvncaddy.vnchome.com, new IP# 99.99.99.99 not the right info, but find/replaced.)

Services used was asked. Here's a list of the customizations I can think of from memory:
  • profile.add - personal profile cfg
  • hosts.add - personal hosts file cfg
  • dnsmasq.conf.add - personal mapping MAC to local IP
  • smb.postconf - fix SMB directory permissions
  • amtm - latest installed but no services currently used
  • usericon - custom .log icons for <MAC> devices, same for last few Asus routers
  • DDNS service - configured my VNC address
  • have an authorized key for SSH access
Thanks in advance!
 

Attachments

What did you end up doing? Based on the router sh!tting the bed at 16:20, I'd start out by setting fixed wireless channels instead of auto. Might be the symptom rather than the cause, but worth a try.
Code:
Sep 16 16:19:51 acsd: acs_update_status(1333): acs get chanspec failed ret code: -22
Sep 16 16:20:45 kernel: rcu: INFO: rcu_preempt detected stalls on CPUs/tasks:
Sep 16 16:20:45 kernel: rcu:     Tasks blocked on level-0 rcu_node (CPUs 0-3): P4195
Sep 16 16:20:45 kernel: rcu:     (detected by 1, t=60012 jiffies, g=29854301, q=134114)
Sep 16 16:20:45 kernel: Call trace:
Sep 16 16:20:45 kernel:  __switch_to+0xe0/0x160
Sep 16 16:20:45 kernel:  0x284
Sep 16 16:20:45 kernel: Call trace:
Sep 16 16:20:45 kernel:  __switch_to+0xe0/0x160
Sep 16 16:20:45 kernel:  0x284
Sep 16 16:21:37 acsd: acsd_chanim_query(878): failed to get chanim resultsret code: -22
Sep 16 16:23:23 acsd: acsd_chanim_query(878): failed to get chanim resultsret code: -22
Sep 16 16:23:29 kernel: Print axmacphyIfTbl
Sep 16 16:23:29 kernel: Print vasipregister
Sep 16 16:23:29 kernel: Print vasippchistory
Sep 16 16:23:29 kernel: Print smctable
Sep 16 16:23:29 kernel: Print smctinytable
Sep 16 16:23:29 kernel: Print BFM table
Sep 16 16:23:29 kernel: Print bfdIndexLUT
Sep 16 16:23:33 kernel: GET STA INFO failed, -21
Sep 16 16:23:45 kernel: rcu: INFO: rcu_preempt detected stalls on CPUs/tasks:
Sep 16 16:23:45 kernel: rcu:     Tasks blocked on level-0 rcu_node (CPUs 0-3): P4195
Sep 16 16:23:45 kernel: rcu:     (detected by 2, t=240017 jiffies, g=29854301, q=538047)
Sep 16 16:23:45 kernel: Call trace:
Sep 16 16:23:45 kernel:  __switch_to+0xe0/0x160
Sep 16 16:23:45 kernel:  __schedule+0x1ac/0x430
Sep 16 16:23:45 kernel:  preempt_schedule_common+0x24/0x50
Sep 16 16:23:45 kernel:  preempt_schedule+0x24/0x30
Sep 16 16:23:45 kernel:  __local_bh_enable_ip+0x98/0xa0
Sep 16 16:23:45 kernel:  _raw_spin_unlock_bh+0x1c/0x30
Sep 16 16:23:45 kernel:  blog_unlock+0x18/0x20
Sep 16 16:23:45 kernel:  bcm_nf_blog_ct_is_expired+0x38/0xb0
Sep 16 16:23:45 kernel:  nf_ct_gc_expired+0x80/0xd0
Sep 16 16:23:45 kernel:  gc_worker+0x1c4/0x340
Sep 16 16:23:45 kernel:  process_one_work+0x198/0x2e0
Sep 16 16:23:45 kernel:  worker_thread+0x48/0x400
Sep 16 16:23:45 kernel:  kthread+0x118/0x150
Sep 16 16:23:45 kernel:  ret_from_fork+0x10/0x24
Sep 16 16:23:45 kernel: Call trace:
Sep 16 16:23:45 kernel:  __switch_to+0xe0/0x160
Sep 16 16:23:45 kernel:  __schedule+0x1ac/0x430
Sep 16 16:23:45 kernel:  preempt_schedule_common+0x24/0x50
Sep 16 16:23:45 kernel:  preempt_schedule+0x24/0x30
Sep 16 16:23:45 kernel:  __local_bh_enable_ip+0x98/0xa0
Sep 16 16:23:45 kernel:  _raw_spin_unlock_bh+0x1c/0x30
Sep 16 16:23:45 kernel:  blog_unlock+0x18/0x20
Sep 16 16:23:45 kernel:  bcm_nf_blog_ct_is_expired+0x38/0xb0
Sep 16 16:23:45 kernel:  nf_ct_gc_expired+0x80/0xd0
Sep 16 16:23:45 kernel:  gc_worker+0x1c4/0x340
Sep 16 16:23:45 kernel:  process_one_work+0x198/0x2e0
Sep 16 16:23:45 kernel:  worker_thread+0x48/0x400
Sep 16 16:23:45 kernel:  kthread+0x118/0x150
Sep 16 16:23:45 kernel:  ret_from_fork+0x10/0x24
Sep 16 16:23:49 kernel: GET STA INFO failed, -19
Sep 16 16:23:56 kernel: GET STA INFO failed, -19
Sep 16 16:23:56 kernel: GET STA INFO failed, -19
Sep 16 16:23:57 kernel: GET STA INFO failed, -19
Sep 16 16:23:57 kernel: GET STA INFO failed, -19
Sep 16 16:23:57 kernel: GET STA INFO failed, -19
Sep 16 16:23:57 kernel: GET STA INFO failed, -19
Sep 16 16:23:58 kernel: GET STA INFO failed, -19
Sep 16 16:23:58 kernel: dealloc_netinfo enter wdev=00000000afd7b831
Sep 16 16:23:58 kernel: dealloc_netinfo exit iface_cnt=2
Sep 16 16:23:58 kernel: dealloc_netinfo enter wdev=00000000178ced2a
Sep 16 16:23:58 kernel: dealloc_netinfo exit iface_cnt=1
Sep 16 16:23:58 kernel: dealloc_netinfo enter wdev=0000000013014aba
Sep 16 16:23:58 kernel: dealloc_netinfo exit iface_cnt=1
Sep 16 16:23:58 kernel: dhd_os_stop_wd_thread(): thread:dhd_watchdog_thread:3b5 terminated OK
Sep 16 16:23:58 kernel: ndev(wl0.1) 0000000023c5259b not found
Sep 16 16:23:58 acsd: acsd_chanim_query(878): failed to get chanim resultsret code: -19
Sep 16 16:23:58 kernel: iface_cnt=1
Sep 16 16:23:58 kernel: wl_probe_wdev_all: net_list[0] bssidx: 0, ifidx: 0 ndev(eth6): 00000000b0505634, wdev: 000000002110290c wdev->netdev(eth6): 00000000b0505634
Sep 16 16:23:58 kernel: ndev(wl0.1) 0000000023c5259b not found
Sep 16 16:23:58 kernel: iface_cnt=1
Sep 16 16:23:58 kernel: wl_probe_wdev_all: net_list[0] bssidx: 0, ifidx: 0 ndev(eth6): 00000000b0505634, wdev: 000000002110290c wdev->netdev(eth6): 00000000b0505634
Sep 16 16:23:58 kernel: ndev(wl0.1) 0000000023c5259b not found
Sep 16 16:23:58 kernel: iface_cnt=1
Sep 16 16:23:58 kernel: wl_probe_wdev_all: net_list[0] bssidx: 0, ifidx: 0 ndev(eth6): 00000000b0505634, wdev: 000000002110290c wdev->netdev(eth6): 00000000b0505634
Sep 16 16:23:58 kernel: ndev(wl0.1) 0000000023c5259b not found
Sep 16 16:23:58 kernel: iface_cnt=1
Sep 16 16:23:58 kernel: wl_probe_wdev_all: net_list[0] bssidx: 0, ifidx: 0 ndev(eth6): 00000000b0505634, wdev: 000000002110290c wdev->netdev(eth6): 00000000b0505634
Sep 16 16:23:58 kernel: Invalid device mode -1
Sep 16 16:23:58 kernel: Get event_msgs error (-19)
Sep 16 16:24:41 kernel: wfd_unregisterdevice Successfully unregistered ifidx 1 wfd_idx 1
Sep 16 16:24:41 acsd: acsd_chanim_query(878): failed to get chanim resultsret code: -19
Sep 16 16:24:41 kernel: ndev(wl0.1) 0000000023c5259b not found
Sep 16 16:24:41 kernel: iface_cnt=1
Sep 16 16:24:41 kernel: wl_probe_wdev_all: net_list[0] bssidx: 0, ifidx: 0 ndev(eth6): 00000000b0505634, wdev: 000000002110290c wdev->netdev(eth6): 00000000b0505634
Sep 16 16:24:41 kernel: ndev(wl0.1) 0000000023c5259b not found
Sep 16 16:24:41 kernel: iface_cnt=1
Sep 16 16:24:41 kernel: wl_probe_wdev_all: net_list[0] bssidx: 0, ifidx: 0 ndev(eth6): 00000000b0505634, wdev: 000000002110290c wdev->netdev(eth6): 00000000b0505634
Sep 16 16:24:41 kernel: ndev(wl0.1) 0000000023c5259b not found
Sep 16 16:24:41 kernel: iface_cnt=1
Sep 16 16:24:41 kernel: wl_probe_wdev_all: net_list[0] bssidx: 0, ifidx: 0 ndev(eth6): 00000000b0505634, wdev: 000000002110290c wdev->netdev(eth6): 00000000b0505634
Sep 16 16:24:41 kernel: ndev(wl0.1) 0000000023c5259b not found
Sep 16 16:24:41 kernel: iface_cnt=1
Sep 16 16:24:41 kernel: wl_probe_wdev_all: net_list[0] bssidx: 0, ifidx: 0 ndev(eth6): 00000000b0505634, wdev: 000000002110290c wdev->netdev(eth6): 00000000b0505634
Sep 16 16:24:41 kernel: Invalid device mode -1
Sep 16 16:24:41 kernel: GET STA INFO failed, -19
Sep 16 16:24:41 kernel: ndev(wl0.1) 0000000023c5259b not found
Sep 16 16:24:41 kernel: iface_cnt=1
Sep 16 16:24:41 kernel: wl_probe_wdev_all: net_list[0] bssidx: 0, ifidx: 0 ndev(eth6): 00000000b0505634, wdev: 000000002110290c wdev->netdev(eth6): 00000000b0505634
Sep 16 16:24:41 kernel: ndev(wl0.1) 0000000023c5259b not found
Sep 16 16:24:41 kernel: iface_cnt=1
Sep 16 16:24:41 kernel: wl_probe_wdev_all: net_list[0] bssidx: 0, ifidx: 0 ndev(eth6): 00000000b0505634, wdev: 000000002110290c wdev->netdev(eth6): 00000000b0505634
Sep 16 16:24:42 kernel: ndev(wl0.1) 0000000023c5259b not found
Sep 16 16:24:42 kernel: iface_cnt=1
Sep 16 16:24:42 kernel: wl_probe_wdev_all: net_list[0] bssidx: 0, ifidx: 0 ndev(eth6): 00000000b0505634, wdev: 000000002110290c wdev->netdev(eth6): 00000000b0505634
Sep 16 16:24:42 kernel: ndev(wl0.1) 0000000023c5259b not found
Sep 16 16:24:42 kernel: iface_cnt=1
Sep 16 16:24:42 kernel: wl_probe_wdev_all: net_list[0] bssidx: 0, ifidx: 0 ndev(eth6): 00000000b0505634, wdev: 000000002110290c wdev->netdev(eth6): 00000000b0505634
Sep 16 16:24:42 kernel: Invalid device mode -1
Sep 16 16:24:42 kernel: Get event_msgs error (-19)
Sep 16 16:24:42 kernel: find p2p index from wdev(0000000013014aba) failed
 
What did you end up doing? Based on the router sh!tting the bed at 16:20, I'd start out by setting fixed wireless channels instead of auto. Might be the symptom rather than the cause, but worth a try.
Router was failing ~24-48 hours on a restart. Decided to go back to the .5 firmware and ignore the client count. For a while the client count didn't move with the .5 firmware. Today's reboot has started that problem again. Figured whatever fixes are in .5 WITH the known irrelevant problem is better than the .4 version at this point.

What to do with no advice on how to make it last >24 hours? Router 6 months old. Cable modem days old. Has to be the router. Inspiriation. Hooked up a Kasa switch to the router. I have it power off at 4:30 AM and power on at 4:31 AM. Most days, it seems to be making it through the day without a crash. Wish I had a more techincal solution than that, but short of a solution, holding out for firmware .6 and hoping for the best.

Interesting idea on fixed wireless channels. Worth seeing how that might affect things. Not sure exactly how to configure that, but will diligently investigate. Thanks VERY MUCH for taking the time to respond and for giving me something else to try! :D <3
 
Based on the router sh!tting the bed at 16:20, I'd start out by setting fixed wireless channels instead of auto.
Worked with ChatGPT to figure out what was best, given my local competing WiFi signals. Here's what it had me choose:
Channel bandwidth (2.4G) - 20 MHz
Channel bandwidth (5G) - 40 MHz (check) Enable 160 MHz
Control Channel (2.4G) - 1 (best, alternatively 6 or 11)
Control Channel (5G) - 36

No idea if this aversely affects much negatively (i.e. some IoT device stops working / connecting), but about to reboot and give it a try! :)
 
5G should be 80 MHz. Leave 160 disabled. Disable AX on 2.4G.
Set 5G to 80, no 160. AX took a while to find. Turns out it's not where the old post was, but in "Professional" in mine. Everything seems to be connected and Clients: # count stable, too. Leaving Kasa reboot for 4:30 AM so I have a clean reboot for tomorrow, then can see how it goes.

Thanks!
 

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!
Back
Top