https://bugzilla.novell.com/show_bug.cgi?id=878720 https://bugzilla.novell.com/show_bug.cgi?id=878720#c0 Summary: Dell Precision 4700 re-suspends after resume from s2ram Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: x86-64 OS/Version: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: geoff@cs.hmc.edu QAContact: qa-bugs@suse.de Found By: --- Blocker: --- Created an attachment (id=590931) --> (http://bugzilla.novell.com/attachment.cgi?id=590931) Log file from first suspend/resume User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:29.0) Gecko/20100101 Firefox/29.0 Note: this may be related to Bug 639152. When I suspend my Dell Precision M4700 to RAM by closing the lid and then open the lid again, it resumes just fine. Then 3 to 10 seconds later it suspends again. If I then resume by pressing the power button, it comes alive and works perfectly. It's only a minor nuisance (except when I'm too eager on the power button and initiate shutdown instead!) but it would be nice to see it fixed. About 1 time in 20 it doesn't happen. I was able to capture both pm-suspend.log files by copying the first one during the few seconds before the machine re-suspended. Both are attached. Reproducible: Always Steps to Reproduce: 1. Close lid and wait for suspend. 2. Open lid and wait a few seconds. Actual Results: Laptop re-suspends after step 2. Expected Results: After resume, laptop remains powered on. The ".old" log file is from the first suspend. Looking at the end of the first log and the beginning of the second, it's not clear *why* the suspend was initiated. My best guess is that the "lid closed" signal from the first suspend isn't properly cleared, but that's only a guess. Hmmm...looks like Bugzilla will only allow one attachment. This is the "old" log file. I'll try to add the new one in a separate comment. -- 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.