http://bugzilla.novell.com/show_bug.cgi?id=627324 http://bugzilla.novell.com/show_bug.cgi?id=627324#c0 Summary: s2ram on Samsung NC10 fails and takes up 100% of CPU after resume Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: i386 OS/Version: openSUSE 11.3 Status: NEW Severity: Critical Priority: P5 - None Component: Other AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: swesemeyer@hotmail.com QAContact: qa@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.11) Gecko/20100714 SUSE/3.5.11-0.1.1 Firefox/3.5.11 After suspending my Samsung NC10 to ram by either closing the lid or pressing the suspend button, it suspends ok. However on resume, I get a blank screen and nothing happens (ie no password prompt appears). Pressing CTRl+ALT F7 appears to kick-start things a bit but while I can get a console by pressing CTRL+ALT F1-F9, none of them accept keyboard input. Sometimes CTRL+ALT F7 will result in a password prompt and I can unlock my session. However, when checking with top, s2ram uses 100% of the CPU. Reproducible: Always Steps to Reproduce: 1.Login to a KDE session 2.Press suspend button/close lid 3.Press PowerOn button Actual Results: Blank screen and no passowrd prompt displayed ressing CTRL+ALT+F7 followed by a random combination of CTRL+ALT+F1 and CTRL+ALT+F7 will sometimes give a password prompt unlocking the session and using top shows s2ram to run at 100 % KDE Network manager is disabled(bug 552862) Expected Results: password prompt appears s2ram does not use 100% of CPU network is not disabled The way of obtaining the password prompt is somewhat random. When I don't manage to get the prompt a CTRL-BACKSPACE to restart the X server works as well. However, that results in a potential loss of data. Most users will just assume that resume failed and go for a hard reset when no password prompt appears after resuming. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.