Powernowd does not scale my C2D E6550 higher, even with 100% load

Bug #223361 reported by elfenquetsche
2
Affects Status Importance Assigned to Milestone
powernowd (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: powernowd

powernowd 0.97-2ubuntu4

My Intel Core 2 Duo E6550 (G0 Stepping) has two steps: 2000 and 2333 Mhz. Powernowd seems to recognize this correctly. When I have 100% load, powernowd does not enable the second step.

#powernowd
powernowd: PowerNow Daemon v0.97, (c) 2003-2006 John Clemens
powernowd: Found 2 scalable units: -- 1 'CPU' per scalable unit
powernowd: cpu0: 2000Mhz - 2333Mhz (2 steps)
powernowd: cpu1: 2000Mhz - 2333Mhz (2 steps)

System:
Ubuntu 8.04 64 bit
Intel C2D E6550 G0 Stepping
Gigabyte P35 DS3R F6 bios
2 GB Kingston DDR2 800 Ram

Revision history for this message
jstammi (jstammi) wrote :

I can confirm this for Karmic x64 using Phenom X4 925 on GA-MA78G-DS3H.

I upgraded my system to this configuration and wondered the cpu frequency stays for 800Mhz while running prime95 with 4 load threads.

Stopping powernowd immediately raised frequencies to 2800Mhz (as expected). Starting again lowered frequencies to 800Mhz again.

Though the 4 power levels are detected afais correctly:
$ cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies
2800000 2100000 1600000 800000

And for short time periods one can see the cpu frequencies on single cpu increases to 2800Mhz, too. But with prime95 running I would expect highest frequency all the time.

Searching available packages a bit I found the package powersaved to replace powernowd. After installation of this cpu frequencies now behave as expected.

I'm not sure if the powernowd was installed by default - it might have happened that it was installed on my request (while looking for hardware sensors support).

Revision history for this message
Phillip Susi (psusi) wrote :

The powernowd package is obsolete, please do not use it. CPU frequency scaling is now handled by the kernel, so if you still have issues on a modern release, file a bug against the linux package.

Changed in powernowd (Ubuntu):
status: New → Invalid
Revision history for this message
Steve Langasek (vorlon) wrote :

This is not an appropriate way to declare a package "obsolete". If you think a package should not be used, file a bug to get it removed from the archive and *then* invalidate the bugs.

Changed in powernowd (Ubuntu):
status: Invalid → New
Revision history for this message
Phillip Susi (psusi) wrote :

This package is obsolete and has been removed from the archive. Closing associated bugs.

Changed in powernowd (Ubuntu):
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.