registry team mailing list archive

[Bug Watch Updater <203677@xxxxxxxxxxxxxxxxxx>]

Launchpad has imported 4 comments from the remote bug at
http://bugs.freedesktop.org/show_bug.cgi?id=15144.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.

------------------------------------------------------------------------
On 2008-03-20T08:09:38+00:00 Sense Hofstede wrote:

As reported on Launchpad(https://bugs.edge.launchpad.net/ubuntu/+source/hal/+bug/203677) by Levis Cyril cpufreq doesn't change after a suspend to the RAM. 
The version being used is 0.5.10+git20080301-1ubuntu2, at Hardy Heron.
At the original report you can find reports and logs. If you need more, please don't hesitate to ask.

Reply at: https://bugs.launchpad.net/gnome-power/+bug/203677/comments/7

------------------------------------------------------------------------
On 2008-03-21T13:02:35+00:00 Danny Kukawka wrote:

I don't see why you think this is a HAL issue. There is never a info
about the cpufreq get changed. This is no indication for a HAL bug.
First check if g-p-m really set the CPU freq to HAL, it could be g-p-m
bug or a kernel problem.

Reply at: https://bugs.launchpad.net/gnome-power/+bug/203677/comments/8

------------------------------------------------------------------------
On 2008-03-22T03:34:20+00:00 Sense Hofstede wrote:

Maybe the output of lshal -m gives more information:
http://launchpadlibrarian.net/12739550/oups_forget_this.txt

According to someone at LP (and I believe him, since I'm not a HAL
expert) this log indicates that the problem is within HAL.

Reply at: https://bugs.launchpad.net/gnome-power/+bug/203677/comments/9

------------------------------------------------------------------------
On 2008-03-26T11:41:23+00:00 Danny Kukawka wrote:

No, this log don't indicate anything. SetPowersave() (or the property
power_management.is_powersave_set) has nothing to do with CPU freq
settings. It's the job of g-p-m to set the CPU freq (via) after resume
and not the job of HAL itself. Or it's a kernel bug.

And: you don't see anything in lshal -m if the CPU freq get changed

Close this for now, until there is a proof that HAL cause the problem,
as NOTOURBUG

Reply at: https://bugs.launchpad.net/gnome-power/+bug/203677/comments/10


** Changed in: hal
       Status: Invalid => Won't Fix

** Changed in: hal
   Importance: Unknown => Medium

-- 
gnome-power-manager cpufreq problem
https://bugs.launchpad.net/bugs/203677
You received this bug notification because you are a member of Registry
Administrators, which is the registrant for gnome-power.