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.

108 REPLIES 108

fairfacts
Star I

I don’t think it’s hardware. Maybe wrong but I don’t believe it’s running hot and the fact it moves between cores makes me believe it’s config or os throwing issues. 

cowhow
Star II

Using my hand as a gauge my router isn't hot.  Just for grins I put a small fan behind it which made no difference.  I don't think it's hardware either unless multiple vendors supplied chips to Asus.  There are others who are having no problems at all with this router, or at least by their reviews and comments they aren't.  At this point there's not much else to do but sit and wait for a resolution from Asus or replace the router which is looking more favorable by the day.

My gut says 90pct of users set it up with basic defaults through the gui and never look at the logs or spot performance blips.  Most of the commenters seem from either more advanced users or more complex networks and maybe the intersection of both. 
I went to the logs because I wanted to see what was going on with occasionally having network blips - which I still suspect is actually my old switches.  Plus an outage from my isp where the Verizon end point was flapping.  Power cycle of its power supply resolved it after I traced upstream -  but I started with the logs.  Some users will also see the thermal errors, see it’s not hot and assume it’s all ok and not log it. 

RicoSuave
Star II

Update since the last time I posted. No change as of yet. Router is still having random drops in speed and I'm having to perform hard a reset almost on a daily basis. Logs still show continuous thermal faults and single core CPU spikes. Haven't heard back from ASUS since the last time I contacted them. I'm extremely disappointed from the lack of transparency from ASUS. I understand their mod teams on this forum can only do so much, but I find it unacceptable that ASUS hasn't put out an official statement regarding the plethora of issues this router seems to have. Clearly this isn't a hardware issue (or maybe it is, I wouldn't know cause again... ASUS refuses to communicate), but I find it most surprising that a team of network engineers can't seem to fix an issue that many here have provided feedback and data on. ASUS, do better. I expect a fix soon. @Aureliannn_ASUS