What's new

RT-AX56U - Wifi 2.4Ghz disconnected (wl0: fatal error)

  • 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!

screamjojo

Occasional Visitor
Hi everybody,

Randomly, every days, my 2.4Ghz clients no longer have internet access, when it tries to connect to the wifi network, it disappears and then reappears in my client list but does not stay connected.
I have been looking for a solution on the forum for a long time (disabled Airtime, enabled Bluetooth Coexistence ...) but I cannot find what could cause my problem. Can you help me ?
Firmware : Merlin 384.16
Asus RT-AX56U

No problem with 5ghz.

Log :

Code:
Apr 26 11:24:42 kernel: wl0: fatal error, reinitializing, total count of reinit's[18908]
Apr 26 11:24:42 kernel: wl0: fatal error, reinitializing, total count of reinit's[18909]
Apr 26 11:24:43 kernel: wl0: PSMx dump at 297893 seconds. corerev 130.1 reason:watchdog ucode revision 1518.123 features 0x5106
Apr 26 11:24:43 kernel: psmxdebug 0x01ff0022 macctl 0x80000403 maccmd 0x4
Apr 26 11:24:43 kernel: psm_brc 0x0000 psm_brc_1 0x0000 M_UCODE_DBGST 0x0
Apr 26 11:24:43 kernel: PC (psmdebug_x):
Apr 26 11:24:43 kernel: 0x1ff0022  0x1fd0639  0x170642   0x1d90644
Apr 26 11:24:43 kernel: 0x1ff0022  0x7f0637   0x1ff063d  0x7f0641
Apr 26 11:24:43 kernel: 0x1ff0022  0x1ff0636  0x1ff063b  0x1ff067f
Apr 26 11:24:43 kernel: 0x1ff0022  0x1ff0636  0x1ff063b  0x1ff067f
Apr 26 11:24:43 kernel: 0x1ff0022  0x1ff0636  0x1ff063b  0x1ff067e
Apr 26 11:24:43 kernel: 0x1ff0022  0x1ff0636  0x1ff063b  0x1ff067e
Apr 26 11:24:43 kernel: 0x1ff0022  0x7f0637   0x1ff063d  0x1ff0681
Apr 26 11:24:43 kernel: 0x1ff0022  0x7f0637   0x170642   0x1950642
Apr 26 11:24:43 kernel: 0x1ff0022  0x370638   0x1ff063e  0x1ff0681
Apr 26 11:24:43 kernel: 0x1ff0022  0x1ff0636  0x1ff063b  0x1ff067f
Apr 26 11:24:43 kernel: 0x1ff0022  0x370638   0x1d90644  0x1fd0644
Apr 26 11:24:43 kernel: 0x1ff0022  0x1ff0636  0x1ff063c  0x1ff0640
Apr 26 11:24:43 kernel: 0x1ff0022  0x1ff0636  0x1ff063c  0x1ff0680
Apr 26 11:24:43 kernel: 0x1ff0022  0x7f0637   0x1ff063d  0x1ff0681
Apr 26 11:24:43 kernel: 0x1ff0022  0x1ff0636  0x1ff063c  0x1ff067f
Apr 26 11:24:43 kernel: 0x1ff0022  0x7f0637   0x1ff063d  0x1ff0681
Apr 26 11:24:43 kernel: PC (psmdebug):
Apr 26 11:24:43 kernel: 0x1ff001a  0x1d90054  0x1ff05f3  0x1fd01f0
Apr 26 11:24:43 kernel: 0x1ff001a  0x1930054  0x1ff05ef  0x7f01ee
Apr 26 11:24:43 kernel: psmx stack_status : 0x5
Apr 26 11:24:43 kernel: psmx stack_entries:
Apr 26 11:24:43 kernel: 0x0000
Apr 26 11:24:43 kernel: 0x0000
Apr 26 11:24:43 kernel: 0x0000
Apr 26 11:24:43 kernel: 0x0000
Apr 26 11:24:43 kernel: 0x0000
Apr 26 11:24:43 kernel: 0x0000
Apr 26 11:24:43 kernel: 0x0000
Apr 26 11:24:43 kernel: 0x0000

