This widget could not be displayed.
This widget could not be displayed.
cancel
Showing results for 
Search instead for 
Did you mean: 

RT-BE92U Persistent Thermal Zone Faults

RicoSuave
Star III

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.

180 REPLIES 180

RicoSuave
Star III

Update: I ran the beta firmware version (9.0.0.6.102_37803) for about a week now without any real change. Still had random drops in speed and connectivity that would require a manual reboot. Saw that the new firmware version was released (3.0.0.6.102_37500),  so I uploaded that yesterday. As of this morning, thermal errors persist, except this time it's every second as opposed to every 3 seconds. This is going to be incredibly frustrating to troubleshoot whenever I have another issue cause the log is now going to be saturated with nuisance errors that I'm going to have to filter through. The router has been up for about 20 hours since updating the firmware. I'm going to continue to monitor and stress test the network for a few days before I send another report and message to @Aureliannn_ASUS . So far... not pleased.

fairfacts
Star II

I am on the latest too.  Turned the radio for 6ghz off on the wifi / professional tab - no change. Rebooted the router - 30 minutes of no thermal errors - but now the thermals are back - so have reset the radio to 'on'. No change

kjm
Star II

Some good news

Thank you for your recent contact to our CEO's office!
Good afternoon, I hope you are well.

I have heard back from our team about the thermal messages you have been getting. The good news is it has been confirmed that the thermal error log indicates a thermal information read error and not

an abnormal with the thermal module itself.  You can feel safe to use the router, and we will be fixing this issue in a future update release. We do appreciate your feedback as it does help our engineers

to pinpoint potential issues so that they can be addressed. If you do have further concerns, please let us know and we'd be happy to assist you. Take care!

Please make note of your case number for your future reference: N2502017157-0005

I am not having reset issues and turning off 6Ghz has stopped the messages for me.  Hopefully the fix will address that as well.  No timing and when.

serunis
Visitor

hey guys, I have suffered the same. but I found the way to not make CPU to stuck 99% usage.

I set the seperate SSID to each frequency, and I set to use 6GHz as backhaul only (I have two BE92U with wireless AI mesh).

I set all device to use 2.4GHz or 5GHz, and no 6GHz. with this setting, CPU usage does not go to 99% even if thermal error occured. which I can get more stable connection than before.

There is something wrong with 6GHz I think, and MLO is the kill switch, it makes my router go 99% cpu usage instantly

senyk92
Star I

adding this in as a edit to provide value to the community: In my testing i found that the version before 37500 is more stable and didn't have as many reboots occur, once i got the firmware to 37500 alot more reboots occurred, i believe this is due to the cpu.

what bugs me is Firmware version 3.0.0.6.102_37500 literally claims to fix the cpu issue in the description, yet is still occurs - how does one find faith that any of this will be fixed anytime soon?

senyk92_0-1740293844032.png