Frequency Scaling reverts to "conservative", even with powernowd installed

Bug #87001 reported by Stefano Rivera
4
Affects Status Importance Assigned to Milestone
gnome-power-manager (Ubuntu)
Invalid
Undecided
Unassigned
powernowd (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: linux-source-2.6.20

My Acer Ferrari 4005WLMi Laptop keeps booting up with the "conservative" governor enabled. I can change it to ondemand, but a suspend, hibernate, or reboot seems to revert it to conservative.

$ dpkg -l powernowd
ii powernowd 0.97-1ubuntu7 control cpu speed and voltage using 2.6 kernel interfa
$ uname -a
Linux liszt 2.6.20-8-generic #2 SMP Tue Feb 13 01:14:41 UTC 2007 x86_64 GNU/Linux

Tags: acer ferrari
Revision history for this message
Stefano Rivera (stefanor) wrote :
Revision history for this message
Stefano Rivera (stefanor) wrote :
Revision history for this message
Stefano Rivera (stefanor) wrote :

Note: I've also reported this in bug #80813 on package powernowd (which may well be the same problem...)

Tim Gardner (timg-tpi)
Changed in linux-source-2.6.20:
assignee: nobody → timg-tpi
Revision history for this message
Stefano Rivera (stefanor) wrote :

Hmm. More to this, it changes automatically to "powersave" when I'm on battery, so I'm thinking maybe it's a g-p-m bug.

Revision history for this message
Ben Collins (ben-collins) wrote :

The kernel doesn't keep state on this setting. That's up to userspace.

Changed in linux-source-2.6.20:
status: Unconfirmed → Rejected
Revision history for this message
Paul Sladen (sladen) wrote :

This is somehow related to bug #78512.

Revision history for this message
Stefano Rivera (stefanor) wrote :

Bug 78512 is SMP, I'm talking uniprocessor.

Revision history for this message
Paul Sladen (sladen) wrote :

The built-in default of the kernel is 'conservative'. When a computer is switched off, it has no memory of previous settings. When the system boots, the built-in default is always used ('conservative').

If we want something else to be used, we need to have a program to tell the kernel to use something other than the default, /at every boot/.

After we have told the kernel we would like it to use a different governor, then we're okay to complain about the kernel changing the governor on its own.

The initscript that currently does this type of setting is called '/etc/init.d/powernowd'; not that this is primarily a script, by default we no longer start the associated daemon. That script currently lacks a useful configuration method since we stopped using the daemon and switched to the built-in kernel methods.

Changed in gnome-power-manager:
status: Unconfirmed → Rejected
Revision history for this message
Paul Sladen (sladen) wrote :

The 'powernowd' initscript lacks a useful configuration method. Also related to bug #78512 (restoring those configuration choices following a resume from hibernation or suspend with multiple CPUs).

Changed in linux-source-2.6.20:
assignee: timg-tpi → nobody
status: Rejected → Confirmed
Revision history for this message
Stefano Rivera (stefanor) wrote :
Changed in powernowd:
status: Confirmed → Rejected
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.