Comment # 7 on bug 925961 from Jean Delvare

The acerhdf driver is the same in openSUSE 13.1 and 13.2.

The coretemp driver reads the temperature values from MSR, while the acerhdf
uses ACPI EC reads. It's hard to tell where exactly the EC gets the
temperatures, but if these would interfere at the hardware level, the same
problem would exist with openSUSE 13.1, which is not the case.

I rather suspect some problem in the thermal subsystem, however the coretemp
driver registers with the hwmon subsystem. There is a bridge between both
subsystems, to expose thermal zones as hwmon temperature device, but it does
not go in the other direction so I can't see how a hwmon driver could impact
the acerhdf driver.

So I'm afraid I have no idea what's going on.

Dieter, could you please describe precisely what happens under 13.2 in the
following cases:

* Neither coretemp nor acerhdf is loaded.
* Only acerhdf is loaded.
* Only coretemp is loaded.
* First acerhdf is loaded, then coretemp is loaded.
* First coretemp is loaded, then acerhdf is loaded.

Best way to test this is to blacklist both modules and load them manually, with
a cold boot between each test.

I would also like to know:

* Does "sensors" (without parameters) return anything else, or only coretemp?
On both 13.1 and 13.2.

* Do you have any user-space fan control utility running on this laptop?
Something like the fancontrol script.