The remaining task here for hal has been fixed in a recent pm-utils
upload.
** Changed in: hal (Ubuntu)
Status: Confirmed = Fix Released
--
CPU Frequency Scaling Monitor applet on dual-core doesn't work after resume
https://bugs.launchpad.net/bugs/124797
You received this bug
Marking confirmed as it can be reproduced here and as suggested in
comment 30.
** Changed in: hal (Ubuntu)
Status: New = Confirmed
--
CPU Frequency Scaling Monitor applet on dual-core doesn't work after resume
https://bugs.launchpad.net/bugs/124797
You received this bug notification
I believe this bug (The suspend scripts do not restore the cpufreq
governor on resume.) is the same as this other bug from 2006:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/64070
--
CPU Frequency Scaling Monitor applet on dual-core doesn't work after resume
I'm getting this problem on an up to date Hardy too.
Running a Core 2 Duo Lenovo R61.
Do you need any logs, specs etc?
--
CPU Frequency Scaling Monitor applet on dual-core doesn't work after resume
https://bugs.launchpad.net/bugs/124797
You received this bug notification because you are a
I just attached a dmesg log, but by mistake attached it to a duplicate
of this bug. The attachment is
http://launchpadlibrarian.net/12134489/dmesg . It's from booting
normally, working for a while, then suspending and resuming. The suspend
begins at timestamp 5712. In particular, the line
[
I'm no kernel hacker, but that does look very interesting... in fact,
the lines before and after look related as well:
[0.574636] ACPI Error (psloop-0136): Found unknown opcode 17 at AML address
c28b27c3 offset 0, ignoring [20070126]
[0.574645] ACPI Error (psargs-0355): [DBþÿ]
I should probably also add that, ostensibly at least, restarting
powernowd fixes the problem.
If I try and write this into one of the acpi scripts though it doesn't
take effect.
Does anyone have any idea how to debug this further?
--
CPU Frequency Scaling Monitor applet on dual-core doesn't
I examined the original bug report from TJ and noted that before a resume, the
state in /sys/devices/system/cpu/cpuN/cpufreq/scaling_governor for CPU's 0 and
1 on my laptop is ondemand.
However after a resume they are reset to performance, and not preserving the
original ondemand state.
Now.
The hal scripts in /usr/lib/hal/scripts/, specifically hal-system-power-
suspend and hal-system-power-hibernate prefer to use powersaved if it is
installed, but in my experience, powersaved does not work.
I modified these scripts to prefer acpi-scripts instead. I can upload a
patch if you want.
I'm not sure if this has been mentioned before, but if I unload
(modprobe -r) acpi_cpufreq and reload it, the proper cpufreq directories
and symlinks are restored.
For now, I'll will add this in the resume.d dir for /etc/acpi
I wonder if this is true w/ other cpufreq modules (k8, centrino)? The
** Also affects: hal (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Status: In Progress = Invalid
--
CPU Frequency Scaling Monitor applet on dual-core doesn't work after resume
https://bugs.launchpad.net/bugs/124797
You received this bug notification
I just had a conversation with Colin King on IRC. This bug apparently
conflates two issues:
1. The suspend scripts do not restore the cpufreq governor on resume.
2. The cpufreq support on core 1 disappears entirely on resume.
This bug now tracks issue 1, which has to do with HAL.
For issue 2,
** Changed in: linux (Ubuntu)
Status: Triaged = In Progress
--
CPU Frequency Scaling Monitor applet on dual-core doesn't work after resume
https://bugs.launchpad.net/bugs/124797
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Changed in: linux (Ubuntu)
Assignee: Ubuntu Kernel ACPI Team (ubuntu-kernel-acpi) = Colin King
(colin-king)
--
CPU Frequency Scaling Monitor applet on dual-core doesn't work after resume
https://bugs.launchpad.net/bugs/124797
You received this bug notification because you are a member
** Changed in: linux (Ubuntu)
Importance: Undecided = Medium
Assignee: (unassigned) = Ubuntu Kernel ACPI Team (ubuntu-kernel-acpi)
Status: Incomplete = Triaged
--
CPU Frequency Scaling Monitor applet on dual-core doesn't work after resume
https://bugs.launchpad.net/bugs/124797
You
It seems that the ACPI team is taking care of it now (or at least they
are assigned to it...)... COOL!
My system may be different than most, here's my specs:
Dell Vostro 1400
Intel Core 2 Duo @ 2.0 GHz
nVidia GeForce 8400 GS
3 GB Ram
160 GB Hard Disk w/ ~120 GB Linux partition
Something (in my
According to Matthew Garrett, the ACPI errors are a good candidate for
being the cause of this bug.
--
CPU Frequency Scaling Monitor applet on dual-core doesn't work after resume
https://bugs.launchpad.net/bugs/124797
You received this bug notification because you are a member of Ubuntu
Bugs,
I've been running 2.6.24-? on gutsy for weeks with no real problems. If
you're worried, make sure it doesn't pull too much hardy stuff in...
Last I checked, 2.6.24 didn't require very many (any?) package upgrades.
(I haven't had a chance to play with the most recent one...)
The old kernel
Nothing has changed with 2.6.24-10, the bug is still there. The dmesg is
also basically the same, but I'm attaching it just in case. In
particular, the suspicious ACPI errors mentioned above are still there.
** Attachment added: dmesg
http://launchpadlibrarian.net/12235140/dmesg
--
CPU
Care to test with the latest 2.6.24-10 ubuntu-kernel. If the issue
still exists, care to attach your dmesg output after resuming from
Suspend?
Also, please note that we will keep this report open against the
currently developed kernel bug against 2.6.20 and 2.6.22 this will be
closed. Thanks.
Is there a package that won't break gutsy that I can use to test, or
will I have to install Hardy?
--
CPU Frequency Scaling Monitor applet on dual-core doesn't work after resume
https://bugs.launchpad.net/bugs/124797
You received this bug notification because you are a member of Ubuntu
Bugs,
At the moment, there's not even a Hardy package since 2.6.24-10 is not
in the archive: http://packages.ubuntu.com/search?keywords=linux-
image-2.6.24searchon=namessuite=hardysection=all
--
CPU Frequency Scaling Monitor applet on dual-core doesn't work after resume
What are you talking about? There is a 2.6.24-10 on that page for every
arch that I can think of--can I install the hardy package on gutsy?
--
CPU Frequency Scaling Monitor applet on dual-core doesn't work after resume
https://bugs.launchpad.net/bugs/124797
You received this bug notification
That 2.6.24-10 package appeared just in the last few hours. I wouldn't
recommend installing it on Gutsy.
--
CPU Frequency Scaling Monitor applet on dual-core doesn't work after resume
https://bugs.launchpad.net/bugs/124797
You received this bug notification because you are a member of Ubuntu
For me, running /etc/init.d/powernowd restart does not help, apparently
because some modules (like acpi-cpufreq) can't be unloaded.
--
CPU Frequency Scaling Monitor applet on dual-core doesn't work after resume
https://bugs.launchpad.net/bugs/124797
You received this bug notification because you
I am quite sure that bug #183033 is a duplicate of this one. Bug #68191
seems to have a few different issues mixed in, one of them being this
one.
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
CPU Frequency Scaling Monitor applet on dual-core doesn't work after
Does anyone see any substantial difference between this bug and bug
#68191 or bug #183033? I'm thinking all 3 are dupes now.
--
CPU Frequency Scaling Monitor applet on dual-core doesn't work after resume
https://bugs.launchpad.net/bugs/124797
You received this bug notification because you are a
I can seem to change governor, but after a resume I get the governor set
to performance. This is on Hardy: Linux yensid 2.6.24-3-generic #1 SMP
Thu Jan 3 23:30:29 UTC 2008 i686 GNU/Linux
--
CPU Frequency Scaling Monitor applet on dual-core doesn't work after resume
Leann correctly marked my bug (141339) as a duplicate of this one.
On my system, running /etc/init.d/powernowd restart reliably fixes the
problem. I created a script in /etc/acpi/resume.d with these contents:
#!/bin/sh
/etc/init.d/powernowd restart
This is automatically run when the system
Hi TJ, I'm running the new 7.10 Gutsy release (2.6.22-14-generic kernel)
on my Dell Inspiron 1420 laptop with Intel(R) Core(TM)2 Duo CPU T7500
and using CPU Frequency Scaling Monitor 2.20,0 and can verify this bug
still exists. I'm curious if you've noticed any regressions from Gutsy
Tribe-5 to
** Also affects: linux-source-2.6.22 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux-source-2.6.22 (Baltix)
Status: New = Invalid
--
CPU Frequency Scaling Monitor applet on dual-core doesn't work after resume
https://bugs.launchpad.net/bugs/124797
You received
** Changed in: linux-source-2.6.22 (Ubuntu)
Importance: Undecided = Low
Status: New = Incomplete
--
CPU Frequency Scaling Monitor applet on dual-core doesn't work after resume
https://bugs.launchpad.net/bugs/124797
You received this bug notification because you are a member of Ubuntu
It does look as if this bug has returned. I'll dig into it.
** Changed in: linux-source-2.6.22 (Ubuntu)
Assignee: (unassigned) = TJ (intuitivenipple)
Status: Incomplete = Confirmed
--
CPU Frequency Scaling Monitor applet on dual-core doesn't work after resume
Also confirmed with a duo core 2. Removing one applet and placing anew
is the only way I've seen around the problem.
--
CPU Frequency Scaling Monitor applet on dual-core doesn't work after resume
https://bugs.launchpad.net/bugs/124797
You received this bug notification because you are a member
Fixed as of Gutsy Tribe-5 2.6.22-10-generic, with CPU Frequency Scaling
Monitor 2.19.1
--
CPU Frequency Scaling Monitor applet on dual-core doesn't work after resume
https://bugs.launchpad.net/bugs/124797
You received this bug notification because you are a member of Ubuntu
Bugs, which is the
not a gnome-applets bug
** Changed in: gnome-applets (upstream)
Status: New = Invalid
** Changed in: linux-source-2.6.20 (Ubuntu)
Sourcepackagename: gnome-applets = linux-source-2.6.20
Assignee: Ubuntu Desktop Bugs = (unassigned)
Status: Confirmed = New
--
CPU Frequency
I confirm this on my Lenovo T60p. However, this bug is not related to
the applet but it is an acpi bug. In fact, there is no way I can change
the frequency even using cpufreq-set or cpufreq-selector.
--
CPU Frequency Scaling Monitor applet on dual-core doesn't work after resume
Thank you for your bug. Marking confirmed since somebody else has the
issue. Likely an upstream bug to send on bugzilla by somebody having a
configuration to trigger the bug
** Changed in: gnome-applets (Ubuntu)
Importance: Undecided = Low
Assignee: (unassigned) = Ubuntu Desktop Bugs
I confirm this, 2nd cpu seems not to respond to a governor option change after
suspend/resume; removing and re-adding the applet corrects it.
With Gutsy's kernel 2.6.22 I don't see the problem right now. I will test it
more extensively though and report if I see anything interesting.
--
CPU
39 matches
Mail list logo
