http://bugzilla.kernel.org/show_bug.cgi?id=8865
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |acpi-
| |[EMAIL PROTECTED]
| |et
AssignedTo|[EMAIL PROTECTED] |[EMAIL PROTECTED]
|bugs.osdl.org |
Status|NEW |ASSIGNED
------- Comment #10 from [EMAIL PROTECTED] 2008-01-09 00:07 -------
Devon,
please confirm that you can reproduce the failure with
CONFIG_HWMON=n and the latest stable kernel.
please use thermal.nocrt=1 to disable the shutdown on critical trip point.
You should still, however, get a warning in dmesg that you reached 95C.
please enable CONFIG_PRINTK_TIME=y and enable your
acpi_thermal_get_temperature hook so from dmesg we'll be able to see
how fast the reported temperature is changing.
what cpufreq governor sees the problem?
is the problem still seen when using the "performance" cpufreq governor?
Michal, please use thermal.nocrt=1 and printk time like above
to see if perhaps the shutdown is from a transient erroneous
reading, or if the temperature really is critical.
--
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
_______________________________________________
acpi-bugzilla mailing list
acpi-bugzilla@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla
