https://bugzilla.novell.com/show_bug.cgi?id=333711#c2 Mark Gordon changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mtgordon@novell.com Status|NEW |NEEDINFO Info Provider| |estellnb@gmail.com --- Comment #2 from Mark Gordon 2007-10-15 12:10:43 MST --- That report had the following resolution: http://article.gmane.org/gmane.linux.kernel.suspend.devel/2474 Excerpted: "Your BIOS does not support suspend to RAM. Maybe you need to turn on some option in the BIOS." The contents of /sys/power/state would seem to be a smoking gun. This came to a happy resolution: http://article.gmane.org/gmane.linux.kernel.suspend.devel/2488 Excerpted: "Perfect! I should have tried this before. Sorry for making the earlier noise." Not entirely sure why suspend under WinXP didn't have any problems, but... Could you check the BIOS settings? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=333711 Mark Gordon changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team-screening@forge.provo.novell.com |behlert@novell.com Component|Basesystem |Mobile Devices -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=333711#c4 Stefan Seyfried changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|hmacht@novell.com |seife@novell.com Status|NEW |ASSIGNED --- Comment #4 from Stefan Seyfried 2007-10-25 11:05:18 MST --- The BIOS supports standby (S1), but not suspend to RAM (S3). Unfortunately we don't support standby yet with 10.3. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=333711#c6 Elmar Stellnberger (AT/K) changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|LATER | --- Comment #6 from Elmar Stellnberger (AT/K) 2007-11-18 10:38:21 MST --- Unfortunately that has not helped: * changed /usr/lib/pm-utils/functions as described * added S2RAM_OPTS="-f" to /usr/lib/pm-utils/defaults

powersave -u Suspend to ram request sent. ** nothing happens **

powersave -m Standby request sent. ** nothing happens **

s2ram -f Switching from vt7 to vt1 s2ram_do: No such device switching back to vt7 ** as before: screen turns dark, but directly thereupon machine awakens again *

Selecting Stand-by from the kpowersave tray menu has at first resulted in an increased system activity, but stayed without effect afterwards. Neither StandBy nor S2Ram work. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=333711 User estellnb@gmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=333711#c8 Elmar Stellnberger (AT/K) changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |REOPENED Info Provider|estellnb@gmail.com | --- Comment #8 from Elmar Stellnberger (AT/K) 2007-12-05 10:22:02 MST --- Powersave says it has sent a request but actually nothing happens to pm-suspend.log:

powersave -m Standby request sent. powersave -u Suspend to ram request sent.

tail -n 1 -f /var/log/pm-suspend.log Wed Dec 5 16:38:39 CET 2007: done running thaw hooks.

-- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=333711 User estellnb@gmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=333711#c10 --- Comment #10 from Elmar Stellnberger (AT/K) 2007-12-07 09:21:56 MST --- Created an attachment (id=186414) --> (https://bugzilla.novell.com/attachment.cgi?id=186414) pm-suspend.log -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=333711 Elmar Stellnberger (AT/K) changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |REOPENED Info Provider|estellnb@gmail.com | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=333711 User seife@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=333711#c13 Stefan Seyfried changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dkukawka@novell.com Status|REOPENED |NEEDINFO Info Provider| |dkukawka@novell.com --- Comment #13 from Stefan Seyfried 2007-12-11 05:01:19 MST --- Danny, is it possible that HAL refuses to do s2ram for some reason? Can we somehow find out if the s2ram capability is disabled in HAL? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=333711 Elmar Stellnberger (AT/K) changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |REOPENED Info Provider|dkukawka@novell.com | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=333711 User estellnb@gmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=333711#c16 --- Comment #16 from Elmar Stellnberger (AT/K) 2007-12-11 05:35:03 MST --- Ooops, that was an error by me. 'powersave -u' really does not have any effect while s2ram turns the screen off for about a second (tested again). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=333711 User estellnb@gmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=333711#c18 Elmar Stellnberger (AT/K) changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |NEEDINFO Info Provider| |seife@novell.com --- Comment #18 from Elmar Stellnberger (AT/K) 2007-12-11 06:56:03 MST --- 'echo -n standby >/sys/power/state' does not react on keybord, cd insertion or wol signals, but wakes up as soon as the ** mouse is moved **. YIPEE !!! (Just why haven`t I tested that before) It is the same for any runlevel. Unfortunately the wake from Standby causes an immediate shutdown, which makes it totally inharnessable. P.S.: The s2ram-hack may not have worked, because the reaction is so different. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=333711 User seife@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=333711#c20 Stefan Seyfried changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|seife@novell.com | --- Comment #20 from Stefan Seyfried 2007-12-11 09:03:07 MST --- Another question: does powersave -u not even throw an error? It should... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=333711 User estellnb@gmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=333711#c22 --- Comment #22 from Elmar Stellnberger (AT/K) 2007-12-11 13:47:49 MST --- Yes, pm-suspend is invoked without parameters on 'powersave -u' (My approach was to replace /usr/sbin/pm-suspend by a script that issues 'echo "$0 $*"

