On Sat, 4 Sep 2004 11:22:27 +0200, Stefan Seyfried
On Fri, Sep 03, 2004 at 05:40:27PM -0700, Osho GG wrote:
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?
I am using 2.6.8.1 patched with acpi-20040715-2.6.8, bootsplash-3.1.4-sp3, bk-cpufreq and cpufreq-speedstep-dothan-3 patches. I have also compiled all the ACPI modules in the kernel (not sure if that matters though).
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?
Before standby, pidof powersaved gives 13167. After standby, pidof powersaved gives 20493. I tried doing powersave -c at this point but that just seemed to hang. Doing strace -p 20493 gives Process 20493 attached - interrupt to quit waitpid(20494, So, I did ps -aef | grep 20494 to find out which process 20494 is. I got root 20494 20493 0 01:28 ? 00:00:00 /bin/bash /usr/sbin/powersave_proxy global.resume.standby root 21185 20494 0 01:28 ? 00:00:00 /usr/bin/powersave -c So, I guessed that 20494 is the process that is really stuck. So, I did kill 20494. Now, strace -p 20493 gives more messages after waitpid. Process 20493 attached - interrupt to quit waitpid(20494, [WIFSIGNALED(s) && WTERMSIG(s) == SIGTERM], 0) = 20494 --- SIGCHLD (Child exited) @ 0 (0) --- time([1094320778]) = 1094320778 rt_sigaction(SIGPIPE, {0x401d3f60, [], 0}, {SIG_DFL}, 8) = 0 send(3, "<30>Sep 4 10:59:38 [powersaved]"..., 68, 0) = 68 rt_sigaction(SIGPIPE, {SIG_DFL}, NULL, 8) = 0 time([1094320778]) = 1094320778 rt_sigaction(SIGPIPE, {0x401d3f60, [], 0}, {SIG_DFL}, 8) = 0 send(3, "<30>Sep 4 10:59:38 [powersaved]"..., 134, 0) = 134 rt_sigaction(SIGPIPE, {SIG_DFL}, NULL, 8) = 0 time([1094320778]) = 1094320778 rt_sigaction(SIGPIPE, {0x401d3f60, [], 0}, {SIG_DFL}, 8) = 0 send(3, "<28>Sep 4 10:59:38 [powersaved]"..., 189, 0) = 189 rt_sigaction(SIGPIPE, {SIG_DFL}, NULL, 8) = 0 exit_group(0) = ? Process 20493 detached I tried doing pidof powersaved at this point and it resulted in nothing. So, I guess powersaved is no longer running. I also got a little warning from kpowersave telling me to restart rcpowersaved. I did rcpowersaved restart and everything is back working as expected (CPU frequency is getting throttled as seen in /proc/cpuinfo for example). Sorry if this was too much information. thanks, Osho