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.

[Chobra]

Update: spoke too soon, core issue is back even with wifi 7 disabled

[def2]

Wanna chime in as well, Just got the BE92U a week ago and have been having the same issue One core with extremely high usage, bouncing every 2-3 seconds and the thermal zone faults. This is despite minimal network usage and only 3 devices connected

Jan 12 22:27:17 kernel: read_bpcm_reg_direct_keyhole: Wait for completion failed, devAddr 0x3, offset 24, idx 2
Jan 12 22:27:17 kernel: thermal thermal_zone0: Failed to get RAIL 0 temperature, ret=256
Jan 12 22:27:17 kernel: thermal thermal_zone0: Failed to get temperature, ret=-1
Jan 12 22:27:17 kernel: thermal thermal_zone0: failed to read out thermal zone (-1)
Jan 12 22:27:20 kernel: read_bpcm_reg_direct_keyhole: Wait for completion failed, devAddr 0x3, offset 24, idx 2
Jan 12 22:27:20 kernel: thermal thermal_zone0: Failed to get RAIL 0 temperature, ret=256
Jan 12 22:27:20 kernel: thermal thermal_zone0: Failed to get temperature, ret=-1
Jan 12 22:27:20 kernel: thermal thermal_zone0: failed to read out thermal zone (-1)

[MongoNC]

I bought this router primarily because it had 2.5G ports as I plan to run a wire to a switch where my TV and PS5 are when I moved into my new house just before Christmas (I prefer wired over wireless as much as possible - I'm old school like that). I've had nothing but problems with this thing. Same issues as the OP and everyone else in this thread with one CPU spiking and random reboots despite nightly planned reboots when not in use. I've tried everything that everyone else has. It was extremely frustrating to have to endure this so I gave up.

The best solution I could think of was, to stay with ASUS (because I'm not a fan of Netgear) was to buy a RT-BE86U for stability which seems to be operating fine. But now I have a $250 brick. Maybe it'll come in handy if the stability issues are fixed at which I can always use it as a mesh repeater. But as it stands, it's best used as a switch without wireless. In other words, worthless.

Very disappointed.

[Aureliannn_ASUS]

Hi all,

Regarding the "Thermal Zone Faults" error message in your router logs, our team currently suspects that it is due to abnormal CPU usage or temperature reading rather than the router being under high-stress conditions. 

Our initial assessment indicates that the cooling system is functioning correctly, and this issue does not affect the router's normal operation, so please feel assured.

We will need some time to discuss and address the CPU usage issue with the manufacturer. 

A firmware update will be released to correct this in the future. Please be informed and thank you for your understanding. 

If you encounter any anomalies during use, please provide a detailed description of the issue so our team can investigate further.

Thank you very much for your understanding and cooperation.

[changkai]

I'm pretty sure it should be quite easy for your support team to reproduce the issue as it has been observed by so many users with pretty high frequency (more than once a day). What you probably need to do is to include more logs as the current logs don't seem to provide sufficient information to understand what triggered the reboots. Please do it quickly as we're all running out of patience with this product and ASUS.