On Fri, 2010-04-23 at 10:11 -0400, Greg Folkert wrote: > Okay, I can't get reportbug to work properly at the moment, it fails to > reach BTS for linux-2.6 > > > In any case, here is the details I have now: > > Package: linux-2.6 > Version: 2.6.32+25 > Severity: normal > > Running linux-image-2.6.32-3-686-bigmem 2.6.32-9, this problem is better > without a battery in the battery slot, giving me 1.6GHz. > > Problems though, is that now the machine is preferring 1.6GHz now for > everything, no matter what power profile I give it. No matter what I try > to force. Sometimes it even locks at 800MHz. I can see the policy change for > a few milliseconds, but goes right back to 1.6GHz > > Plus the 2.6.32 kernel screws up the X rendering and makes it feel like > I'm back in 1994 running CDE on OSF/1 box, using XDMCP. Lethargic response > times, likely due to the GEM system changes. > > I've switched back to linux-image-2.6.31-rc4-686-bigmem > 2.6.31~rc4-1~experimental.1~snapshot.14067 as my kernel in use. This gives > *MUCH* *MUCH* better CPU speed results *AND* the X renders fast and light, > like it should. Since the updates to cpufreq* packages (and other things I am sure) > I am running at 2.2GHz all the time (without the battery in, or out ON AC only) [...] Please report this upstream at <https://bugzilla.kernel.org> under product 'Power Management, component 'cpufreq'. Let us know the bug number so that we can track it. Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse.
Attachment:
signature.asc
Description: This is a digitally signed message part