Description of problem: With Fedora 24, kernel 4.6.4 Linux cba 4.6.4-301.fc24.x86_64 #1 SMP Tue Jul 12 11:50:00 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux When WOWLAN is enabled (wake on wireless LAN), the system fails to suspend to RAM: the journal shows: (journalctl -r): Aug 01 18:29:46 cba kernel: PM: Some devices failed to suspend, or early wake event detected Aug 01 18:29:46 cba kernel: sd 1:0:0:0: [sda] Stopping disk Aug 01 18:29:46 cba kernel: PM: Device phy0 failed to suspend async: error -16 Aug 01 18:29:46 cba kernel: dpm_run_callback(): wiphy_suspend+0x0/0x240 [cfg80211] returns -16 After the wifi-related error, the system stops the suspend process and gnome-shell shows the lock screen. This was working fine with Fedora 21, 22, 23, up until at least kernel 4.5.7, Linux abc 4.5.7-200.fc23.x86_64 #1 SMP Wed Jun 8 17:41:50 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux I could workaround this problem by disabling WOWLAN in the Fedora 24 box: sudo iw phy phy0 wowlan disable magic-packet Version-Release number of selected component (if applicable): Kernel 4.6.4 WiFi HW & driver info (lshw) *-network description: Wireless interface product: Wireless 7260 vendor: Intel Corporation physical id: 0 bus info: pci@0000:01:00.0 logical name: wlp1s0 version: 73 serial: d8:fc:xx:xx:xx:xx width: 64 bits clock: 33MHz capabilities: bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=iwlwifi driverversion=4.6.4-301.fc24.x86_64 firmware=16.242414.0 ip=192.168.x.x latency=0 link=yes multicast=yes wireless=IEEE 802.11abgn resources: irq:132 memory:df100000-df101fff How reproducible: Every time. Steps to Reproduce: 1. Enable WOWLAN sudo iw phy phy0 wowlan enable magic-packet 2. attempt to suspend the system (systemctl suspend) 3. Actual results: after a few seconds, gnome-shell displays the lock screen Expected results: system should suspend Additional info: I found a kernel bug from late last year that seems related: https://bugzilla.kernel.org/show_bug.cgi?id=109591 Wondering if Fedora 24 kernel is missing that patch.
*********** 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 24 kernel bugs. Fedora 24 has now been rebased to 4.7.4-200.fc24. 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 have moved on to Fedora 25, and are still experiencing this issue, please change the version to Fedora 25. If you experience different issues, please open a new bug report for those.
Re-tested with the latest fedora 24 kernel Linux cba 4.7.5-200.fc24.x86_64 #1 SMP Mon Sep 26 21:25:47 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux Doing: sudo iw phy phy0 wowlan enable magic-packet $ iw phy phy0 wowlan show WoWLAN is enabled: * wake up on magic packet Attempting to suspend the system fails, and produces the exact same issue as described in the bug description. So no change at all with the newest kernel. Oct 04 09:57:45 cba kernel: PM: Some devices failed to suspend, or early wake event detected Oct 04 09:57:45 cba kernel: PM: Device phy0 failed to suspend async: error -16 Oct 04 09:57:45 cba kernel: dpm_run_callback(): wiphy_suspend+0x0/0x250 [cfg80211] returns -16
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There are 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 24 kernel bugs. Fedora 25 has now been rebased to 4.10.9-100.fc24. 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 have moved on to Fedora 26, and are still experiencing this issue, please change the version to Fedora 26. 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 2 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.