| |||||||||||||
|
| |||||||||||||
OverheatingOverheatingPosted May 13, 2008 7:24 UTC (Tue) by ajtucker (subscriber, #11974)Parent article: Matthew Garrett on the race to idle
After reading the article and re-enabling cpufreq-ondemand, I now remember why I use the userspace cpuspeed daemon instead. After 10 minutes or so my laptop switches itself off when the CPU has reached something over 90 degrees C. So while the benefit of switching states quickly is nice (it certainly feels more responsive), the kernel CPU governers definitely need to be able to keep an eye on, and be constrained by, the CPU temperature, as Matthew mentioned briefly in the article.
(Log in to post comments)
Overheating Posted May 13, 2008 16:17 UTC (Tue) by zlynx (subscriber, #2285) [Link] It sounds to me that your laptop needs to be taken apart and have the dust blown out. You may also have one of those problems where the heatsink uses a fluid coolant that has leaked out.
Overheating Posted May 15, 2008 15:11 UTC (Thu) by ajtucker (subscriber, #11974) [Link] Thanks, it'd been a while since I'd given it a good blast, and it certainly helped -- I've reverted back to using the kernel on-demand governor and the temperature is more stable. I still stand by the comment that it should be possible to tell the governor to take into account the CPU temperature and trip points and throttle back if necessary.
Overheating Posted May 22, 2008 16:24 UTC (Thu) by anton (subscriber, #25547) [Link] I still stand by the comment that it should be possible to tell the governor to take into account the CPU temperature and trip points and throttle back if necessary.Since you have been happy with a userspace solution for that, you can also use a userspace solution in combination with ondemand: Just lower the cpufreq/scaling_max_freq value when the CPU gets too hot. This will make ondemand lower the maximum frequency it chooses.
|
|
||||||||||||