RT-BE92U Persistent Thermal Zone Faults

[RicoSuave]

First post here so bear with me if I miss anything. Since purchase, my RT-BE92U has been plagued with the same issues others have posted here. Up until the new firmware version dropped, I was having constant problems with network stability. I am currently running the latest firmware version (3.0.0.6.102_37435) and a lot of the issues seem to have been resolved except for one. Before the firmware update, I was seeing intermittent thermal zone errors in the system log. Since applying the update, I am consistently getting the following errors that appear every 3 seconds exactly:

Jan 4 18:29:52 kernel: read_bpcm_reg_direct_keyhole: Wait for completion failed, devAddr 0x3, offset 24, idx 2
Jan 4 18:29:52 kernel: thermal thermal_zone0: Failed to get RAIL 0 temperature, ret=256
Jan 4 18:29:52 kernel: thermal thermal_zone0: Failed to get temperature, ret=-1
Jan 4 18:29:52 kernel: thermal thermal_zone0: failed to read out thermal zone (-1)

On occasion, the errors coincide with a drastic decrease in wireless network performance. Under normal conditions, when connected to the 6GHz network, my wireless network download speed averages around 1100Mbps. This will drop to a nearly unusable 2-3Mbps. The 2.5GHz and 5GHz networks also see a decrease in speed to around the same 2-3Mbps. Wired clients seem unaffected. Once I perform a hard reset to the router, it seems to correct the speed issue for a while, but the thermal zone errors continue to persist. This seems to happen anywhere from once a week, to every day. Performing a hard reset isn't something I want to nor should have to keep doing to correct the issue every time it happens. Please let me know if there is anything else I can do to stop this from happening. I am getting very close to returning this router and exchanging it for a different brand. Thanks.

[fairfacts]

I am on this one: 3.0.0.6.102_37506-g3caded7_1090-gca005_BB0B

had to download from here ASUS RT-BE92U｜WiFi 7｜ASUS USA myself unpack and apply it (the auto update didnt pick it up).

Solved thermal issues.  Much easier to read logs now and I have several days of logs. Still seeing some issues :

These fairly regularly: Mar 6 14:46:04 kernel: WLC_SCB_DEAUTHORIZE error (-30) and slightly different:

ar 5 06:22:14 kernel: WLC_SCB_DEAUTHORIZE error (-30)
Mar 5 06:22:14 kernel: WLC_SCB_DEAUTHENTICATE_FOR_REASON err -30

which dont seem tied to a specific MAC address like these: Mar 6 14:24:07 wlceventd: wlceventd_proc_event(706): wl1.2: ReAssoc XX:XX:XX:XX:XX:XX, status: Successful (0), rssi:-71

Mar 6 14:46:04 wlceventd: wlceventd_proc_event(656): wl0.2: Deauth_ind XX:XX:XX:XX:XX:XX, status: 0, reason: Disassociated due to inactivity (4), rssi:-60

Which I believe are normal

