5G network crashing on an AC86U

[jeden]

Sometimes, like once a day, I get these messages (kernel trap, etc etc) and the 5G network stays visible but it does not accept any more clients.

May  8 16:54:31 kernel: DUMP CONSOLE: 030028.174 wl1: STA xx:xx:xx:xx:bf:ab removed from MU client set.
May  8 16:54:31 kernel: DUMP CONSOLE: 030028.174 wl1: STA xx:xx:xx:xx:da:f4 removed from MU client set.
May  8 16:54:31 kernel: DUMP CONSOLE: 030028.175 wlc_ucode_download: wl1: Loading non-MU ucode
May  8 16:54:31 kernel: DUMP CONSOLE: 030028.190 wl1: CORE INIT : nfifo 32 mu_tx_enab 0
May  8 16:54:31 kernel: DUMP CONSOLE: 030028.190 wl1: CORE INIT : mode 2 pktclassify 1 rxsplit 0  hdr conve 0 DMA_CT Enabled
May  8 16:54:31 kernel: DUMP CONSOLE: 030028.211 wl1: link up (wl1)
May  8 16:54:31 kernel: DUMP CONSOLE: 030028.218 wl1.0: wlc_send_bar: seq 0x1d0 tid 0
May  8 16:54:31 kernel: DUMP CONSOLE: 030028.219 wl1.0: wlc_send_bar: seq 0x29 tid 3
May  8 16:54:31 kernel: DUMP CONSOLE: 030028.488 wl1.0: wlc_send_bar: seq 0x46 tid 6
May  8 16:54:31 kernel: DUMP CONSOLE: 030029.121 wl1.0: wlc_send_bar: seq 0xdd0 tid 3
May  8 16:54:31 kernel: DUMP CONSOLE: 030029.248 wl1.0: wlc_send_bar: seq 0x57c tid 0
May  8 16:54:31 kernel: DUMP CONSOLE: 030032.174 wlc_ucode_download: wl1: Loading MU ucode
May  8 16:54:31 kernel: DUMP CONSOLE: 030032.190 wl1: CORE INIT : nfifo 32 mu_tx_enab 1
May  8 16:54:31 kernel: DUMP CONSOLE: 030032.190 wl1: CORE INIT : mode 2 pktclassify 1 rxsplit 0  hdr conve 0 DMA_CT Enabled
May  8 16:54:31 kernel: DUMP CONSOLE: 030032.211 wl1: link up (wl1)
May  8 16:54:31 kernel: DUMP CONSOLE: 030032.212 wl1.0: wlc_send_bar: seq 0xddc tid 3
May  8 16:54:31 kernel: DUMP CONSOLE: 030032.214 wl1.0: wlc_send_bar: seq 0x4a0 tid 0
May  8 16:54:31 kernel: DUMP CONSOLE: 030032.214 wl1.0: wlc_send_bar: seq 0x88c tid 3
May  8 16:54:31 kernel: DUMP CONSOLE: 030032.374 wl1.0: wlc_send_bar: seq 0x59b tid 0
May  8 16:54:31 kernel: DUMP CONSOLE: 030033.174 wl1: STA xx:xx:xx:xx:da:f4 selected as MU client at index 1.
May  8 16:54:31 kernel: DUMP CONSOLE: 030033.174 wl1: STA xx:xx:xx:xx:bf:ab selected as MU client at index 0.
May  8 16:54:31 kernel: DUMP CONSOLE: 030040.173 wl1: STA xx:xx:xx:xx:bf:ab removed from MU client set.
May  8 16:54:31 kernel: DUMP CONSOLE: 030040.173 wl1: STA xx:xx:xx:xx:da:f4 removed from MU client set.
May  8 16:54:31 kernel: DUMP CONSOLE: 030040.174 wlc_ucode_download: wl1: Loading non-MU ucode
May  8 16:54:31 kernel: DUMP CONSOLE: 030040.189 wl1: CORE INIT : nfifo 32 mu_tx_enab 0
May  8 16:54:31 kernel: DUMP CONSOLE: 030040.190 wl1: CORE INIT : mode 2 pktclassify 1 rxsplit 0  hdr conve 0 DMA_CT Enabled
May  8 16:54:31 kernel: DUMP CONSOLE: 030040.210 wl1: link up (wl1)
May  8 16:54:31 kernel: DUMP CONSOLE: 030040.212 wl1.0: wlc_send_bar: seq 0x5d9 tid 0
May  8 16:54:31 kernel: DUMP CONSOLE: 030040.213 wl1.0: wlc_send_bar: seq 0xeb8 tid 3
May  8 16:54:31 kernel: DUMP CONSOLE: 030040.215 wl1.0: wlc_send_bar: seq 0x2d3 tid 0
May  8 16:54:31 kernel: DUMP CONSOLE: 030040.215 wl1.0: wlc_send_bar: seq 0x4a2 tid 3
May  8 16:54:31 kernel: DUMP CONSOLE: 030041.175 wlc_ucode_download: wl1: Loading MU ucode
May  8 16:54:31 kernel: DUMP CONSOLE: 030041.190 wl1: CORE INIT : nfifo 32 mu_tx_enab 1
May  8 16:54:31 kernel: DUMP CONSOLE: 030041.191 wl1: CORE INIT : mode 2 pktclassify 1 rxsplit 0  hdr conve 0 DMA_CT Enabled
May  8 16:54:31 kernel: DUMP CONSOLE: 030041.211 wl1: link up (wl1)
May  8 16:54:31 kernel: DUMP CONSOLE: 030041.212 wl1.0: wlc_send_bar: seq 0x5eb tid 0
May  8 16:54:31 kernel: DUMP CONSOLE: 030041.214 wl1.0: wlc_send_bar: seq 0x6a0 tid 3
May  8 16:54:31 kernel: DUMP CONSOLE: 030041.214 wl1.0: wlc_send_bar: seq 0x78f tid 0
May  8 16:54:31 kernel: DUMP CONSOLE: 030041.223 
May  8 16:54:31 kernel: DUMP CONSOLE: FWID 01-157f5da0
May  8 16:54:31 kernel: DUMP CONSOLE: flags 330005
May  8 16:54:31 kernel: DUMP CONSOLE: 030041.223 
May  8 16:54:31 kernel: DUMP CONSOLE: TRAP 4(2ab9d0): pc 20de54, lr 23c1d9, sp 2aba28, cpsr 8000193, spsr 8000033
May  8 16:54:31 kernel: DUMP CONSOLE: 030041.223   dfsr 7, dfar 46b468
May  8 16:54:31 kernel: DUMP CONSOLE: 030041.223   r0 5e4, r1 43a89c, r2 43b268, r3 c080, r4 2aba5c, r5 1e, r6 43a89c
May  8 16:54:31 kernel: DUMP CONSOLE: 030041.223   r7 0, r8 42416c, r9 33e834, r10 0, r11 20078c, r12 7c0
May  8 16:54:31 kernel: DUMP CONSOLE: 030041.223 
May  8 16:54:31 kernel: DUMP CONSOLE:    sp+0 0033e494 0042416c 0033e834 00000012
May  8 16:54:31 kernel: DUMP CONSOLE: 030041.223   sp+10 0033e4b8 0043a89c 003404a4 0023c443
May  8 16:54:31 kernel: DUMP CONSOLE: 
May  8 16:54:31 kernel: DUMP CONSOLE: 030041.223 sp+1c 0023c443
May  8 16:54:31 kernel: DUMP CONSOLE: 030041.223 sp+c4 0023ccd1
May  8 16:54:31 kernel: DUMP CONSOLE: 030041.223 sp+11c 0026b177
May  8 16:54:31 kernel: DUMP CONSOLE: 030041.223 sp+164 0020a56d
May  8 16:54:31 kernel: DUMP CONSOLE: 030041.223 sp+19c 00200001
May  8 16:54:31 kernel: DUMP CONSOLE: 030041.223 sp+1b0 0000880f
May  8 16:54:31 kernel: DUMP CONSOLE: 030041.223 sp+1fc 0026cfdb
May  8 16:54:31 kernel: DUMP CONSOLE: 030041.223 sp+23c 002457fd
May  8 16:54:31 kernel: DUMP CONSOLE: 030041.223 sp+24c 00003e79
May  8 16:54:31 kernel: DUMP CONSOLE: 030041.223 sp+274 002515f3
May  8 16:54:31 kernel: DUMP CONSOLE: 030041.223 sp+28c 002517d7
May  8 16:54:31 kernel: DUMP CONSOLE: 030041.223 sp+2b4 0022f1c5
May  8 16:54:31 kernel: DUMP CONSOLE: 030041.223 sp+2c4 00251901
May  8 16:54:31 kernel: DUMP CONSOLE: 030041.223 sp+2c8 0001d2ad
May  8 16:54:31 kernel: DUMP CONSOLE: 030041.223 sp+2dc 0001d4cd
May  8 16:54:31 kernel: DUMP CONSOLE: 030041.223 sp+2ec 000120cf
May  8 16:54:31 kernel: dhdpcie_checkdied: msgtrace address : 0x00000000
May  8 16:54:31 kernel: console address  : 0x0043FCF0
May  8 16:54:31 kernel: Assrt not built in dongle
May  8 16:54:31 kernel: TRAP type 0x4 @ epc 0x20de54, cpsr 0x8000193, spsr 0x8000033, sp 0x2aba28, lp 0x23c1d9, rpc 0x20de54
May  8 16:54:31 kernel: Trap offset 0x2ab9d0, r0 0x5e4, r1 0x43a89c, r2 0x43b268, r3 0xc080, r4 0x2aba5c, r5 0x1e, r6 0x43a89c, r7 0x0

