https://bugzilla.novell.com/show_bug.cgi?id=230717 Summary: suspend to ram does not work properly Product: openSUSE 10.2 Version: Final Platform: 32bit OS/Version: SuSE Other Status: NEW Keywords: tracking Severity: Major Priority: P5 - None Component: Usability AssignedTo: siegfried.olschner@novell.com ReportedBy: jan.sekal@volny.cz QAContact: siegfried.olschner@novell.com I have been testing s2ram and suspend to disk quite thouroughly (all experiences made on acer travel mate 2413 NLM): I have tried to change /etc/pm/config s2ram parameters to many (approx. 10) of that listed on http://en.opensuse.org/S2ram With all parameters it was possible to wake the machine up properly for the first time, but none parameter functioned more than once (with some parameters, resuming occurred first after pressing win key several times), after the second suspend to ram (with that particular parameter of s2ram) resuming failed in approx 90 % (this means, that my observation is that the bug is NOT RELATED to HARDWARE, but to the SOFTWARE). With suse 10.1 final, s2ram -f -a3 worked fine (except for one minor problem not inhibiting the functionality - sometimes, screen has not been locked, sometimes some other screensaver has been selected - not the one i told KDE to use), and flawless. today, i had following experience: 1. restart the computer 2. i had five applications running, see. attachment with the desktop screenshot 3. i performed suspend to ram, /etc/pm/config with parameter S2RAM_OPTS="-f -a 3" 4. after resuming, message box telling suspend to ram failed appeared 5. approx. after 20 min of using the computer, a X Window restarted two times in a sequence (in approx. 1 s), i switched to ksysguard and noticed, that it had not been collecting the whole 20 min no data - after the restart of the x window, the data that had been collected all the 20 min scrolled to the left very quickly in the windows of the ksysguard (see the screenshot in attachment) (what would normally take 20 min, took here approx. 30 seconds). with -f -a 3, i have observed, that the network does not work after resume (under suse 10.1 final it did work) - workaround - manually switch to offline regime and then back to online (this does not work always - once, i was not able to acces the web page www.csadlb.cz (which had been loaded before the suspend to ram) via firefox, although via konqueror it WAS possible - workaround was to restart the computer - after that both browsers were able to view this page) s2ram -f -a 3 works fine under ALT CTRL F1 console under root - i tried it only approx 4 times, but i did not notice any problem. The problem lies probably in X window system (not in hardware). -- 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, or are watching someone who is.