Jeremy Fitzhardinge wrote:
> Alexey Starikovskiy wrote:
>
>> Could you try to unload or disable hardware sensors and check if it
>> helps?
>> CONFIG_I2C=m
>> CONFIG_I2C_ALGOBIT=m
>> CONFIG_I2C_ALGOPCA=m
>> CONFIG_I2C_I810=m
>> CONFIG_I2C_PIIX4=m
>> CONFIG_SENSORS_DS1337=m
>> CONFIG_SENSORS_DS1374=m
>> CONFIG_SENSORS_EEPROM=m
>> CONFIG_SENSORS_PCF8574=m
>> CONFIG_SENSORS_PCA9539=m
>> CONFIG_SENSORS_PCF8591=m
>> CONFIG_SENSORS_MAX6875=m
>>
>
> That seems to have helped. If I watch
> /proc/acpi/thermal_zone/THM?/temperature, it seems stable even under
> load. I didn't try watching the thermal_zones when these options were
> enabled, but I presume the temperature was not controlled for it to hit
> 128 degC.
Hm, perhaps I was too optimistic. I have lm_sensors disabled, and all
i2c options unconfigured in my kernel, but it still has temperature
control problems. Perhaps the ambient temperature was lower when I
reported success.
When I do a big compile, the temperature reported in
/proc/acpi/thermal_zone/THM0/temperature rapidly approaches 100C, and
when it goes over 100 it triggers the critical shutdown. When it shuts
down, it (mis-?)reports the temperature as 128C.
This seems to be real, and not a kernel artifact. If I reboot the same
kernel immediately, it boots up to the message "ACPI: Core revision
20070126" and then hangs. If I boot Windows immediately afterwards, it
reboots a short way into the boot process.
I've noticed one behavioral change with this kernel. On the older
kernels, the CPU frequency would sometimes drop to lowest speed,
apparently because of an ACPI thermal limiting event. This kernel
doesn't seem to drop speed. I seem to remember Ingo had a patch to
ignore the ACPI thermal limits in cpufreq; did that get merged?
J
-
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
