I seem to be loosing CPU performance (in terms of reported clock speed) while using Linux (SUSE 9.1, x86_64). FYI, I've never overclocked or played around with clock speed in BIOS or through jumpers.
This is the order of events
1)I boot up my computer. Post screen correctly identifies AMD64 3200+ at 2.2GHz.
2)Linux boots. Log in as user (not root).
3)CPU is correctly reported at 2.2GHz (using "cat /proc/cpuinfo"). However, load is contantly 100%.
4)Find that process "cupsd" is consuming 99% of CPU (This is an entirely different problem it seems). I believe this has to do with incorrectly configured print settings or something. So I "kill" the process.
5)Computer will beep twice.
6)Reported GHz drops to 1.8GHz until hard reset.
My first inclination is that powersave is down throttling the clock to save power. I have tried to shut it off by using "powersave -f" (as root), however it gives me the warning that it can't access the daemon, and I am not sure that it is even running at all.
I have also give it CPU intensive task to test if the CPU speed would jump up during that period, but it did not seem to.
Does anyone have an idea how I could go about diagnosing this problem? How can i get those 400MHz back?
It may be worth noting that the clock speed is correctly identified in Windows. I feel it must be Linux.
This is the order of events
1)I boot up my computer. Post screen correctly identifies AMD64 3200+ at 2.2GHz.
2)Linux boots. Log in as user (not root).
3)CPU is correctly reported at 2.2GHz (using "cat /proc/cpuinfo"). However, load is contantly 100%.
4)Find that process "cupsd" is consuming 99% of CPU (This is an entirely different problem it seems). I believe this has to do with incorrectly configured print settings or something. So I "kill" the process.
5)Computer will beep twice.
6)Reported GHz drops to 1.8GHz until hard reset.
My first inclination is that powersave is down throttling the clock to save power. I have tried to shut it off by using "powersave -f" (as root), however it gives me the warning that it can't access the daemon, and I am not sure that it is even running at all.
I have also give it CPU intensive task to test if the CPU speed would jump up during that period, but it did not seem to.
Does anyone have an idea how I could go about diagnosing this problem? How can i get those 400MHz back?
It may be worth noting that the clock speed is correctly identified in Windows. I feel it must be Linux.
)
Facebook
Twitter