...

.../pm-suspend-invocations.log).

-- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=333711 User estellnb@gmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=333711#c24 --- Comment #24 from Elmar Stellnberger (AT/K) 2007-12-11 14:24:44 MST --- Nevertheless several problems still exist: * shutdown after resume (runlev 5: at first kicker & kdesktop vanish ~ black areas on screen (~ Comment #18) * screen is not turned off during standby; messages: Preparing suspend ... Stopping tasks ... done. Suspending console(s) * wake only on mouse move; not on keybord, cd or wol - events (Comment #18) * s2ram -i does refuses to detect my mainboard (first posting) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=333711 User seife@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=333711#c26 Stefan Seyfried changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |hmacht@novell.com Status|ASSIGNED |RESOLVED Resolution| |WONTFIX --- Comment #26 from Stefan Seyfried 2007-12-13 06:32:01 MST --- (In reply to comment #21 from Elmar Stellnberger (AT/K))

No it does not even throw an error (just the message 'Suspend to ram request sent.' ; see Comment #6).

Ok, that's - as we now see by looking at the code - a bug in powersave. (In reply to comment #23 from Elmar Stellnberger (AT/K))

The reason why your hack to pm-action out of Comment #5 did not work as desired was that we have overlooked line 100: 100: if ! grep -q mem /sys/power/state ; then 101: echo "Error: kernel cannot suspend to ram." 1>&2 102: exit 1 103: fi have exchanged that by if ! grep -q '' /sys/power/state and the hack started to issue s2ram on powersave -u.

so now replace the "s2ram" invocation by "echo standby > /sys/power/state" and it should at least do standby. (In reply to comment #24 from Elmar Stellnberger (AT/K))

Nevertheless several problems still exist: * shutdown after resume (runlev 5: at first kicker & kdesktop vanish ~ black areas on screen (~ Comment #18)

This might be because the button module still throws a button event after resuming from standby, which it does not after suspend. A workaround might be that you unload the button module before suspend, see http://en.opensuse.org/Pm-utils on how to do that.

* screen is not turned off during standby; messages: Preparing suspend ... Stopping tasks ... done. Suspending console(s)

Probably a BIOS problem.

* wake only on mouse move; not on keybord, cd or wol - events (Comment #18)

Probably a BIOS problem, might also be a problem in ACPI wakeup handling.

* s2ram -i does refuses to detect my mainboard (first posting)

No, there is nothing to detect, since your machine cannot suspend to RAM. It does not provide capability "S3". There is nothing Linux can do about that. And since you can clearly see that standby is not very well supported and needs lots of testing, i hope that you now also understand why we don't support standby out of the box. Thus i have to close this bug as "WONTFIX" for now, since i simply cannot fix it. I will try to improve support for standby in further releases, but this needs lots of work and lots of testing before we can unleash it on unsuspecting users. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.