RT-AX86U Pro WIFI keeps restarting every hour

[crs]

I have this device for around 3 months. Around 2 month ago i started to observe weird behavior regarding wifi. Every hour or so my WiFi network turn on and off. I tried 4 different firmware version and always have the same result.. When i check logs i only see something
like this.

kernel: CSIMON: CSIMON[1.1.0] Initialization

kernel: CSIMON: M2M usr already registered ...

No other logs present when wifi drops. From what i can see other people with this device have the same problem.

 

[bennor]

Have you rebooted the router?
What firmware are you running?
Do you have a USB3 hard drive attached to the router?
What are your specific WiFi settings for the affected WiFi band (2.4 Ghz or 5 Ghz)?
A forum search turns up someone else who had a similar issue:

RT-AX86U PRO - CSIMON: M2M usr already registered

Since yesterday I am having issues with 2.4GHz network. All Wifi clients dropping. I can see my log is flodded with following. Mar 23 12:14:19 kernel: CSIMON: CSIMON[1.1.0] Initialization Mar 23 12:14:19 kernel: CSIMON: M2M usr already registered ... Mar 23 12:14:37 kernel: CSIMON...

www.snbforums.com

Edit to add: And the forum search turned up other earlier discussions:

RT-AX55 log looping. No Wifi clients can connect

Hello. I have been having problems with occasional disconnect of all wifi clients. Today when it happened again, and after the router was rebooted with the external button, I was able to inspect the log from the GUI interface. The following log shows an endless loop of messages for a few second...

www.snbforums.com

Asus RT-AX55 (kernel: CSIMON: M2M usr already registered ...)

Hello, This weekend my internet stared acting up... keeps going up and down several times... this usually happens around 19.00 last couple of hours.... Called my ISP this morning and they basically said "i cant see any problems from our end, but i see you have a 3rd party router, maybe thats...

www.snbforums.com

Use the forum search feature to find even more past discussions where people had similar error messages to see if there are any suggestions in those earlier discussions.

 

[crs]

Have you rebooted the router?

Yes, it didnt helped

What firmware are you running?

Currently 3.0.0.6.102_34319

Do you have a USB3 hard drive attached to the router?

No

What are your specific WiFi settings for the affected WiFi band (2.4 Ghz or 5 Ghz)?

This are my wireless settings. But im using guest network pro WIFI and have problems with that network in particular. I dont know if setting are duplicated between guest network and default WiFi network.

A forum search turns up someone else who had a similar issue:

RT-AX86U PRO - CSIMON: M2M usr already registered

Since yesterday I am having issues with 2.4GHz network. All Wifi clients dropping. I can see my log is flodded with following. Mar 23 12:14:19 kernel: CSIMON: CSIMON[1.1.0] Initialization Mar 23 12:14:19 kernel: CSIMON: M2M usr already registered ... Mar 23 12:14:37 kernel: CSIMON...

www.snbforums.com

from what i found out its a common issue but i didnt find any solution

 

[bennor]

from what i found out its a common issue but i didnt find any solution

Looking at the logs of my RT-AX86U Pro running latest stock Asus 3006 firmware the error cropped up a few times two days ago but hasn't shown up since. When the error shows up it is sometimes followed by one or more of the following:

kernel: wl0: wlc_ulmu_sw_trig_enable: HE UL-OFDMA not enabled
kernel: In wl_dfs_cac_notify_status chanspec 0xd024 DFS state 0
kernel: In wl_dfs_cac_notify_status chanspec 0xe832 DFS state 0
kernel: In wl_dfs_cac_notify_status chanspec 0xe832 DFS state 1
kernel: wfd_registerdevice Successfully registered dev wl0.1 ifidx 1 wfd_idx 0
kernel: wfd_registerdevice Successfully registered dev wl0.2 ifidx 2 wfd_idx 0

Don't seem to notice any WiFi devices not being able to connect though. And I do have DFS enabled (160 MHz) on the 5 Ghz WiFi band.

 

[bbunge]

Not experiencing that issue here on 3.0.0.6.102_34349-g805dff6_403-gd851b. There are, however, a couple of minor issues with this firmware that may not bother your setup.
There is also a beta firmware for the AX86U Pro that does fix a couple of issues. You may want to try it. Link here: https://www.asuswebstorage.com/navi...12473A99044A16686800F04?type=previewPageCover

