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 II

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.

75 REPLIES 75

Chobra
Star II

As a work around until the issue has been resolved via firmware update do the below.  No more thermal fault and core 50-100% for 3 days now and no scheduled auto reboot needed.  Also reduced deauth with reason = unspecified.

Main culprit:

  • Disable MLO
  • Disable wifi 7

Secondary culprit:

  • Separate each band (2.4, 5, 6GHz) with its own SSID

Optional:

  • Legacy 2.4ghz devices, use WPA/WPA2 auth rather than WPA2 only
  • Disable the following on all bands (2.4, 5, 6GHz)
    • WMM APSD
    • AMPDU 
    • MIMO
    • MU-MIMO
    • OFDMA
    • Explicit beamforming
    • Universal beamforming

Deleted

cowhow
Star II

Just for the record I just experienced my first random reboot.  And I hate to keep harping on this but these thermal errors make reading the logs for events such as this almost useless.

I know Asus can't just throw out a new firmware but some updates would help.  My real concern is this is hardware related in which case I'd be screwed.  That is unless Asus wanted to ship me a new router to Costa Rica.  So, a call to Asus tech support tomorrow morning.  This router has been out long enough not to be having these problems, problems that shouldn't have appeared at all.

DesiBuckeye
Star II

I tried to reboot overnight (to see if the deauth issues would go away) and the router was very erratic in the morning (incredibly low speeds of less than 1 Mbps, even when hardwired, when the WAN speed was close to 1 Gbps). I had to hard reset. Speed came back, but I still have all the errors (deauth and thermal). I'm going to exchange it for another unit to see if another unit does any better, else I'll switch routers

The wife and I lived in Fort Worth for 20 something years and just relocated back to Costa Rica.  If I were still in Fort Worth I'd do the same as you.  As critical as these errors are we need a fix and pronto.  I was just reading a Reddit where a guy installed build 37521 and said the log errors stopped.  He used the feedback page to request access.