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.
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.
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.
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
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.