(I've attached a longer log that contains messages that appear before and later.)

Here's the configuration, as I could have poked something I shouldn't have.

As you can see, the channel has changed to 0, and if I click the dropdown there are no options other than Auto. Actual channel is usually 64.

Thank you.

 

[jeden]

That was 384.17, but I've just checked—it happens on 3.0.0.4.384_81858 also.

 

[K-2SO]

Current Control Channel 0 - usually bad news. Same thing in Asus stock and Merlin - RMA time.

 

[jeden]

Good insight. I've been looking at other threads and it seems most of the affected users had that problem right after booting, and not after a while of using the router.

Truth is I've been playing a lot lately with the 5G settings, changing channels constantly, etc. because I wanted to see which one would give me the best latency and throughput results. I will stop changing the configuration to see if it doesn't happen again, which could indicate a software problem. Otherwise I'll have to RMA the router which, in the current situation, will be a headache.

Thanks!

 

[KGB7]

Manually set channel and the channel width.

 

[jeden]

Thank you. Channel was manually set, but I am going to set width to 80 MHz. (It was 20/40/80)

 

[jeden]

Unfortunately it keeps happening once a day. Channel is 0 but the MAC address is visible in the webui (other users mentioned they couldn't see it anymore). Additionally, one of the crashes didn't produce a trap message in the syslog.

I've rolled back to 384.15. It was working fine there and the 384.16 changelog mentions "UPDATED: Merged SDK + binary blobs 384_81352 for RT-AC86U" which could be related.

I'd gladly return it but once again it is not possible currently. I'll post here if anything changes.

 

[jrmtz85]

ran into the same issue on an 86U. Wifi was transmitting, but no devices could connect. Had to RMA twice, but the second time, Asus just sent me a brand new 86U. Discussed here:
https://www.snbforums.com/threads/ac86u-after-a-few-days-has-no-5ghz-clients.54752/

 

[jeden]

It kept happening again and again, I just returned it and got an 88U instead. We'll see how it goes.

 

[jeden]

Just a few months later, the 88U is doing the exact same thing. Great hardware quality it seems.