Re: [PATCH v2 2/3] thermal: hwmon: Register a hwmon device for each thermal zone
Oliver Freyermuth <[email protected]> Tue, 28 Jul 2026 23:26:18 +0200
| Newsgroups | dev.linux.lists.sashiko,org.kernel.vger.linux-hwmon |
|---|---|
| Message-ID | <[email protected]> |
Dear hwmon devs, (please keep me in CC, I am not subscribed to the list), after upgrading my systems to kernel 7.1.5 which incorporates this change (Arch and Gentoo), I have for now become aware of two places with userspace fallout from this change: * KDE / Plasma System Monitor Report: https://bugs.kde.org/show_bug.cgi?id=523588 Corresponding userspace code: https://invent.kde.org/plasma/ksystemstats/-/blob/46f7e842767774b96bcd22edec0636a267151475/plugins/lmsensors/lmsensors.cpp As Plasma System Monitor remembers the (full) hwmon sensor name in all widgets and thermal zone IDs may change depending on module load order, sensors are lost both after upgrade to 7.1.5 and at "random" boots after (whenever init order changes for some reason). * (good old) gkrellm Report: https://git.srcbox.net/gkrellm/gkrellm/issues/98 As shown in the report, gkrellm remembers the full hwmon sensor name and hence is affected both when upgrading to 7.1.5 and also at "random" boots after (whenever init order changes for some reason). My custom Conky script followed the established practice of these tools and also broke, but in my case, I fixed it myself by just ignoring the thermal zone ID if present ( https://github.com/olifre/conky-themes/commit/6d015b9d9eae21ffab8c5571c387534bb93cbc50 ). As I do not use Gnome or other system monitoring tools, I do not know if the fallout is larger than this, but given that lmsensors returns the new names with thermal zone ID included, it seems likely other tools suffer from similar problems. Cheers, Oliver