I do recommend you upgrade to the 3.0.0.6.102_34349 firmware at a minimum. Might also be a good idea to power cycle the router then do a factory reset and manually configure. I know it is a pain but might be worth the effort.

 

[bennor]

@crs, post your Wireless > General settings too, redacting sensitive information if needed.

Is there any other equipment next to or near by the router?
Are you in a location with a lot of WiFi signals from the neighbor's routers?
Have you tried a hard factory reset and manual reconfiguration?
Try installing the latest firmware (3.0.0.6.102_34349).
If the error is happening repeatedly, try powering off all WiFi client devices to see if the errors persist. If they don't then try powering on each WiFi client, one at a time, to see if there is a specific WiFi client causing the issue.

 

[crs]

Not experiencing that issue here on 3.0.0.6.102_34349-g805dff6_403-gd851b. There are, however, a couple of minor issues with this firmware that may not bother your setup.
There is also a beta firmware for the AX86U Pro that does fix a couple of issues. You may want to try it. Link here: https://www.asuswebstorage.com/navi...12473A99044A16686800F04?type=previewPageCover

I do recommend you upgrade to the 3.0.0.6.102_34349 firmware at a minimum. Might also be a good idea to power cycle the router then do a factory reset and manually configure. I know it is a pain but might be worth the effort.

thanks for the info about beta firmware. Is there a guide how to install it? i will give it a try

post your Wireless > General settings too

Keep in mind i have problems with guest wifi. I didnt test default wifi and dont know if these settings apply to guest wifi

Is there any other equipment next to or near by the router?

only power strip, i doubt thats causing the problem but i moved it to be sure

Are you in a location with a lot of WiFi signals from the neighbor's routers?

apartment building

Have you tried a hard factory reset and manual reconfiguration?

Only factory restart and recovery from cfg file. I will test it with some device off to see if that help. Meanwhile i post some more detailed logs from router

