Bug 40312
Summary: | /sys/bus/platform/devices/coretemp content is changed from previous kernels | ||
---|---|---|---|
Product: | Drivers | Reporter: | dasnoopy (a.antolini.new) |
Component: | Hardware Monitoring | Assignee: | Jean Delvare (jdelvare) |
Status: | RESOLVED INVALID | ||
Severity: | normal | CC: | linux |
Priority: | P1 | ||
Hardware: | All | ||
OS: | Linux | ||
Kernel Version: | linux 3.0.0 stable | Subsystem: | |
Regression: | No | Bisected commit-id: |
Description
dasnoopy
2011-07-29 06:31:34 UTC
Regarding all temps in one dir : it's a change implemented with Kernel 3.0 commit 199e0de7f5df31a4fc485d4aaaf8a07718252ace Author: Durgadoss R <durgadoss.r@intel.com> Date: Fri May 20 01:29:35 2011 +0530 hwmon: (coretemp) Merge pkgtemp with coretemp This patch merges the pkgtemp with coretemp driver. The sysfs interfaces for all cores in the same pkg are shown under one directory, in hwmon. It also supports CONFIG_HOTPLUG_CPU. So, the sysfs interfaces are created when each core comes online and are removed when it goes offline. sorry if I didn't check before in the changelog Now I would like to now if the core count is correct or not Andrea Data is correct and as expected. temp1 is the package temperature which is not supported for your CPU. Applications should not depend on sequential sensor attribute numbering. Guenter This is a bug in conky or any other application affected by this change, so please report it there. The coretemp driver still implements a compliant hwmon interface which will make any reasonably recent version of libsensors happy. Not only monitoring applications shouldn't assume fixed or sequential numbering of sensor inputs, as Guenter correctly wrote in comment #2, but they shouldn't assume _anything_ at all, and they shouldn't have to: proper monitoring applications should simply build on top of libsensors. |