My uptime is only 1 day 16 hrs so I think  reboot happened when I wasnt looking and once again the router lost NTP (log has entries for dec 31 19:00:34 and I cleared the log after the patch upgrade so something happened to bounce the device:

Mar 4 22:12:09 wlceventd: wlceventd_proc_event(733): wl1.2: Assoc XX:XX:XX:XX:XX:XX, status: Successful (0), rssi:-71
Dec 31 19:00:34 kernel: klogd started: BusyBox v1.24.1 (2025-02-25 15:09:35 CST)
Dec 31 19:00:34 kernel: Linux version 4.19.294 (root@asus) (gcc version 10.3.0 (Buildroot 2021.02.4)) #1 SMP PREEMPT Tue Feb 25 15:13:59 CST 2025
Dec 31 19:00:34 kernel: ARM_SMCCC_ARCH_WORKAROUND_1 missing from firmware
Dec 31 19:00:34 kernel: Kernel command line: coherent_pool=4M cpuidle_sysfs_switch pci=pcie_bus_safe console=ttyAMA0,115200 rootwait rng_core.default_quality=1024 mtdparts=brcmnand.0:2097152(loader),265289728@2097152(image) root=/dev/ubiblock0_6 ubi.mtd=image ubi.block=0,6 rootfstype=squashfs
Dec 31 19:00:34 kernel: bootloader version U-Boot2019.07(02/25/2025-15:11:46+0800)50404p3@523100
Dec 31 19:00:34 kernel: BoardId [RT-BE92U], NVRAM_ULBOARDSTUFFOPTION=0
Dec 31 19:00:34 kernel: size of sk_buff 576
Dec 31 19:00:34 kernel: offset of cb in sk_buff 400

etc and continuing until NTP is reconnected and the time resets correctly

and this error :

Mar 6 11:40:06 acsd: wl1 received event: tx pkt delay suddently jump
Mar 6 12:20:52 acsd: wl1 received event: tx pkt delay suddently jump

[senyk92]

The device has been on 37506 for around 5 days and 15 hours ( I was around for about 24 hours of that for actual use ), I did a hard reset via WPS after installing the update and i did not turn on MLO. The device has been stable, meaning before i had constant cpu maxing out and reboot issues, that now has resolved. This is all without MLO turned on in default config post hard reset, all 3 bands are being selected by the device. 

I will be testing turning on MLO here in a day or two, setting up more specific bands and ensuring wifi 7 is enabled, but this is way better than prior to 37506, atleast at base value without fully taking advantage of the device.

Whats interesting is i do see errors in the logs related to MLO, even though it is not turned on, logs below


Mar 9 03:00:23 watchdog: restart_firewall due DST time changed(0->1)
Mar 9 03:00:23 rc_service: watchdog 4165:notify_rc restart_firewall
Mar 9 03:00:23 rc_service: watchdog 4165:notify_rc restart_wan
Mar 9 03:00:23 rc_service: waitting "restart_firewall"(last_rc:restart_autowan) via watchdog ...
Mar 9 03:00:24 miniupnpd[27342]: shutting down MiniUPnPd
Mar 9 07:00:25 rc_service: waitting "restart_wan"(last_rc:restart_wan) via watchdog ...
Mar 9 03:00:29 miniupnpd: it is advised to use network interface name instead of 192.168.50.1/255.255.255.0
Mar 9 03:00:29 miniupnpd[7475]: HTTP listening on port 41665
Mar 9 03:00:29 miniupnpd[7475]: Listening for NAT-PMP/PCP traffic on port 5351
Mar 9 03:00:30 udhcpc_wan[7484]: hnd_get_phy_status: Temporarily Router cannot get the PHY() status...
Mar 9 03:00:30 wan: finish adding multi routes
Mar 9 03:00:31 miniupnpd[7475]: shutting down MiniUPnPd
Mar 9 03:00:31 miniupnpd: it is advised to use network interface name instead of 192.168.50.1/255.255.255.0
Mar 9 03:00:31 miniupnpd[7744]: HTTP listening on port 34385
Mar 9 03:00:31 miniupnpd[7744]: Listening for NAT-PMP/PCP traffic on port 5351
Mar 9 03:00:31 kernel: Crossbow TCP Pure ACK Enabled
Mar 9 03:00:31 rc_service: udhcpc_wan 7484:notify_rc stop_samba
Mar 9 03:00:31 Samba Server: smb daemon is stopped
Mar 9 03:00:32 rc_service: udhcpc_wan 7484:notify_rc start_samba
Mar 9 07:00:32 WAN(0) Connection: WAN was restored.
Mar 9 03:00:33 wan_up: Restart DDNS
Mar 9 03:00:33 dhcp client: bound (Sanitized by senyk92 ) for 83117 seconds.
Mar 9 03:31:24 WATCHDOG: [FAUPGRADE][auto_firmware_check:(8677)]do webs_update
Mar 9 03:31:35 WATCHDOG: [FAUPGRADE][auto_firmware_check:(8695)]retrieve firmware information
Mar 9 03:31:35 WATCHDOG: [FAUPGRADE][auto_firmware_check:(8710)]fimrware update check first time
Mar 9 03:31:35 WATCHDOG: [FAUPGRADE][auto_firmware_check:(8741)]no need to upgrade firmware
Mar 9 12:15:31 kernel: PKT:
Mar 9 12:15:31 kernal packets sanitized by senyk92
Mar 9 16:00:00 wlceventd: wlceventd_proc_event(733): wl1.1: Assoc(Sanitized by senyk92 ), status: Successful (0), rssi:-66
Mar 9 16:00:00 wlceventd: wlceventd_proc_event(733): wl1.1: Assoc(Sanitized by senyk92 ), status: Successful (0), rssi:-63
Mar 9 16:00:06 wlceventd: wlceventd_proc_event(733): wl1.1: Assoc(Sanitized by senyk92 ), status: Successful (0), rssi:-70
Mar 9 16:00:17 wlceventd: wlceventd_proc_event(706): wl2.1: ReAssoc(Sanitized by senyk92 ), status: Successful (0), rssi:-82
Mar 9 16:00:22 kernel: ^[[32;1m=== MLO ERROR [wlc_ap_process_assocreq] Assoc processingfailure forMar 9 03:00:23 watchdog: restart_firewall due DST time changed(0->1)
Mar 9 03:00:23 rc_service: watchdog 4165:notify_rc restart_firewall
Mar 9 03:00:23 rc_service: watchdog 4165:notify_rc restart_wan
Mar 9 03:00:23 rc_service: waitting "restart_firewall"(last_rc:restart_autowan) via watchdog ...
Mar 9 03:00:24 miniupnpd[27342]: shutting down MiniUPnPd
Mar 9 07:00:25 rc_service: waitting "restart_wan"(last_rc:restart_wan) via watchdog ...
Mar 9 03:00:29 miniupnpd: it is advised to use network interface name instead of 192.168.50.1/255.255.255.0
Mar 9 03:00:29 miniupnpd[7475]: HTTP listening on port 41665
Mar 9 03:00:29 miniupnpd[7475]: Listening for NAT-PMP/PCP traffic on port 5351
Mar 9 03:00:30 udhcpc_wan[7484]: hnd_get_phy_status: Temporarily Router cannot get the PHY() status...
Mar 9 03:00:30 wan: finish adding multi routes
Mar 9 03:00:31 miniupnpd[7475]: shutting down MiniUPnPd
Mar 9 03:00:31 miniupnpd: it is advised to use network interface name instead of 192.168.50.1/255.255.255.0
Mar 9 03:00:31 miniupnpd[7744]: HTTP listening on port 34385
Mar 9 03:00:31 miniupnpd[7744]: Listening for NAT-PMP/PCP traffic on port 5351
Mar 9 03:00:31 kernel: Crossbow TCP Pure ACK Enabled
Mar 9 03:00:31 rc_service: udhcpc_wan 7484:notify_rc stop_samba
Mar 9 03:00:31 Samba Server: smb daemon is stopped
Mar 9 03:00:32 rc_service: udhcpc_wan 7484:notify_rc start_samba
Mar 9 07:00:32 WAN(0) Connection: WAN was restored.
Mar 9 03:00:33 wan_up: Restart DDNS
Mar 9 03:00:33 dhcp client: bound (Sanitized by senyk92 ) for 83117 seconds.
Mar 9 03:31:24 WATCHDOG: [FAUPGRADE][auto_firmware_check:(8677)]do webs_update
Mar 9 03:31:35 WATCHDOG: [FAUPGRADE][auto_firmware_check:(8695)]retrieve firmware information
Mar 9 03:31:35 WATCHDOG: [FAUPGRADE][auto_firmware_check:(8710)]fimrware update check first time
Mar 9 03:31:35 WATCHDOG: [FAUPGRADE][auto_firmware_check:(8741)]no need to upgrade firmware
Mar 9 12:15:31 kernel: PKT:
Mar 9 12:15:31 kernal packets sanitized by senyk92
Mar 9 16:00:00 wlceventd: wlceventd_proc_event(733): wl1.1: Assoc(Sanitized by senyk92 ), status: Successful (0), rssi:-66
Mar 9 16:00:00 wlceventd: wlceventd_proc_event(733): wl1.1: Assoc(Sanitized by senyk92 ), status: Successful (0), rssi:-63
Mar 9 16:00:06 wlceventd: wlceventd_proc_event(733): wl1.1: Assoc(Sanitized by senyk92 ), status: Successful (0), rssi:-70
Mar 9 16:00:17 wlceventd: wlceventd_proc_event(706): wl2.1: ReAssoc(Sanitized by senyk92 ), status: Successful (0), rssi:-82
Mar 9 16:00:22 kernel: ^[[32;1m=== MLO ERROR [wlc_ap_process_assocreq] Assoc processingfailure for 12:ff:3a:6b:47:ca on wl1 status 30 ===^[[0m
Mar 9 16:00:22 wlceventd: wlceventd_proc_event(656): wl1.1: Deauth_ind(Sanitized by senyk92 ), status: 0, reason: Station requesting (re)association is not authenticated with responding station (9), rssi:-75
Mar 9 16:00:22 wlceventd: wlceventd_proc_event(673): wl1.1: Disassoc(Sanitized by senyk92 ), status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:-75
Mar 9 16:00:24 wlceventd: wlceventd_proc_event(696): wl1.1: Auth(Sanitized by senyk92 ), status: Successful (0), rssi:0
Mar 9 16:00:24 wlceventd: wlceventd_proc_event(706): wl1.1: ReAssoc(Sanitized by senyk92 ), status: Successful (0), rssi:-73
Mar 9 16:01:14 wlceventd: wlceventd_proc_event(656): wl2.1: Deauth_ind(Sanitized by senyk92 ), status: 0, reason: Disassociated due to inactivity (4), rssi:-84
Mar 9 16:01:37 wlceventd: wlceventd_proc_event(696): wl2.1: Auth(Sanitized by senyk92 ), status: Successful (0), rssi:0
Mar 9 16:01:37 wlceventd: wlceventd_proc_event(706): wl2.1: ReAssoc(Sanitized by senyk92 ), status: Successful (0), rssi:-66
Mar 9 16:02:14 wlceventd: wlceventd_proc_event(656): wl1.1: Deauth_ind(Sanitized by senyk92 ), status: 0, reason: Disassociated due to inactivity (4), rssi:-55
Mar 9 16:07:38 rc_service: httpd 4160:notify_rc start_webs_update
Mar 9 16:12:50 wlceventd: wlceventd_proc_event(733): wl1.1: Assoc(Sanitized by senyk92 ), status: Successful (0), rssi:-60
Mar 9 16:12:51 wlceventd: wlceventd_proc_event(673): wl1.1: Disassoc(Sanitized by senyk92 ), status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Mar 9 16:12:51 wlceventd: wlceventd_proc_event(656): wl1.1: Deauth_ind(Sanitized by senyk92 ), status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:0
Mar 9 16:12:55 wlceventd: wlceventd_proc_event(696): wl1.1: Auth(Sanitized by senyk92 ), status: Successful (0), rssi:0
Mar 9 16:12:55 wlceventd: wlceventd_proc_event(733): wl1.1: Assoc(Sanitized by senyk92 ), status: Successful (0), rssi:-60
Mar 9 16:13:33 wlceventd: wlceventd_proc_event(696): wl1.1: Auth(Sanitized by senyk92 ), status: Successful (0), rssi:0
Mar 9 16:13:33 wlceventd: wlceventd_proc_event(706): wl1.1: ReAssoc(Sanitized by senyk92 ), status: Successful (0), rssi:-67
Mar 9 16:13:59 wlceventd: wlceventd_proc_event(656): wl2.1: Deauth_ind(Sanitized by senyk92 ), status: 0, reason: Disassociated due to inactivity (4), rssi:-82
Mar 9 16:16:37 wlceventd: wlceventd_proc_event(706): wl2.1: ReAssoc(Sanitized by senyk92 ) status: Successful (0), rssi:-77
Mar 9 16:17:07 wlceventd: wlceventd_proc_event(656): wl1.1: Deauth_ind(Sanitized by senyk92 ), status: 0, reason: Disassociated due to inactivity (4), rssi:-60
Mar 9 16:17:07 kernel: WLC_SCB_DEAUTHORIZE error (-30)
on wl1 status 30 ===^[[0m
Mar 9 16:00:22 wlceventd: wlceventd_proc_event(656): wl1.1: Deauth_ind(Sanitized by senyk92 ), status: 0, reason: Station requesting (re)association is not authenticated with responding station (9), rssi:-75
Mar 9 16:00:22 wlceventd: wlceventd_proc_event(673): wl1.1: Disassoc(Sanitized by senyk92 ), status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:-75
Mar 9 16:00:24 wlceventd: wlceventd_proc_event(696): wl1.1: Auth(Sanitized by senyk92 ), status: Successful (0), rssi:0
Mar 9 16:00:24 wlceventd: wlceventd_proc_event(706): wl1.1: ReAssoc(Sanitized by senyk92 ), status: Successful (0), rssi:-73
Mar 9 16:01:14 wlceventd: wlceventd_proc_event(656): wl2.1: Deauth_ind(Sanitized by senyk92 ), status: 0, reason: Disassociated due to inactivity (4), rssi:-84
Mar 9 16:01:37 wlceventd: wlceventd_proc_event(696): wl2.1: Auth(Sanitized by senyk92 ), status: Successful (0), rssi:0
Mar 9 16:01:37 wlceventd: wlceventd_proc_event(706): wl2.1: ReAssoc(Sanitized by senyk92 ), status: Successful (0), rssi:-66
Mar 9 16:02:14 wlceventd: wlceventd_proc_event(656): wl1.1: Deauth_ind(Sanitized by senyk92 ), status: 0, reason: Disassociated due to inactivity (4), rssi:-55
Mar 9 16:07:38 rc_service: httpd 4160:notify_rc start_webs_update
Mar 9 16:12:50 wlceventd: wlceventd_proc_event(733): wl1.1: Assoc(Sanitized by senyk92 ), status: Successful (0), rssi:-60
Mar 9 16:12:51 wlceventd: wlceventd_proc_event(673): wl1.1: Disassoc(Sanitized by senyk92 ), status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Mar 9 16:12:51 wlceventd: wlceventd_proc_event(656): wl1.1: Deauth_ind(Sanitized by senyk92 ), status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:0
Mar 9 16:12:55 wlceventd: wlceventd_proc_event(696): wl1.1: Auth(Sanitized by senyk92 ), status: Successful (0), rssi:0
Mar 9 16:12:55 wlceventd: wlceventd_proc_event(733): wl1.1: Assoc(Sanitized by senyk92 ), status: Successful (0), rssi:-60
Mar 9 16:13:33 wlceventd: wlceventd_proc_event(696): wl1.1: Auth(Sanitized by senyk92 ), status: Successful (0), rssi:0
Mar 9 16:13:33 wlceventd: wlceventd_proc_event(706): wl1.1: ReAssoc(Sanitized by senyk92 ), status: Successful (0), rssi:-67
Mar 9 16:13:59 wlceventd: wlceventd_proc_event(656): wl2.1: Deauth_ind(Sanitized by senyk92 ), status: 0, reason: Disassociated due to inactivity (4), rssi:-82
Mar 9 16:16:37 wlceventd: wlceventd_proc_event(706): wl2.1: ReAssoc(Sanitized by senyk92 ) status: Successful (0), rssi:-77
Mar 9 16:17:07 wlceventd: wlceventd_proc_event(656): wl1.1: Deauth_ind(Sanitized by senyk92 ), status: 0, reason: Disassociated due to inactivity (4), rssi:-60
Mar 9 16:17:07 kernel: WLC_SCB_DEAUTHORIZE error (-30)