Description of problem: On my laptop, a Lenovo Yoga 2 Pro running Fedora 20 with XFCE, something is causing the machine to wake up just after a lid close suspend. Version-Release number of selected component (if applicable): Kernel: 3.12.8-300.fc20.x86_64 Systemd: 208-9.fc20 NetworkManager: 0.9.9.0-28.git20131003.fc20 How reproducible: This is happening quite often, but not all the time. Other people have informally reported the same symptoms. I have seen the bogus wakeups when Wi-Fi is enabled but no connection is active, when Wi-Fi is disabled, and when NetworkManager is not running. If bogus wakeups happen with an active connection, they happen much less often. Steps to Reproduce: 1. Close lid (with no active Wi-Fi connection) Actual results: System suspends, then quickly wakes up again, probably due to some Wi-Fi activity. Expected results: System stays suspended until lid open. Additional info: I grabbed several extracts from the system log for suspend due to a lid-close event and a few for suspend from the menu. They are attached to this report. It appears that something during the lid-close suspend is causing NetworkManager to turn on the Wi-Fi which then appears to be waking up the machine. I would have blamed NetworkManager, but I tried suspending after killing NetworkManager. A lid-close suspend without NetworkManager running causes NetworkManager to be activated, whereas a menu suspend does not. This indicates to me that the problem is somewhere in systemd, maybe in the systemd scripts, so I am assigning this bug to systemd. There are several other bugs related to suspend problems, but this appears to be different, even though I have heard others complaining about the same problem.
Created attachment 858668 [details] system log extracts under various conditions
Hmm? systemd has no control over what causes resumes from suspend. This sounds like a hardware (BIOS) bug, or maybe kernel bug, but systemd certainly not.
OK. I'll dig further.
The resumes may be due to USB activity. At least there is the claim that turning off wakeup-on-activity for the USB hubs prevents the result. https://www.csslayer.info/wordpress/linux/yoga-2-pro-on-linux/ is one place where this claim is made, and I haven't had the inadvertent wakeups since I put this fix in place. Anyway, is there any way to determine the cause of a wakeup?
I'm again asking if there is any way to determine why the Yoga 2 Pro routinely spontaneously wakes up from lid close sleep but doesn't wake up when explicitly put to sleep. There is a workaround - turning off USB wakeups - but why the difference and is there any way to roll the workaround into the distributed system?
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 20 kernel bugs. Fedora 20 has now been rebased to 3.14.4-200.fc20. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you experience different issues, please open a new bug report for those.
*********** MASS BUG UPDATE ************** This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 4 weeks. If you are still experiencing this issue, please reopen and attach the relevant data from the latest kernel you are running and any data that might have been requested previously.