Trying to fix 'thermal thermal_zone2: failed to read out thermal zone (-61)'

jahf

New Member
Apr 11, 2022
5
1
3
I'm fine tuning Proxmox on my home system and have my dmesg errors down to 2 things (the other being the intel ibt-20-1-3 driver not existing and as I'm not using Bluetooth on the host I'm not fixing that).

The error in question:

'[ 13.756471] thermal thermal_zone2: failed to read out thermal zone (-61)'

I'm not super concerned, I would just like to get this done if possible.

Relevant hardware in use:
  • Gigabyte X570 Master rev. 1 BIOS F36b / AMD 5950X / 4x Kingston KSM32ED8/32ME
  • Nvidia RTX 3080TI (model: Founder's Edition)
  • Nvidia GTX 1060 6GB (model: Gigabyte Mini-ITX OC)
  • LSISAS2008 (HBA)

I don't think I have any other components that are likely to have thermal monitoring abilities. I'm assuming the motherboard is where this would be pulling from but listing the others just in case.

`dmesg | grep thermal` reports:

[ 0.761334] thermal_sys: Registered thermal governor 'fair_share'
[ 0.761334] thermal_sys: Registered thermal governor 'bang_bang'
[ 0.761334] thermal_sys: Registered thermal governor 'step_wise'
[ 0.761334] thermal_sys: Registered thermal governor 'user_space'
[ 0.761334] thermal_sys: Registered thermal governor 'power_allocator'
[ 2.410718] thermal LNXTHERM:00: registered as thermal_zone0
[ 2.411190] ACPI: thermal: Thermal Zone [PCT0] (17 C)
[ 2.412190] thermal LNXTHERM:01: registered as thermal_zone1
[ 2.412655] ACPI: thermal: Thermal Zone [UAD0] (17 C)
[ 2.787904] thermal cooling_device18: hash matches
[ 13.756471] thermal thermal_zone2: failed to read out thermal zone (-61)

So zone0 and zone1 are loading fine. I'd be lying if I said I knew which devices each zone is reading.
 
I suspect you won't really be able to get rid of this error, because it might result from a device not being loaded yet, similar to this bug report.

You should be able to tell exactly which device is at fault here by issuing grep . /sys/class/thermal/thermal_zone2/type
The message will most likely not hurt the system in any way, though you might be able to find a solution somehow. If the wifi driver is causing the problem, however, then you are probably out of luck, as the discussion about this problem is still ongoing (see linked report).