I had two systems, none had more than two thermal zones.
It was enough to outline the test a bit better, but not to show the good / bad
case output.
But it gave me the chance to test and install the build I had which is
all fine
$ sudo apt install ./thermald_2.4.9-1ubuntu0.5_amd64.deb
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Note, selecting 'thermald' instead of './thermald_2.4.9-1ubuntu0.5_amd64.deb'
The following packages will be upgraded:
thermald
1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/221 kB of archives.
After this operation, 0 B of additional disk space will be used.
Get:1 /home/ubuntu/thermald_2.4.9-1ubuntu0.5_amd64.deb thermald amd64
2.4.9-1ubuntu0.5 [221 kB]
(Reading database ... 106221 files and directories currently installed.)
Preparing to unpack .../thermald_2.4.9-1ubuntu0.5_amd64.deb ...
Unpacking thermald (2.4.9-1ubuntu0.5) over (2.4.9-1ubuntu0.4) ...
Setting up thermald (2.4.9-1ubuntu0.5) ...
Processing triggers for dbus (1.12.20-2ubuntu4.1) ...
Processing triggers for man-db (2.10.2-1) ...
Scanning processes...
Scanning processor microcode...
Scanning linux images...
Running kernel seems to be up-to-date.
The processor microcode seems to be up-to-date.
No services need to be restarted.
No containers need to be restarted.
No user sessions are running outdated binaries.
No VM guests are running outdated hypervisor (qemu) binaries on this
host.
** Description changed:
[Impact]
Some CPU sensors are not enumerated, this can make thermald deviates from the
correct behavior of the CPU TDP.
[Fix]
Traverse all sensors under hwmon sysfs directory to make sure everything is
enumerated.
[Test]
Check the output of thermald. Once the fix is in place, thermal zones that
are previously omitted now shows up:
[INFO]Zone 1: AMBF, Active:1 Bind:1 Sensor_cnt:1
+ To do so
+ 0. get a large machine which will have more thermal zones
+ 1. stop the potentially auto-running service
+ $ systemctl stop thermald
+ 2. run the daemon in foreground with loglevel to see what is going on.
+ On many modern systemd (=the large ones) it might not know the CPUid,
+ to bypass that for the test you can ask it to ignore the check
+ $ sudo thermald --no-daemon --loglevel=info --ignore-cpuid-check
+ 3. check the output
+ On init the system will be probed and that will show something like:
+
+ ...
+ ZONE DUMP BEGIN
+ [1718954645][INFO]Zone 2: cpu, Active:1 Bind:0 Sensor_cnt:1
+ ...
+ [1718954645][INFO]Zone 3: cpu, Active:1 Bind:0 Sensor_cnt:1
+ ...
+ ZONE DUMP END
+
+ In here, on systems with many thermal zones one would before the fix
+ only see a few, and with the fix more zones.
+
[Where problems could occur]
Since the new logic traverse the whole hwmon sysfs, the startup time can take
slightly longer.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054391
Title:
Fix CPU thermal sensors enumeration
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2054391/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
