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.

[Lid]

@cowhow I had to remove my IoT and guest network just to get some stability. It shouldn't be this way. I have applied their beta firmware as a last resort.  I do hope it doesn't brick the router entirely as their own testing seems entirely lacking.

[cowhow]

@Lid The funny thing for me is CPU usage has changed.  Core 4 was all over the place but it's settled down and core 2 is the busy one.  I wished we had a way of filtering logs because all those bogus thermal entries make it difficult to read logs for relevant info.

Did the beta firmware improve things?  I would suspect I would need to contact ASUS to get my hands on it.

[DesiBuckeye]

I'm having the same issues.  Had completely unstable network after setting up router (with accompanying firmware upgrade). Came to this and other posts. Did the hard reset and set it up again, and the network is "less unstable", but still with issues.  I still have the log full of these issues below (more than thermal now) and also a "wave pattern" of speed/bandwidth, Core 3 bouncing close to 100% and RAM at about 75%

Errors:

Jan 23 13:44:18 bsd: bsd: Skip STA:7c:21:4a:58:91:ca reject BSSID
Jan 23 13:44:20 kernel: read_bpcm_reg_direct_keyhole: Wait for completion failed, devAddr 0x3, offset 24, idx 2
Jan 23 13:44:20 kernel: thermal thermal_zone0: Failed to get RAIL 0 temperature, ret=256
Jan 23 13:44:20 kernel: thermal thermal_zone0: Failed to get temperature, ret=-1
Jan 23 13:44:20 kernel: thermal thermal_zone0: failed to read out thermal zone (-1)

On the graph, the blue line is download speed, orange line is upload speed. They're on different axes (as noted on the left)

[Lid]

Since applying the beta firmware I have a whole host of new log messages and seem to be experiencing more wifi drops.  After a previous reset I was not seeing the level or thermal logs that others are experiencing and the CPU load seems to have calmed down.  I however attributed the bouncing cores to my USB HDD. When I remove the drive it improved.    ASUS placed the beta on a share so I can presumably allow others to test it? Perhaps best if you direct message me and I'll share their download link.

[DesiBuckeye]

his is what I see after a reboot. The thermal errors haven't come up yet, but there are all kinds of new errors.

Jan 24 11:22:47 kernel: WLC_SCB_DEAUTHORIZE error (-30)
Jan 24 11:22:47 kernel: WLC_SCB_DEAUTHENTICATE_FOR_REASON err -30
Jan 24 11:22:47 wlceventd: wlceventd_proc_event(656): wl0.1: Deauth_ind C8:FF:77:E9:0A:A8, status: 0, reason: 4-way handshake timeout (f), rssi:0
Jan 24 11:22:47 wlceventd: wlceventd_proc_event(656): wl0.1: Deauth_ind C8:FF:77:E9:0A:A8, status: 0, reason: Unspecified reason (1), rssi:0
Jan 24 11:22:47 wlceventd: wlceventd_proc_event(673): wl0.1: Disassoc C8:FF:77:E9:0A:A8, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Jan 24 11:23:07 wlceventd: wlceventd_proc_event(696): wl1.1: Auth 94:D0:0D:5F:49:21, status: Successful (0), rssi:0
Jan 24 11:23:07 wlceventd: wlceventd_proc_event(733): wl1.1: Assoc 94:D0:0D:5F:49:21, status: Successful (0), rssi:-52
Jan 24 11:23:11 kernel: WLC_SCB_DEAUTHORIZE error (-30)
Jan 24 11:23:11 wlceventd: wlceventd_proc_event(656): wl1.1: Deauth_ind 94:D0:0D:5F:49:21, status: 0, reason: 4-way handshake timeout (f), rssi:-52
Jan 24 11:23:11 kernel: WLC_SCB_DEAUTHENTICATE_FOR_REASON err -30
Jan 24 11:23:11 kernel: WLC_SCB_DEAUTHORIZE error (-30)
Jan 24 11:23:11 wlceventd: wlceventd_proc_event(656): wl1.1: Deauth_ind 94:D0:0D:5F:49:21, status: 0, reason: Unspecified reason (1), rssi:-53
Jan 24 11:23:11 wlceventd: wlceventd_proc_event(696): wl1.1: Auth 94:D0:0D:5F:49:21, status: Successful (0), rssi:-53
Jan 24 11:23:11 wlceventd: wlceventd_proc_event(733): wl1.1: Assoc 94:D0:0D:5F:49:21, status: Successful (0), rssi:-53
Jan 24 11:23:13 wlceventd: wlceventd_proc_event(673): wl1.1: Disassoc 94:D0:0D:5F:49:21, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:0
Jan 24 11:23:13 wlceventd: wlceventd_proc_event(656): wl1.1: Deauth_ind 94:D0:0D:5F:49:21, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:0
Jan 24 11:23:14 wlceventd: wlceventd_proc_event(696): wl1.1: Auth 94:D0:0D:5F:49:21, status: Successful (0), rssi:0
Jan 24 11:23:15 wlceventd: wlceventd_proc_event(733): wl1.1: Assoc 94:D0:0D:5F:49:21, status: Successful (0), rssi:-53
Jan 24 11:23:19 kernel: WLC_SCB_DEAUTHORIZE error (-30)
Jan 24 11:23:19 kernel: WLC_SCB_DEAUTHENTICATE_FOR_REASON err -30