This was actually introduced from Jammy to Noble via the upgrade of landscape-client from xx to 24.02. In version 24.02, as said in the GitHub release notes (https://github.com/canonical/landscape- client/releases/tag/24.02), the temperature is now read "from hwmon devices [by @jck112 in #204]". Before, it was only read from "thermal" which often leads to more accurate results and less outliers than hwmon.
Unfortunately, the following precedence is used for reading thermal zones (depending on availability): 1. /sys/class/hwmon/*/temp*_input 2. /sys/class/thermal/*/temp 3. /proc/acpi/thermal_zone/*/temperature. This was introduced by PR #204 (canonical/landscape-client). Changing the order to 1. /sys/class/thermal/*/temp 2. /sys/class/hwmon/*/temp*_input 3. /proc/acpi/thermal_zone/*/temperature would help in this case since hwmon is causing the outliers. We experienced this issue right after upgrading from Jammy to Noble because of the bumped version. Downgrading to a version prior to 24.02 would also help mitigate this issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2126868 Title: landscape-client: Ability to scope reported temperature sensor on sysinfo command To manage notifications about this bug go to: https://bugs.launchpad.net/landscape-client/+bug/2126868/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
