Unfortunately this bug report is being closed because we received no
response to the last inquiry for information. However, the Intrepid
Ibex 8.10 Beta release was most recently announced -
http://www.ubuntu.com/testing/intrepid/beta . If you are able to
confirm this is still an issue with this
The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the
upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would
appreciate it if you could please test this newer 2.6.27 Ubuntu kernel.
There are one of two ways you should be able to test:
1) If you are comfortable
** Changed in: linux-source-2.6.17 (Ubuntu)
Status: Invalid = Won't Fix
** Tags removed: edgy-close
--
After hibernation, powernowd only controls one CPU
https://bugs.launchpad.net/bugs/47513
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct
The 18 month support period for Edgy Eft 6.10 has reached it's end of
life. As a result, we are closing the linux-source-2.6.17 Edgy Eft
kernel task.
Hardy Heron 8.04 was recently released. It would be helpful if you
could test the new release and verify if this is still an issue -
I am assigning this bug to the 'ubuntu-kernel-team' per their bug
policy. For future reference you can learn more about their bug policy
at https://wiki.ubuntu.com/KernelTeamBugPolicies .
** Changed in: linux-source-2.6.17 (Ubuntu)
Assignee: (unassigned) = Ubuntu Kernel Team
I'm having this problem in Kubuntu Feisty on my HP Pavilion zv2040TX
with a 1.7GHz Core 2 Duo
--
After hibernation, powernowd only controls one CPU
https://launchpad.net/bugs/47513
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
A simple workaround for those actually using powernowd could be a script
in /etc/acpi/resume.d, which calls something like invoke-rc.d --quiet
powernowd restart
--
After hibernation, powernowd only controls one CPU
https://launchpad.net/bugs/47513
--
ubuntu-bugs mailing list
If you're using powernowd, you should be using the userspace governor,
not the ondemand one. powernowd will automatically set this when
starting up, which is why restarting powernowd solves the problems you
are all seeing.
When the system goes to sleep and comes back, apparently the kernel (or
Actually, I'm wrong, it looks like edgy has changed to using the
'ondemand ' governor by default instead of the actual powernowd daemon.
So my daemon isn't even running anymore.
Still the governor isn't getting restored correctly on both CPUs. this
is a kernel and/or ubuntu script problem. Not a
Ok John, thanks for your time :)
I will go on and see what else I dig up on this issue in the
kernel/ubuntu scripts !
--
After hibernation, powernowd only controls one CPU
https://launchpad.net/bugs/47513
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
I'm having the same problem with the latest (24/10/06) Kubuntu Edgy
packages. Same versions as above. Laptop is a Toshiba Satellite
A100-0FH, 1.6ghz Core Duo.
After suspend or hibernation, cpu0 uses the ondemand governor (good),
cpu1 uses performance governor (not good). The fan 'sticks' on
I get the very same error in the latest (k)ubuntu edgy:
powernowd: Version: 0.97-1ubuntu6
kernel: 2.6.17-10-generic #2 SMP Fri Oct 13 18:45:35 UTC 2006 i686 GNU/Linux
My machine is an IBM/Lenovo Thinkpad T60p (2007-93g), 2.16ghz Core Duo.
Only one CPU is controlled by powernowd upon wakeup.
If
12 matches
Mail list logo
