https://bugzilla.kernel.org/show_bug.cgi?id=15946
--- Comment #89 from Len Brown <l...@kernel.org> 2012-06-05 05:02:31 --- > This is definitely not a temperature problem. It wasn't useful for the original submitter, because their EC shuts down the system, but possibly your box is different... You can use the kernel cmdline "thermal.nocrt=1" or the module parameter "options thermal nocrt=1" and that will disable the action taken when the critical trip point fires. When it fires, you can then monitor the temperature -- eg. see if it stays high, or spike goes away etc. It seems that the EC on this box is basically going out to lunch. If we have Linux ignore the bogus temperature reading, the EC takes matters into its own hands and shuts off the system. One possible approach would be to neuter the ACPI EC driver altogether so that it doesn't load. For it may be interaction with the Linux EC driver that is confusing the motherboard EC. -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. You are watching the assignee of the bug. ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ acpi-bugzilla mailing list acpi-bugzilla@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla
