Description of problem: suspended laptop with closed lid resumes acer aspire v5 573g Version-Release number of selected component (if applicable): kernel 3.14.2-200.fc20.x86_64 How reproducible: often Steps to Reproduce: 1. close lid, laptop suspends 2. wait 3. sometimes, laptop with lid closed is found running Actual results: laptop resumes when I don't want it to. this is really bad as the disk spins when I transport the laptop. Expected results: laptop should stay suspended Additional info: added log
[root@silvia jonathan]# journalctl --since "18:00" -- Logs begin at Sat 2014-04-05 22:11:28 CEST, end at Sun 2014-05-18 22:49:18 CEST. -- May 18 20:57:45 silvia kernel: Freezing user space processes ... (elapsed 0.002 seconds) done. May 18 20:57:45 silvia systemd[1]: Time has been changed May 18 20:57:45 silvia systemd[1499]: Time has been changed May 18 20:57:45 silvia systemd[5089]: Time has been changed May 18 20:57:45 silvia systemd[1759]: Time has been changed May 18 20:57:45 silvia systemd-sleep[12342]: System resumed. May 18 20:57:45 silvia systemd[1]: Service bluetooth.target is not needed anymore. Stopping. May 18 20:57:45 silvia systemd[1]: Stopping Bluetooth. May 18 20:57:45 silvia systemd[1]: Stopped target Bluetooth. May 18 20:57:45 silvia systemd[1]: Starting Bluetooth. May 18 20:57:45 silvia systemd[1]: Reached target Bluetooth. May 18 20:57:45 silvia systemd[1]: Started Suspend. May 18 20:57:45 silvia systemd[1]: Requested transaction contradicts existing jobs: File exists May 18 20:57:45 silvia systemd[1]: Service sleep.target is not needed anymore. Stopping. May 18 20:57:45 silvia systemd-logind[1065]: Operation finished. May 18 20:57:45 silvia kernel: Freezing remaining freezable tasks ... (elapsed 0.000 seconds) done. May 18 20:57:45 silvia bluetoothd[991]: Endpoint unregistered: sender=:1.48 path=/MediaEndpoint/A2DPSourc May 18 20:57:45 silvia bluetoothd[991]: Endpoint unregistered: sender=:1.48 path=/MediaEndpoint/A2DPSink May 18 20:57:45 silvia dbus[1070]: [system] Rejected send message, 4 matched rules; type="error", sender= May 18 20:57:45 silvia dbus[1070]: [system] Rejected send message, 4 matched rules; type="error", sender= May 18 20:57:45 silvia dbus[1070]: [system] Rejected send message, 4 matched rules; type="error", sender= May 18 20:57:45 silvia dbus[1070]: [system] Rejected send message, 4 matched rules; type="error", sender= May 18 20:57:45 silvia bluetoothd[991]: Endpoint registered: sender=:1.48 path=/MediaEndpoint/A2DPSource May 18 20:57:45 silvia bluetoothd[991]: Endpoint registered: sender=:1.48 path=/MediaEndpoint/A2DPSink May 18 20:57:45 silvia NetworkManager[1141]: <info> wake requested (sleeping: yes enabled: yes) May 18 20:57:45 silvia NetworkManager[1141]: <info> waking up and re-enabling... May 18 20:57:45 silvia NetworkManager[1141]: <info> (p3p1): device state change: unmanaged -> unavailable May 18 20:57:45 silvia NetworkManager[1141]: <info> (p3p1): bringing up device. May 18 20:57:45 silvia mcelog[1095]: Hardware event. This is not a software error. May 18 20:57:45 silvia mcelog[1095]: MCE 0 May 18 20:57:45 silvia mcelog[1095]: CPU 0 BANK 5 May 18 20:57:45 silvia mcelog[1095]: MISC 78a0000086 ADDR ffb01fc0 May 18 20:57:45 silvia mcelog[1095]: TIME 1400439463 Sun May 18 20:57:43 2014 May 18 20:57:45 silvia mcelog[1095]: MCG status: May 18 20:57:45 silvia mcelog[1095]: MCi status: May 18 20:57:45 silvia mcelog[1095]: Uncorrected error May 18 20:57:45 silvia mcelog[1095]: MCi_MISC register valid May 18 20:57:45 silvia mcelog[1095]: MCi_ADDR register valid May 18 20:57:45 silvia mcelog[1095]: Processor context corrupt May 18 20:57:45 silvia mcelog[1095]: MCA: corrected filtering (some unreported errors in same region) May 18 20:57:45 silvia mcelog[1095]: Generic CACHE Level-2 Generic Error May 18 20:57:45 silvia mcelog[1095]: STATUS ae0000000040110a MCGSTATUS 0 May 18 20:57:45 silvia mcelog[1095]: MCGCAP c07 APICID 0 SOCKETID 0 May 18 20:57:45 silvia mcelog[1095]: CPUID Vendor Intel Family 6 Model 69 May 18 20:57:45 silvia mcelog[1095]: Hardware event. This is not a software error. May 18 20:57:45 silvia mcelog[1095]: MCE 1 May 18 20:57:45 silvia mcelog[1095]: CPU 0 BANK 6 May 18 20:57:45 silvia mcelog[1095]: MISC 38a0000086 ADDR ffb3ad40 May 18 20:57:45 silvia mcelog[1095]: TIME 1400439463 Sun May 18 20:57:43 2014 May 18 20:57:45 silvia mcelog[1095]: MCG status: May 18 20:57:45 silvia mcelog[1095]: MCi status: May 18 20:57:45 silvia mcelog[1095]: Error overflow May 18 20:57:45 silvia mcelog[1095]: Uncorrected error May 18 20:57:45 silvia mcelog[1095]: MCi_MISC register valid May 18 20:57:45 silvia mcelog[1095]: MCi_ADDR register valid May 18 20:57:45 silvia mcelog[1095]: Processor context corrupt May 18 20:57:45 silvia mcelog[1095]: MCA: corrected filtering (some unreported errors in same region) May 18 20:57:45 silvia mcelog[1095]: Generic CACHE Level-2 Generic Error May 18 20:57:45 silvia mcelog[1095]: STATUS ee0000000040110a MCGSTATUS 0 May 18 20:57:45 silvia mcelog[1095]: MCGCAP c07 APICID 0 SOCKETID 0 May 18 20:57:45 silvia mcelog[1095]: CPUID Vendor Intel Family 6 Model 69 May 18 20:57:45 silvia dbus-daemon[1070]: dbus[1070]: [system] Rejected send message, 4 matched rules; ty May 18 20:57:45 silvia dbus-daemon[1070]: dbus[1070]: [system] Rejected send message, 4 matched rules; ty May 18 20:57:45 silvia dbus-daemon[1070]: dbus[1070]: [system] Rejected send message, 4 matched rules; ty May 18 20:57:45 silvia dbus-daemon[1070]: dbus[1070]: [system] Rejected send message, 4 matched rules; ty May 18 20:57:45 silvia kernel: PM: Entering mem sleep May 18 20:57:45 silvia NetworkManager[1141]: <info> NetworkManager state is now DISCONNECTED May 18 20:57:45 silvia NetworkManager[1141]: <info> (wlp4s0): device state change: unmanaged -> unavailab May 18 20:57:45 silvia NetworkManager[1141]: <info> (wlp4s0): bringing up device. May 18 20:57:45 silvia kernel: Suspending console(s) (use no_console_suspend to debug) May 18 20:57:45 silvia kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache May 18 20:57:45 silvia kernel: sd 0:0:0:0: [sda] Stopping disk May 18 20:57:45 silvia kernel: PM: suspend of devices complete after 1099.511 msecs May 18 20:57:45 silvia kernel: PM: late suspend of devices complete after 0.297 msecs May 18 20:57:45 silvia kernel: pcieport 0000:00:1c.3: System wakeup enabled by ACPI May 18 20:57:45 silvia kernel: ehci-pci 0000:00:1d.0: System wakeup enabled by ACPI May 18 20:57:45 silvia kernel: xhci_hcd 0000:00:14.0: System wakeup enabled by ACPI May 18 20:57:45 silvia kernel: PM: noirq suspend of devices complete after 43.669 msecs May 18 20:57:45 silvia kernel: ACPI: Preparing to enter system sleep state S3 May 18 20:57:45 silvia kernel: PM: Saving platform NVS memory May 18 20:57:45 silvia kernel: Disabling non-boot CPUs ... May 18 20:57:45 silvia kernel: kvm: disabling virtualization on CPU1 May 18 20:57:45 silvia kernel: smpboot: CPU 1 is now offline May 18 20:57:45 silvia kernel: kvm: disabling virtualization on CPU2 May 18 20:57:45 silvia kernel: smpboot: CPU 2 is now offline May 18 20:57:45 silvia kernel: kvm: disabling virtualization on CPU3 May 18 20:57:45 silvia kernel: smpboot: CPU 3 is now offline May 18 20:57:45 silvia kernel: ACPI: Low-level resume complete May 18 20:57:45 silvia kernel: PM: Restoring platform NVS memory May 18 20:57:45 silvia kernel: Enabling non-boot CPUs ... May 18 20:57:45 silvia kernel: x86: Booting SMP configuration: May 18 20:57:45 silvia kernel: smpboot: Booting Node 0 Processor 1 APIC 0x1 May 18 20:57:45 silvia kernel: kvm: enabling virtualization on CPU1 May 18 20:57:45 silvia kernel: Intel pstate controlling: cpu 1 May 18 20:57:45 silvia kernel: CPU1 is up May 18 20:57:45 silvia kernel: smpboot: Booting Node 0 Processor 2 APIC 0x2 May 18 20:57:45 silvia dbus-daemon[1070]: dbus[1070]: [system] Rejected send message, 4 matched rules; ty May 18 20:57:45 silvia kernel: PM: Entering mem sleep May 18 20:57:45 silvia NetworkManager[1141]: <info> NetworkManager state is now DISCONNECTED May 18 20:57:45 silvia NetworkManager[1141]: <info> (wlp4s0): device state change: unmanaged -> unavailab May 18 20:57:45 silvia NetworkManager[1141]: <info> (wlp4s0): bringing up device. May 18 20:57:45 silvia kernel: Suspending console(s) (use no_console_suspend to debug) May 18 20:57:45 silvia kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache May 18 20:57:45 silvia kernel: sd 0:0:0:0: [sda] Stopping disk May 18 20:57:45 silvia kernel: PM: suspend of devices complete after 1099.511 msecs May 18 20:57:45 silvia kernel: PM: late suspend of devices complete after 0.297 msecs May 18 20:57:45 silvia kernel: pcieport 0000:00:1c.3: System wakeup enabled by ACPI May 18 20:57:45 silvia kernel: ehci-pci 0000:00:1d.0: System wakeup enabled by ACPI May 18 20:57:45 silvia kernel: xhci_hcd 0000:00:14.0: System wakeup enabled by ACPI May 18 20:57:45 silvia kernel: PM: noirq suspend of devices complete after 43.669 msecs May 18 20:57:45 silvia kernel: ACPI: Preparing to enter system sleep state S3 May 18 20:57:45 silvia kernel: PM: Saving platform NVS memory May 18 20:57:45 silvia kernel: Disabling non-boot CPUs ... May 18 20:57:45 silvia kernel: kvm: disabling virtualization on CPU1 May 18 20:57:45 silvia kernel: smpboot: CPU 1 is now offline May 18 20:57:45 silvia kernel: kvm: disabling virtualization on CPU2 May 18 20:57:45 silvia kernel: smpboot: CPU 2 is now offline May 18 20:57:45 silvia kernel: kvm: disabling virtualization on CPU3 May 18 20:57:45 silvia kernel: smpboot: CPU 3 is now offline May 18 20:57:45 silvia kernel: ACPI: Low-level resume complete May 18 20:57:45 silvia kernel: PM: Restoring platform NVS memory May 18 20:57:45 silvia kernel: Enabling non-boot CPUs ... May 18 20:57:45 silvia kernel: x86: Booting SMP configuration: May 18 20:57:45 silvia kernel: smpboot: Booting Node 0 Processor 1 APIC 0x1 May 18 20:57:45 silvia kernel: kvm: enabling virtualization on CPU1 May 18 20:57:45 silvia kernel: Intel pstate controlling: cpu 1 May 18 20:57:45 silvia kernel: CPU1 is up May 18 20:57:45 silvia kernel: smpboot: Booting Node 0 Processor 2 APIC 0x2 May 18 20:57:45 silvia kernel: kvm: enabling virtualization on CPU2 May 18 20:57:45 silvia kernel: Intel pstate controlling: cpu 2 May 18 20:57:45 silvia kernel: CPU2 is up May 18 20:57:45 silvia kernel: smpboot: Booting Node 0 Processor 3 APIC 0x3 May 18 20:57:45 silvia kernel: kvm: enabling virtualization on CPU3 May 18 20:57:45 silvia kernel: Intel pstate controlling: cpu 3 May 18 20:57:45 silvia kernel: CPU3 is up May 18 20:57:45 silvia kernel: ACPI: Waking up from system sleep state S3 May 18 20:57:45 silvia kernel: xhci_hcd 0000:00:14.0: System wakeup disabled by ACPI May 18 20:57:45 silvia kernel: ACPI: \_SB_.ACAD: ACPI_NOTIFY_BUS_CHECK event May 18 20:57:45 silvia kernel: ehci-pci 0000:00:1d.0: System wakeup disabled by ACPI May 18 20:57:45 silvia kernel: PM: noirq resume of devices complete after 110.046 msecs May 18 20:57:45 silvia kernel: PM: early resume of devices complete after 0.117 msecs May 18 20:57:45 silvia kernel: usb usb2: root hub lost power or was reset May 18 20:57:45 silvia kernel: usb usb3: root hub lost power or was reset May 18 20:57:45 silvia kernel: snd_hda_intel 0000:00:03.0: irq 61 for MSI/MSI-X May 18 20:57:45 silvia kernel: xhci_hcd 0000:00:14.0: irq 64 for MSI/MSI-X May 18 20:57:45 silvia kernel: mei_me 0000:00:16.0: irq 66 for MSI/MSI-X May 18 20:57:45 silvia kernel: pcieport 0000:00:1c.3: System wakeup disabled by ACPI May 18 20:57:45 silvia kernel: snd_hda_intel 0000:00:1b.0: irq 67 for MSI/MSI-X May 18 20:57:45 silvia kernel: dpm_run_callback(): pnp_bus_resume+0x0/0xa0 returns -19 May 18 20:57:45 silvia kernel: PM: Device 00:06 failed to resume: error -19 May 18 20:57:45 silvia kernel: usb 1-1: reset high-speed USB device number 2 using ehci-pci May 18 20:57:45 silvia kernel: usb 2-5: reset low-speed USB device number 4 using xhci_hcd May 18 20:57:45 silvia kernel: xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep fff May 18 20:57:45 silvia kernel: xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep fff May 18 20:57:45 silvia kernel: usb 2-5: ep 0x81 - rounding interval to 64 microframes, ep desc says 80 mi May 18 20:57:45 silvia kernel: usb 2-5: ep 0x82 - rounding interval to 64 microframes, ep desc says 80 mi May 18 20:57:45 silvia kernel: usb 2-4: reset full-speed USB device number 3 using xhci_hcd May 18 20:57:45 silvia kernel: xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep fff May 18 20:57:45 silvia kernel: xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep fff May 18 20:57:45 silvia kernel: xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep fff May 18 20:57:45 silvia kernel: xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep fff May 18 20:57:45 silvia kernel: xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep fff May 18 20:57:45 silvia kernel: xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep fff May 18 20:57:45 silvia kernel: xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep fff May 18 20:57:45 silvia kernel: usb 2-3: reset high-speed USB device number 2 using xhci_hcd May 18 20:57:45 silvia kernel: xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep fff May 18 20:57:45 silvia kernel: [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off May 18 20:57:45 silvia kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300) May 18 20:57:45 silvia kernel: ata1.00: configured for UDMA/100 May 18 20:57:45 silvia kernel: sd 0:0:0:0: [sda] Starting disk May 18 20:57:45 silvia kernel: PM: resume of devices complete after 2185.691 msecs May 18 20:57:45 silvia kernel: PM: Finishing wakeup. May 18 20:57:45 silvia kernel: Restarting tasks ... May 18 20:57:45 silvia kernel: wl 0000:04:00.0: no hotplug settings from platform May 18 20:57:45 silvia kernel: rtsx_pci 0000:05:00.0: no hotplug settings from platform May 18 20:57:45 silvia kernel: r8169 0000:05:00.1: no hotplug settings from platform May 18 20:57:45 silvia kernel: pci 0000:01:00.0: no hotplug settings from platform May 18 20:57:45 silvia kernel: pci_bus 0000:02: Allocating resources May 18 20:57:45 silvia kernel: pci_bus 0000:04: Allocating resources May 18 20:57:45 silvia kernel: pci_bus 0000:05: Allocating resources May 18 20:57:45 silvia kernel: pci_bus 0000:01: Allocating resources May 18 20:57:45 silvia kernel: i915 0000:00:02.0: BAR 6: [??? 0x00000000 flags 0x2] has bogus alignment May 18 20:57:45 silvia kernel: done. May 18 20:57:45 silvia kernel: pci 0000:00:00.0: no hotplug settings from platform May 18 20:57:45 silvia kernel: pci 0000:00:00.0: using default PCI settings May 18 20:57:45 silvia kernel: i915 0000:00:02.0: no hotplug settings from platform May 18 20:57:45 silvia kernel: i915 0000:00:02.0: using default PCI settings May 18 20:57:45 silvia kernel: snd_hda_intel 0000:00:03.0: no hotplug settings from platform May 18 20:57:45 silvia kernel: xhci_hcd 0000:00:14.0: no hotplug settings from platform May 18 20:57:45 silvia kernel: xhci_hcd 0000:00:14.0: using default PCI settings May 18 20:57:45 silvia kernel: mei_me 0000:00:16.0: no hotplug settings from platform May 18 20:57:45 silvia kernel: mei_me 0000:00:16.0: using default PCI settings May 18 20:57:45 silvia kernel: snd_hda_intel 0000:00:1b.0: no hotplug settings from platform May 18 20:57:45 silvia kernel: pcieport 0000:00:1c.0: no hotplug settings from platform May 18 20:57:45 silvia kernel: pcieport 0000:00:1c.2: no hotplug settings from platform May 18 20:57:45 silvia kernel: wl 0000:04:00.0: no hotplug settings from platform
I have an Acer Aspire V5-573G too and caught it running with closed lid once. I'm not sure if I accidentally pressed the power button (which can easily happen when grabbing the laptop. I'll keep an eye on it. At the same time I noticed a couple of MCE too while the laptop is running and this worries me most as it probably indicates a hardware issue: May 31 12:58:07 mimas mcelog: Hardware event. This is not a software error. May 31 12:58:07 mimas mcelog: MCE 0 May 31 12:58:07 mimas mcelog: CPU 0 BANK 6 May 31 12:58:07 mimas mcelog: MISC 78a0000086 ADDR ffb06d00 May 31 12:58:07 mimas mcelog: TIME 1401533870 Sat May 31 12:57:50 2014 May 31 12:58:07 mimas mcelog: MCG status: May 31 12:58:07 mimas mcelog: MCi status: May 31 12:58:07 mimas mcelog: Uncorrected error May 31 12:58:07 mimas mcelog: MCi_MISC register valid May 31 12:58:07 mimas mcelog: MCi_ADDR register valid May 31 12:58:07 mimas mcelog: Processor context corrupt May 31 12:58:07 mimas mcelog: MCA: corrected filtering (some unreported errors in same region) May 31 12:58:07 mimas mcelog: Generic CACHE Level-2 Generic Error May 31 12:58:07 mimas mcelog: STATUS ae0000000040110a MCGSTATUS 0 May 31 12:58:07 mimas mcelog: MCGCAP c07 APICID 0 SOCKETID 0 May 31 12:58:07 mimas mcelog: CPUID Vendor Intel Family 6 Model 69
Glad to have someone to discuss this with :-) I suspected the power button at first as well as it is placed where it is easy to accidently push. However, when I press it on purpose with the lid closed, the laptop does not power up. Also, I often store it where there is no risk of pushing the power button and find it running or with the battery drained. I have been considering that it does succeed to suspend as this is a common linux problem but the fans and disk go silent and the power LED indicates suspend so I think it really suspends fully. Something makes it resume later and I have no idea what. Any ideas would be appreciated. I have problems with the drivers for network and memory card readers as well.
Can you post the output of "lspci"?
$ lspci 00:00.0 Host bridge: Intel Corporation Haswell-ULT DRAM Controller (rev 09) 00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated Graphics Controller (rev 09) 00:03.0 Audio device: Intel Corporation Haswell-ULT HD Audio Controller (rev 09) 00:14.0 USB controller: Intel Corporation 8 Series USB xHCI HC (rev 04) 00:16.0 Communication controller: Intel Corporation 8 Series HECI #0 (rev 04) 00:1b.0 Audio device: Intel Corporation 8 Series HD Audio Controller (rev 04) 00:1c.0 PCI bridge: Intel Corporation 8 Series PCI Express Root Port 1 (rev e4) 00:1c.2 PCI bridge: Intel Corporation 8 Series PCI Express Root Port 3 (rev e4) 00:1c.3 PCI bridge: Intel Corporation 8 Series PCI Express Root Port 4 (rev e4) 00:1c.4 PCI bridge: Intel Corporation 8 Series PCI Express Root Port 5 (rev e4) 00:1d.0 USB controller: Intel Corporation 8 Series USB EHCI #1 (rev 04) 00:1f.0 ISA bridge: Intel Corporation 8 Series LPC Controller (rev 04) 00:1f.2 SATA controller: Intel Corporation 8 Series SATA Controller 1 [AHCI mode] (rev 04) 00:1f.3 SMBus: Intel Corporation 8 Series SMBus Controller (rev 04) 01:00.0 3D controller: NVIDIA Corporation GK107M [GeForce GT 750M] (rev ff) 04:00.0 Network controller: Broadcom Corporation BCM43228 802.11a/b/g/n 05:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. Device 5287 (rev 01) 05:00.1 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 14)
The lspci output is mostly different from what I have. Can you post "lspci -n" just to rule out naming differences? My laptop woke up a couple of hours ago for no apparent reason (after 20h suspend in S3 state with charger attached) so this confirms the issue. Kernel used: pristine 3.14.5, 64 bit, built using the kernel .config from the F20 kernel package). I also did some burn-in testing (9 kernel builds in parallel with -j8 to get enough cache pressure) to check for RAM and hardware tolerance issues: found none (No oops, segfault or any gcc error). What _might_ help as a workaround is to switch off WOL (Wake On Lan, check BIOS).
I've already switched off WOL as I don't use it and thought it might be a source of problems. I'm on BIOS 2.25
$ lspci -n 00:00.0 0600: 8086:0a04 (rev 09) 00:02.0 0300: 8086:0a16 (rev 09) 00:03.0 0403: 8086:0a0c (rev 09) 00:14.0 0c03: 8086:9c31 (rev 04) 00:16.0 0780: 8086:9c3a (rev 04) 00:1b.0 0403: 8086:9c20 (rev 04) 00:1c.0 0604: 8086:9c10 (rev e4) 00:1c.2 0604: 8086:9c14 (rev e4) 00:1c.3 0604: 8086:9c16 (rev e4) 00:1c.4 0604: 8086:9c18 (rev e4) 00:1d.0 0c03: 8086:9c26 (rev 04) 00:1f.0 0601: 8086:9c43 (rev 04) 00:1f.2 0106: 8086:9c03 (rev 04) 00:1f.3 0c05: 8086:9c22 (rev 04) 01:00.0 0302: 10de:0fe4 (rev ff) 04:00.0 0280: 14e4:4359 05:00.0 ff00: 10ec:5287 (rev 01) 05:00.1 0200: 10ec:8168 (rev 14)
Hardware is mostly the same (differences: I have NVIDIA GF117M and AR9462 WiFi). The spontaneous wakeup isn't probably that spontaneous: I've seen it twice at exactly the same time of day (11:44:27 UTC) which suggests an incorrectly initialized RTC chip, leaving a daily alarm on. This needs some searching and kernel (rtc_cmos) digging.
Interesting. I've also come to believe that the wakeups occur at specific times, but it seems to have happened at several times. Do you know of anything to look for in the logs? Or would that be outside of the logging service?
As root, try journalctl | grep 'Restoring platform' and look for timestamps which do not correspond with intentional wakeups. After a spontaneous wakeup (but before the next suspend) you can just type "journalctl" and scroll back to see when it has woken up (note: I got fed up with this systemd "assimilation project" and installed syslog-ng to get /var/log/messages back, configured world-readable).
Can you post the output of "cat /proc/driver/rtc"?
$ cat /proc/driver/rtc rtc_time : 12:51:29 rtc_date : 2014-06-06 alrm_time : 11:39:21 alrm_date : 2014-06-05 alarm_IRQ : no alrm_pending : no update IRQ enabled : no periodic IRQ enabled : no periodic IRQ frequency : 1024 max user IRQ frequency : 64 24hr : yes periodic_IRQ : no update_IRQ : no HPET_emulated : yes BCD : yes DST_enable : no periodic_freq : 1024 batt_status : okay
I ran some simple analysis on "journalctl | grep 'Restoring platform'" There were consistent streaks of daily wakeups that could be consistent for up to one week.
Created attachment 908812 [details] script, calls pm-suspend when laptop appears to be closed Install this in /root and (as root) install a crontab entry such as 0-59/5 * * * * /root/suspend-if-closed to mitigate the issue.
Great, thanks. Just to test if I understood this, your suggested crontab calls the script every 5 minutes when the system is active and checks if the lid is closed, and if it is, it enforces the suspend?
Yes. And when the suspend is enforced via cron then root will receive a mail. But note that the script will race against suspend by the system itself when the lid is closed so occasionally you will see a mail while there was no spontaneous wakeup involved.
A couple of days ago I experimented with "rtcwake" and /sys/class/rtc/rtc0/wakealarm. After that I used the laptop a couple of times. Today the system woke up for no reason, exactly 24h after the last manual wakeup (opening the lid and starting to type at that time). Nothing happened in between. There's no correlation with any earlier experiment with respect to the time of day and /proc/driver/rtc still shows a >48h old alarm (not active). I have a second cronjob to catch any program playing games with the RTC alarm (using /proc/driver/rtc) and didn't find any. So, maybe the RTC hardware is not a factor at all.
Is the OS aware of why it woke up? Like does it know if it was triggered to resume by lid, button, LAN, RTC-alarm or something else? Or is that information never passed or stored?
My problem with my acer aspire v5-531 is that I set the computer to'do nothing' when I close the lid. I use this feature when I want to play audio on the notebook but not have the light from the screen when i am sleeping. When i close the lid suddenly all kinds of things start happening and applications open from nowhere and the music in media player jumps to odd tracks. I think its a really really bad design as when the notebook is off, I can see imprints of the keyboard on the monitor so obviously when it's closed all the keys stay active and get pressed, really annoying!!!
*********** 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.17.2-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 have moved on to Fedora 21, and are still experiencing this issue, please change the version to Fedora 21. If you experience different issues, please open a new bug report for those.
The issue is still present on an up to date F20 laptop running a stock 3.17.2 kernel (from www.kernel.org and built on the same system). The 24h spontaneous wakeup period appears to be always in sync with the very first suspend (lid close or "pm-suspend") after a kernel boot.
I got the same problem on Lenovo X201i on 3.17.8-200.fc20.x86_64. It seems that a known wifi network nearby triggers the wake up. My laptop wakes up around the time I come home or to work. The power button on the X201i is under the lid, so I could not press it accidentally. journalctl: led 14 00:28:17 pmd85 kernel: PM: Syncing filesystems ... done. led 14 10:38:40 pmd85 kernel: PM: Preparing system for mem sleep led 14 10:38:40 pmd85 systemd[1]: Time has been changed led 14 10:38:40 pmd85 systemd[1384]: Time has been changed led 14 10:38:40 pmd85 systemd[1771]: Time has been changed led 14 10:38:40 pmd85 systemd[7709]: Time has been changed led 14 10:38:40 pmd85 systemd-sleep[6570]: System resumed. led 14 10:38:40 pmd85 systemd[1]: Unit bluetooth.target is not needed anymore. Stopping. led 14 10:38:40 pmd85 systemd[1]: Stopping Bluetooth. led 14 10:38:40 pmd85 systemd[1]: Stopped target Bluetooth. led 14 10:38:40 pmd85 systemd[1]: Started Suspend. led 14 10:38:40 pmd85 systemd[1]: Unit sleep.target is not needed anymore. Stopping. led 14 10:38:40 pmd85 systemd[1]: Stopping Sleep. led 14 10:38:40 pmd85 systemd[1]: Stopped target Sleep. led 14 10:38:40 pmd85 systemd[1]: Starting Suspend. led 14 10:38:44 pmd85 systemd-logind[840]: Operation finished. led 14 10:38:44 pmd85 kernel: Freezing user space processes ... (elapsed 0.002 seconds) done. led 14 10:38:44 pmd85 NetworkManager[991]: <info> wake requested (sleeping: yes enabled: yes) led 14 10:38:44 pmd85 NetworkManager[991]: <info> waking up and re-enabling... led 14 10:38:44 pmd85 NetworkManager[991]: <info> (em1): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2] led 14 10:38:44 pmd85 NetworkManager[991]: <info> (em1): bringing up device.
*********** 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.18.7-100.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 have moved on to Fedora 21, and are still experiencing this issue, please change the version to Fedora 21. If you experience different issues, please open a new bug report for those.
*********** 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 21 kernel bugs. Fedora 21 has now been rebased to 3.19.5-200.fc21. 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 22, and are still experiencing this issue, please change the version to Fedora 22. If you experience different issues, please open a new bug report for those.
I have the same problem on Fedora 22 with kernel 4.1.3-201 and systemd 219 on a Fujitsu Lifebook AH532. Willing to provide other details.
(In reply to Tom Johnson from comment #26) > I have the same problem on Fedora 22 with kernel 4.1.3-201 and systemd 219 > on a Fujitsu Lifebook AH532. Willing to provide other details. I have same with that kernel on Thinkpad S3 Yoga 14, it wont suspend on lid closed event. Running 'systemctl suspend' works correctly though.
(In reply to Nick Byrne from comment #27) > I have same with that kernel on Thinkpad S3 Yoga 14, it wont suspend on lid > closed event. Running 'systemctl suspend' works correctly though. The issue is spontaneous wakeups every 24h when lid is closed. When your system does not suspend upon closing the lid then that's a different issue.
This message is a reminder that Fedora 21 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 21. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '21'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 21 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.