Thermel zone failure message on boot (NanoPi NEO2)

SamuraiJapon · May 6

I am getting a thermal zone failure message during boot, which has always happened with kernels after 6.6, at least as far as I know.

Is this error actually harmful?

HardWare:NanoPi NEO2

Armbian Version:

Packages: Debian stable (bookworm) v25.2.3 for NanoPi Neo 2 running Armbian Linux 6.12.20-current-sunxi64
Support: DIY (community maintained)

Kernel: Linux nanopineo2 6.12.20-current-sunxi64 #1 SMP Sat Mar 22 19:54:28 UTC 2025 aarch64 GNU/Linux

dmesg output

[ 7.018086] core: _opp_supported_by_regulators: OPP minuV: 1320000 maxuV: 1320000, not supported by regulator
[ 7.018125] cpu cpu0: _opp_add: OPP not supported by regulators (1104000000)
[ 7.018245] core: _opp_supported_by_regulators: OPP minuV: 1320000 maxuV: 1320000, not supported by regulator
[ 7.018258] cpu cpu0: _opp_add: OPP not supported by regulators (1200000000)
[ 7.018413] core: _opp_supported_by_regulators: OPP minuV: 1340000 maxuV: 1340000, not supported by regulator
[ 7.018426] cpu cpu0: _opp_add: OPP not supported by regulators (1296000000)
[ 7.018552] core: _opp_supported_by_regulators: OPP minuV: 1400000 maxuV: 1400000, not supported by regulator
[ 7.018564] cpu cpu0: _opp_add: OPP not supported by regulators (1368000000)
[ 7.019699] thermal thermal_zone0: binding cdev cpufreq-cpu0 to trip 3 failed: -22
[ 7.019785] thermal thermal_zone0: binding cdev cpufreq-cpu0 to trip 4 failed: -22

dmesg.txt

Edited May 6 by SamuraiJapon

laibsch · May 13

On 5/6/2025 at 6:53 PM, SamuraiJapon said:

Is this error actually harmful?

You should of course monitor the temperatures now to see if the board becomes abnormally hot (use your hand or the programs sensors or btop, for example). That being said, a quick web search suggests to me that you are simply seeing a software problem AKA bug. I suggest you open a bug ticket on the Armbian bug tracker and patiently wait for the board maintainer to have a look into the issue.

https://www.armbian.com/nanopi-neo-2/ lists https://github.com/spendist as the maintainer for your board. Maybe you can send an e-mail?

sources:

SamuraiJapon · May 13

laibsch, thanks for your answer.
I tried several kernels from the 6.x.y series on Armbian, but the same error occurred in all of them.
I think this error did not occur with the 4.14 series kernel downloaded from the board manufacturer's official website.
However, when I built and started the 4.14.111+ kernel downloaded from the board manufacturer's github, the following error occurred.

dmesg (Friendlycore linux kernel 4.14.111+)
[ 2.243976] thermal thermal_zone0: failed to read out thermal zone (-16)

It seems that there has been an error in the thermal driver (dts) of the allwinner H5 SoC for quite some time.
I have already uninstalled Armbian and cannot take logs, so I would like to submit a bug report once I install Armbian again and can take logs.

Edited May 13 by SamuraiJapon

Jean-Marc · Sunday at 08:12 PM

Dear maintainers,

First thanks for your work on this SBC...

On recent 6.12.35-current-sunxi64, i have the same issue...

root@hn-nanopineo2-285:~# uname -a
Linux hn-nanopineo2-285 6.12.35-current-sunxi64 #5 SMP Fri Jun 27 10:11:46 UTC 2025 aarch64 GNU/Linux
root@hn-nanopineo2-285:~# cat /etc/debian_version
12.11

root@hn-nanopineo2-285:~# dpkg -l |grep armbian
ii armbian-bsp-cli-nanopineo2-current 25.8.1 arm64 Armbian CLI BSP for board 'nanopineo2' branch 'current'
ii armbian-firmware 25.8.1 all Armbian - Linux firmware

root@hn-nanopineo2-285:~# dmesg |head
[ 0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd034]
[ 0.000000] Linux version 6.12.35-current-sunxi64 (build@armbian) (aarch64-linux-gnu-gcc (Ubuntu 13.3.0-6ubuntu2~24.04) 13.3.0, GNU ld (
GNU Binutils for Ubuntu) 2.42) #5 SMP Fri Jun 27 10:11:46 UTC 2025
[ 0.000000] KASLR disabled due to lack of seed
[ 0.000000] Machine model: FriendlyARM NanoPi NEO 2
[ 0.000000] OF: reserved mem: Reserved memory: No reserved-memory node in the DT
[ 0.000000] NUMA: Faking a node at [mem 0x0000000040000000-0x000000005fffffff]
[ 0.000000] NODE_DATA(0) allocated [mem 0x5fed9540-0x5fedb5ff]
[ 0.000000] Zone ranges:
[ 0.000000] DMA [mem 0x0000000040000000-0x000000005fffffff]

..... and later in dmesg ...

[ 11.751234] core: _opp_supported_by_regulators: OPP minuV: 1200000 maxuV: 1300000, not supported by regulator
[ 11.761267] cpu cpu0: _opp_add: OPP not supported by regulators (960000000)
[ 11.768453] core: _opp_supported_by_regulators: OPP minuV: 1200000 maxuV: 1300000, not supported by regulator
[ 11.778428] cpu cpu0: _opp_add: OPP not supported by regulators (1008000000)
[ 11.785720] core: _opp_supported_by_regulators: OPP minuV: 1320000 maxuV: 1320000, not supported by regulator
[ 11.795704] cpu cpu0: _opp_add: OPP not supported by regulators (1104000000)
[ 11.802988] core: _opp_supported_by_regulators: OPP minuV: 1320000 maxuV: 1320000, not supported by regulator
[ 11.812992] cpu cpu0: _opp_add: OPP not supported by regulators (1200000000)
[ 11.820337] core: _opp_supported_by_regulators: OPP minuV: 1340000 maxuV: 1340000, not supported by regulator
[ 11.830340] cpu cpu0: _opp_add: OPP not supported by regulators (1296000000)
[ 11.837598] core: _opp_supported_by_regulators: OPP minuV: 1400000 maxuV: 1400000, not supported by regulator
[ 11.847610] cpu cpu0: _opp_add: OPP not supported by regulators (1368000000)
[ 11.855491] thermal thermal_zone0: binding cdev cpufreq-cpu0 to trip 1 failed: -22
[ 11.863260] thermal thermal_zone0: binding cdev cpufreq-cpu0 to trip 2 failed: -22
[ 11.870979] thermal thermal_zone0: binding cdev cpufreq-cpu0 to trip 3 failed: -22
[ 11.878719] thermal thermal_zone0: binding cdev cpufreq-cpu0 to trip 4 failed: -22