[Bug 462125] [NEW] CPU scaling always use Dynamic on Performance Profile (even if Performance policy is set)
Gustavo A. Díaz
gustavo.diaz at gmail.com
Tue Oct 27 18:03:16 UTC 2009
Public bug reported:
Binary package hint: kdebase-workspace
I think since PowerDevil exist, CPU scaling never worked correctly. On Jaunty and now current using Karmic, when I change from Dynamic to Performance on PowerDevil profiles configuration, after i reboot it uses again Dynamic Policy on Performance profile (even is before it was set to Performance, the GUI says Performance but i see the CPU are working on Dynamic). Now, when i go again to the PowerDevil configuration GUI and i press apply again, it returns to Performance policy. But as said, on reboot again returns to Dynamic.
In another partition i am using OpenSUSE 11.2 RC1 and this works correctly: on Performance profile using Performance policy, is always working as expected.
This happen on any system that the CPU allows scaling (at least, on
every of my workstations and notebook). So, i think is not hardware
related at all.
ProblemType: Bug
Architecture: amd64
Date: Tue Oct 27 14:52:25 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/systemsettings
InstallationMedia: Kubuntu 9.10 "Karmic Koala" - Release Candidate amd64 (20091020.2)
NonfreeKernelModules: nvidia
Package: systemsettings 4:4.3.2-0ubuntu7
ProcEnviron:
LANG=es_AR.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SourcePackage: kdebase-workspace
Uname: Linux 2.6.31-14-generic x86_64
XsessionErrors:
(npviewer.bin:2842): Gtk-WARNING **: /usr/lib/gtk-2.0/2.10.0/engines/libqtcurve.so: clase ELF errónea: ELFCLASS64
(npviewer.bin:2842): Gtk-WARNING **: /usr/lib/gtk-2.0/2.10.0/engines/libqtcurve.so: clase ELF errónea: ELFCLASS64
** Affects: kdebase-workspace (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug
--
CPU scaling always use Dynamic on Performance Profile (even if Performance policy is set)
https://bugs.launchpad.net/bugs/462125
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to kdebase-workspace in ubuntu.
More information about the kubuntu-bugs
mailing list