On Fri, Sep 03, 2004 at 05:40:27PM -0700, Osho GG wrote:
Hi,
I have SuSE 9.1 professional on IBM Thinkpad T42p laptop and I am using powersaved to manage power, cpu frequency change etc. So far, throttling/dethrottling works very well. It is the best power utility I have seen in any of the distributions that works well out of the box.
Thanks. It will even be better in 9.2 ;-)
My only complaint is that powersaved seems to crash and restart after ACPI standby. I have configured lid close to go to standby (ACPI S3) and lid open to awake up the laptop. The standby works reliably. And the laptop also awakes up to a working stand reliably.
That's nice to hear, i have yet to get my hands on a machine where S3 works reliably. Are you using the SUSE update kernels or some newer 2.6.8... self compiled ones?
Only that the powersaved daemon seems to have crashed and restarted (the process ids for powersaved are different before and after standby).
I cannot really think of what would cause this, since powersaved should not restart itself. Be careful not to confuse the different "powersave" log messages in syslog since the proxy script also logs its pid and it of course is a new proxy after resume. Could you verify with "pidof powersaved" before and after suspend to RAM?
After CPU, the CPU is no longer throttling if I remove the power. kpowersave in KDE system tray does not display any icon but empty space.
I have to do
pkill powersaved rcpowersaved restart
so it seems the powersaved is just hanging somewhere. You could try to find out the PID with pidof powersaved strace -p PID substituting PID with the number you got from pidof. I am afraid it is just hanging on some unfinished socket request. Ah! Try "powersave -c" after resume, this just sends a query for the current cpufreq mode to the daemon via the socket, but we once had a case where we needed one socket connection after resume to kick powersaved back to life, maybe this is a similar issue. To be honest: the whole suspend-to-RAM code paths are rather untested since i had no machine with working S3 available.
and kpowersave, throttling etc. start working as expected.
Is there any way to figure out why powersaved is crashing and make it stop from crashing?
I don't think it is really crashed, i think it is just hanging. If you can bring it back to life with "powersave -c" it will be very easy, otherwise i don't know yet. Thanks for the report! -- Stefan Seyfried