19:50:32 wlceventd: wlceventd_proc_event(645): wl0.1: Deauth_ind 54:48:E6:931:BA, status: 0, reason: Deauthenticated because sending stationis leaving (or has left) IBSS or ESS (3), rssi:0
19:50:35 wlceventd: wlceventd_proc_event(662): wl0.1: Disassoc 54:48:E6:C2:8F:CE, status: 0, reason: Disassociated due to inactivity(4), rssi:0
19:50:36 wlceventd: wlceventd_proc_event(645): wl0.1: Deauth_ind 54:48:E6:C2:8F:CE, status: 0, reason: Deauthenticated because sending stationis leaving (or has left) IBSS or ESS (3), rssi:0
19:50:41 kernel:CSIMON: CSIMON[1.1.0]Initialization
19:50:41 kernel:CSIMON: M2M usr alreadyregistered ...
19:50:50 kernel:CSIMON: CSIMON[1.1.0]Initialization
19:50:50 kernel:CSIMON: M2M usr alreadyregistered ...
19:50:58 kernel:CSIMON: CSIMON[1.1.0]Initialization
19:50:58 kernel:CSIMON: M2M usr alreadyregistered ...
19:51:08 kernel:CSIMON: CSIMON[1.1.0]Initialization
19:51:08 kernel:CSIMON: M2M usr alreadyregistered ...
19:51:09 wlceventd: wlceventd_proc_event(685): wl1.1: Auth 2E5:93:CE:EE:3A, status:Successful (0), rssi:-36
19:51:09 wlceventd: wlceventd_proc_event(722): wl1.1: Assoc 2E5:93:CE:EE:3A, status:Successful (0), rssi:-36
19:51:16 kernel:CSIMON: CSIMON[1.1.0]Initialization
19:51:16 kernel:CSIMON: M2M usr alreadyregistered ...
19:51:16 wlceventd: wlceventd_proc_event(645): wl1.1: Deauth_ind 2E5:93:CE:EE:3A, status: 0, reason: Unspecified reason (1), rssi:-36
19:51:16 wlceventd: wlceventd_proc_event(645): wl1.1: Deauth_ind 2E5:93:CE:EE:3A, status: 0, reason: Unspecified reason (1), rssi:-36
19:51:19 wlceventd: wlceventd_proc_event(685): wl0.1: Auth 58:B6:23:67:AC:17, status:Successful (0), rssi:0
19:51:19 wlceventd: wlceventd_proc_event(722): wl0.1: Assoc 58:B6:23:67:AC:17, status:Successful (0), rssi:-52
19:51:22 wlceventd: wlceventd_proc_event(645): wl0.1: Deauth_ind 6E:3ADA:A5:BF, status: 0, reason: Unspecified reason (1), rssi:-49
19:51:22 wlceventd: wlceventd_proc_event(685): wl0.1: Auth 6E:3ADA:A5:BF, status:Successful (0), rssi:-49
19:51:22 wlceventd: wlceventd_proc_event(722): wl0.1: Assoc 6E:3ADA:A5:BF, status:Successful (0), rssi:-49
19:51:28 wlceventd: wlceventd_proc_event(645): wl0.1: Deauth_ind 68:14:01:83:BE:AD, status: 0, reason: Disassociateddue toinactivity (4), rssi:-49
19:51:29 wlceventd: wlceventd_proc_event(645): wl0.1: Deauth_ind 68:14:01:83:BE:AD, status: 0, reason: Disassociateddue toinactivity (4), rssi:0
19:51:36 wlceventd: wlceventd_proc_event(685): wl0.1: Auth BA:51:95:37:EA:73, status:Successful (0), rssi:0
19:51:36 wlceventd: wlceventd_proc_event(722): wl0.1: Assoc BA:51:95:37:EA:73, status:Successful (0), rssi:-25
19:51:52 wlceventd: wlceventd_proc_event(685): wl0.1: Auth 54:48:E6:C2:8F:CE, status:Successful (0), rssi:0
19:51:52 wlceventd: wlceventd_proc_event(722): wl0.1: Assoc 54:48:E6:C2:8F:CE, status:Successful (0), rssi:-33
19:51:52 wlceventd: wlceventd_proc_event(685): wl0.1: Auth 54:48:E6:931:BA, status:Successful (0), rssi:0
19:51:52 wlceventd: wlceventd_proc_event(722): wl0.1: Assoc 54:48:E6:931:BA, status:Successful (0), rssi:-45
19:52:05 wlceventd: wlceventd_proc_event(685): wl0.1: Auth 68:14:01:83:BE:AD, status:Successful (0), rssi:0
19:52:05 wlceventd: wlceventd_proc_event(722): wl0.1: Assoc 68:14:01:83:BE:AD, status:Successful (0), rssi:-53
19:59:21 cfg_server: cm_updateChanspec call wl_chanspec_changed_action
19:59:21 cfg_server: event: wl_chanspec_changed_action_a101 of eid(99) of cfgs(5594)
19:59:32 acsd: acs_bgdfs_check_status(656): eth7: background scan channel 0xd87e mismatch [0xe03a, 0xe03a, 0xe03a, 0xe03a]
19:59:58 wlceventd: wlceventd_proc_event(645): wl0.1: Deauth_ind 68:14:01:83:BE:AD, status: 0, reason: Disassociateddue toinactivity (4), rssi:-49
20:01:40 wlceventd: wlceventd_proc_event(645): wl0.1: Deauth_ind 58:B6:23:67:AC:17, status: 0, reason: Disassociateddue toinactivity (4), rssi:-50
20:02:10 wlceventd: wlceventd_proc_event(685): wl0.1: Auth 58:B6:23:67:AC:17, status:Successful (0), rssi:0
20:02:10 wlceventd: wlceventd_proc_event(722): wl0.1: Assoc 58:B6:23:67:AC:17, status:Successful (0), rssi:-53
20:06:55 cfg_server: cm_updateChanspec call wl_chanspec_changed_action
20:06:55 cfg_server: event: wl_chanspec_changed_action_a101 of eid(100) of cfgs(5594)
20:07:37 wlceventd: wlceventd_proc_event(685): wl0.1: Auth 4C:B0:4A:75:BE:44, status:Successful (0), rssi:0
20:07:37 wlceventd: wlceventd_proc_event(722): wl0.1: Assoc 4C:B0:4A:75:BE:44, status:Successful (0), rssi:-23