My configuration page :

2-4.jpg

2-4pro.jpg

5pro.jpg

Annotation-2020-04-26-113228.jpg


Thanks in advance for your help.
 
Hi,
I´m not an expert, but I would try to disable the option to selection channel 12 & 13. Some devices may not be too fond of these I believe. Also - maybe try a fixed channel (1-11).
 
Do not use Auto Control Channels for either band (eventually, you'll have issues on both). Use 1, 6 or 11 and 20MHz bandwidth for the 2.4GHz band. Use non-DFS channels for the 5GHz band with 20/40/80 MHz bandwidth.

Disable Universal Beamforming. Disable Airtime fairness.

I would also suggest an 8 alphanumeric character SSID with no spaces, punctuation, special characters, or smiley faces. The password the same except for 16 characters long too.
 
Hi,
I've always the problem :

Code:
Apr 28 11:18:02 kernel: txe_vasip_intsts 0x0
Apr 28 11:18:02 kernel: wl0: fatal error, reinitializing, total count of reinit's[11577]
Apr 28 11:18:03 kernel: wl0: PSMx dump at 76299 seconds. corerev 130.1 reason:watchdog ucode revision 1518.123 features 0x5106
Apr 28 11:18:03 kernel: psmxdebug 0x01ff0022 macctl 0x80000403 maccmd 0x4
Apr 28 11:18:03 kernel: psm_brc 0x98d3 psm_brc_1 0x0000 M_UCODE_DBGST 0x0
Apr 28 11:18:03 kernel: PC (psmdebug_x):
Apr 28 11:18:03 kernel: 0x1ff0022  0x1fd05d5  0x170642   0x150642
Apr 28 11:18:03 kernel: 0x1ff0022  0x1fd05d5  0x1ff003e  0x1ff067d
Apr 28 11:18:03 kernel: 0x1ff0022  0x1fd05d5  0x1ff003e  0x1ff067d
Apr 28 11:18:03 kernel: 0x1ff0022  0x1fd05d5  0x1ff003e  0x1ff0640
Apr 28 11:18:03 kernel: 0x1ff0022  0x1ff0636  0x1ff063b  0x1ff0640
Apr 28 11:18:03 kernel: 0x1ff0022  0x1ff0636  0x1ff063c  0x1ff0680
Apr 28 11:18:03 kernel: 0x1ff0022  0x1fd05d5  0x1ff003e  0x1ff067e
Apr 28 11:18:03 kernel: 0x1ff0022  0x1ff0636  0x1ff063b  0x1ff067e
Apr 28 11:18:03 kernel: 0x1ff0022  0x1fd05d5  0x1ff003e  0x1ff067e
Apr 28 11:18:03 kernel: 0x1ff0022  0x1ff0636  0x1ff063c  0x7f0641
Apr 28 11:18:03 kernel: 0x1ff0022  0x1fd05d5  0x1ff003e  0x1ff067d
Apr 28 11:18:03 kernel: 0x1ff0022  0x1fd05d5  0x1ff003e  0x1ff067d
Apr 28 11:18:03 kernel: 0x1ff0022  0x1fd05d5  0x1ff003e  0x1ff067d
Apr 28 11:18:03 kernel: 0x1ff0022  0x1ff0636  0x1ff063b  0x1ff067e
Apr 28 11:18:03 kernel: 0x1ff0022  0x1fd05d5  0x1ff003e  0x1ff067d
Apr 28 11:18:03 kernel: 0x1ff0022  0x1fd05d5  0x1ff003e  0x1ff067e
Apr 28 11:18:03 kernel: PC (psmdebug):
Apr 28 11:18:03 kernel: 0x1ff001a  0x1d90054  0x1ff05f1  0x19301f0
Apr 28 11:18:03 kernel: 0x1ff001a  0x1d90054  0x1ff05f1  0x3701ef
Apr 28 11:18:03 kernel: psmx stack_status : 0x5
Apr 28 11:18:03 kernel: psmx stack_entries:
Apr 28 11:18:03 kernel: 0x8080
Apr 28 11:18:03 kernel: 0x8080
Apr 28 11:18:03 kernel: 0x8080
Apr 28 11:18:03 kernel: 0x8080
Apr 28 11:18:03 kernel: 0x8080
Apr 28 11:18:03 kernel: 0x8080
Apr 28 11:18:03 kernel: 0x8080
Apr 28 11:18:03 kernel: 0x8080

I don't know when the problem appears but I've always activate time settings to stop the 2 wifi networks at night. Perhaps the problem appears at the time of reactivation. I am with a second router for Aimesh.

As you can see I have changed the parameters as recommended by @L&LD

param2-4.jpg

pro2-4.jpg


Thanks for your help
 
Seems like the 2.4 GHz radio flats out dies. Try a complete power reset (unplug the power for 5-10 seconds with the router still turned on, then plug it back in). If it still fails, contact Asus or the reseller for a replacement.
 
Seems like the 2.4 GHz radio flats out dies. Try a complete power reset (unplug the power for 5-10 seconds with the router still turned on, then plug it back in). If it still fails, contact Asus or the reseller for a replacement.
I did a factory reset but the problem persists. I sent a ticket to Asus support... Awaiting.
In all case, thanks for your help.
 
I did a factory reset but the problem persists. I sent a ticket to Asus support... Awaiting.
In all case, thanks for your help.

But did you try an electrical reset as suggested, not just resetting your settings?
 
Do you think I can try a most stable firmware ?

It's not a firmware issue. Your log indicates that the radio flats out dies/crashes.
 
I have the same problem with by brand new AC3100. If I factory reset it back to the latest stock it works fine. It is happening wit .17 and .16 but that is far back as I have tested. I have done countless factory resets and restores, unplugged the power for a few minutes, etc. It seems like the radio is working because the site survey is showing other networks on 2.4ghz.

If I reboot the router I can see clients on 2.4ghz for a while, but at some point they disconnect.


Sent from my iPhone using Tapatalk
 
I have the same problem with by brand new AC3100. If I factory reset it back to the latest stock it works fine. It is happening wit .17 and .16 but that is far back as I have tested. I have done countless factory resets and restores, unplugged the power for a few minutes, etc. It seems like the radio is working because the site survey is showing other networks on 2.4ghz.

If I reboot the router I can see clients on 2.4ghz for a while, but at some point they disconnect.


Sent from my iPhone using Tapatalk

You mean you no longer have the problem with the Asus firmware 384.8253 ?

PS: I noticed that the problem only occurs at night when "wireless scheduler" is activated so the wifi network is switched off...
 
You mean you no longer have the problem with the Asus firmware 384.8253 ?

PS: I noticed that the problem only occurs at night when "wireless scheduler" is activated so the wifi network is switched off...

I can still go back to the stock firmware and everything works fine, but I really want to use the extra features in Merlin. I use the Parental Controls and time scheduling, but not on the devices that are using 2.4ghz. Here is what has happened so far this morning.

8am - Unplugged router for a minute and powered it back up.
Looked at the current clients and some are on 2.4ghz, most are on 5ghz.
Sometime around 10:30am-11am - no clients on 2.4 and a 2.4 only client can not see any networks.
Around 11:15 - the 2.4 only client can see network again.

I am currently setup to use Smart Connect, because if a 5ghz capable device connects at 2.4ghz it will reconnect at 5ghz when 2.4 fails.
 
I have an ax58u that is exhibiting the same issue as @screamjojo . When new, the 2.4 worked but i immediately went to Merlin .17. I went back to stock earlier and noticed that when i booted after the flash to stock, the 2.4 asus network name wasnt listing. I am seeing the same wl0 crash in the logs. It is an eBay refrub and I will contact the reseller for a replacment.

@screamjojo Did you solve your problem?

Code:
May 22 21:32:29 kernel: wl0: wlc_bmac_suspend_mac_and_wait: waited 83000 uS and MI_MACSSPNDD is still not on.
May 22 21:32:29 kernel: wl0: reason = mac suspend failure at 323 seconds. corerev 130.1 ucode revision 1518.132 features 0x5106
May 22 21:32:29 kernel: psmdebug 0x01d91de9 phydebug 0x0 macctl 0x84160402 maccmd 0x14
May 22 21:32:29 kernel: psm_brc 0x0000 psm_brc_1 0x0000 M_UCODE_DBGST 0x2
May 22 21:32:29 kernel: brwk_0 0x118b brwk_1 0x0010 brwk_2 0xaa81 brwk_3 0x0ef0 brwk_4 0x0000
May 22 21:32:29 kernel: wlc_dump_ucode_fatal: log_done 0x4
May 22 21:32:29 kernel: wl0: fatal error, reinitializing, total count of reinit's[509]
May 22 21:32:29 kernel: wl0: wlc_bmac_suspend_mac_and_wait: waited 83000 uS and MI_MACSSPNDD is still not on.
 
I have an ax58u that is exhibiting the same issue as @screamjojo . When new, the 2.4 worked but i immediately went to Merlin .17. I went back to stock earlier and noticed that when i booted after the flash to stock, the 2.4 asus network name wasnt listing. I am seeing the same wl0 crash in the logs. It is an eBay refrub and I will contact the reseller for a replacment.

@screamjojo Did you solve your problem?

Code:
May 22 21:32:29 kernel: wl0: wlc_bmac_suspend_mac_and_wait: waited 83000 uS and MI_MACSSPNDD is still not on.
May 22 21:32:29 kernel: wl0: reason = mac suspend failure at 323 seconds. corerev 130.1 ucode revision 1518.132 features 0x5106
May 22 21:32:29 kernel: psmdebug 0x01d91de9 phydebug 0x0 macctl 0x84160402 maccmd 0x14
May 22 21:32:29 kernel: psm_brc 0x0000 psm_brc_1 0x0000 M_UCODE_DBGST 0x2
May 22 21:32:29 kernel: brwk_0 0x118b brwk_1 0x0010 brwk_2 0xaa81 brwk_3 0x0ef0 brwk_4 0x0000
May 22 21:32:29 kernel: wlc_dump_ucode_fatal: log_done 0x4
May 22 21:32:29 kernel: wl0: fatal error, reinitializing, total count of reinit's[509]
May 22 21:32:29 kernel: wl0: wlc_bmac_suspend_mac_and_wait: waited 83000 uS and MI_MACSSPNDD is still not on.

Hi,
When I go back to stock, problem always here. But I've don't try a hard reset after I go back to stock firmware.
My solution : Activate Smart Connect. But with all this problems (2,4ghz crash, QOS bandwitch limiter not working good ...) I think this router is not stable, I will not keep it.
Good luck, hope team Merlin or Asus will fix this issu...
 
@screamjojo, if you're not testing with a full reset after flopping back and forth from stock to RMerlin firmware, no wonder the router isn't stable for you.

This may (or may not) be an issue for either Asus or RMerlin to fix. :)
 
I'm having the same issues as mentioned above by @screamjojo and FYI, it's been straight out of the box and with stock firmware since day 1 having this issue.
 
@Waffleboi, how many firmware versions have you flashed since 'day 1'?

Flashing between different flavors of firmware isn't the only reason to do a full reset if the situation warrants it.
 

Similar threads

Latest threads

Sign Up For SNBForums Daily Digest

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