Comment 40 for bug 88899
Revision history for this message
| C. Brayton (cbrayton-boizebueditorial) wrote | #40 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
(Get the code!)
Problem persists in Lucid 10.04Alpha1 (2.6.312-10) as in all releases after acpi-cpufreq was compiled in rather than left as a module. I cannot detect what is triggering the cpufreq governor to suddenly be set to that "between minimum and minimum," according to cpufreq-info. That it happens after a period of time in operation suggests it could be a temperature threshhold, but I thought I reset mine to 85-100 (reasonable for my Latitude D620, which tends to run between 60-75 degrees C.)
I am not seeing any kernel messages to this effect, though.
I am a poetry-major lower-end poweruser, and this has been driving me nuts for weeks and weeks. On suggestion of various fora, I recompiled a buggy DSDT, played with commandline options at bootup, and other stuff. Tried powernowd -d -vvv and noticed that it seemed to be working at first, resetting freqs according to the rules, at some point its started showing close to 100% CPU usage and indicating freq resets to the maximum that were not actually occurring.
Funny, though: it seems as though the Lucid daily LiveCD, booted off a USB stick, does not have this problem.