You are not logged in.

#1 2018-01-17 16:27:35

samhh
Member
Registered: 2017-12-25
Posts: 18

[SOLVED] Laptop suspend immediately resumes

When I suspend with `systemctl suspend` the system resumes only a few seconds later without me touching anything and with no peripherals attached (laptop - MBP). Some logs:

systemctl status systemd-suspend:

Loaded: loaded (/usr/lib/systemd/system/systemd-suspend.service; static; vendor preset: disabled)
Active: inactive (dead)

Jan 17 16:14:19 username systemd[1]: Starting Suspend...
Jan 17 16:14:19 username systemd-sleep[14973]: Suspending system...
Jan 17 16:14:29 username systemd-sleep[14973]: System resumed.
Jan 17 16:14:29 username systemd[1]: Started Suspend.

dmesg:

[203540.514292] brcmfmac: brcmf_inetaddr_changed: fail to get arp ip table err:-23
[203541.028418] IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready
[203541.600284] PM: suspend entry (deep)
[203541.600286] PM: Syncing filesystems ... done.
[203541.646729] Freezing user space processes ... (elapsed 0.012 seconds) done.
[203541.658850] OOM killer disabled.
[203541.658850] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
[203541.660420] Suspending console(s) (use no_console_suspend to debug)
[203541.660825] sd 0:0:0:0: [sda] Synchronizing SCSI cache
[203541.660877] sd 0:0:0:0: [sda] Stopping disk
[203542.982294] thunderbolt 0000:07:00.0: suspending...
[203542.983084] thunderbolt 0000:07:00.0: suspend finished
[203542.983086] thunderbolt 0000:07:00.0: stopping RX ring 0
[203542.983093] thunderbolt 0000:07:00.0: disabling interrupt at register 0x38200 bit 12 (0x1001 -> 0x1)
[203542.983104] thunderbolt 0000:07:00.0: stopping TX ring 0
[203542.983110] thunderbolt 0000:07:00.0: disabling interrupt at register 0x38200 bit 0 (0x1 -> 0x0)
[203542.983120] thunderbolt 0000:07:00.0: control channel stopped
[203543.942910] ACPI: Preparing to enter system sleep state S3
[203543.995385] ACPI: EC: event blocked
[203543.995386] ACPI: EC: EC stopped
[203543.995387] PM: Saving platform NVS memory
[203543.995393] Disabling non-boot CPUs ...
[203544.024251] smpboot: CPU 1 is now offline
[203544.053677] smpboot: CPU 2 is now offline
[203544.086985] smpboot: CPU 3 is now offline
[203544.116933] smpboot: CPU 4 is now offline
[203544.153523] smpboot: CPU 5 is now offline
[203544.193499] smpboot: CPU 6 is now offline
[203544.210189] smpboot: CPU 7 is now offline
[203544.239030] ACPI: Low-level resume complete
[203544.239090] ACPI: EC: EC started
[203544.239090] PM: Restoring platform NVS memory
[203544.241491] Enabling non-boot CPUs ...
[203544.241541] x86: Booting SMP configuration:
[203544.241542] smpboot: Booting Node 0 Processor 1 APIC 0x2
[203544.345291]  cache: parent cpu1 should not be sleeping
[203544.525497] CPU1 is up
[203544.525541] smpboot: Booting Node 0 Processor 2 APIC 0x4
[203544.620567]  cache: parent cpu2 should not be sleeping
[203544.805466] CPU2 is up
[203544.805510] smpboot: Booting Node 0 Processor 3 APIC 0x6
[203544.899067]  cache: parent cpu3 should not be sleeping
[203545.086725] CPU3 is up
[203545.086775] smpboot: Booting Node 0 Processor 4 APIC 0x1
[203545.093524]  cache: parent cpu4 should not be sleeping
[203545.093727] CPU4 is up
[203545.093755] smpboot: Booting Node 0 Processor 5 APIC 0x3
[203545.172233]  cache: parent cpu5 should not be sleeping
[203545.369820] CPU5 is up
[203545.369848] smpboot: Booting Node 0 Processor 6 APIC 0x5
[203545.452960]  cache: parent cpu6 should not be sleeping
[203545.690885] CPU6 is up
[203545.690912] smpboot: Booting Node 0 Processor 7 APIC 0x7
[203545.775457]  cache: parent cpu7 should not be sleeping
[203546.048792] CPU7 is up
[203546.129923] ACPI: Waking up from system sleep state S3
[203546.221033] pcieport 0000:06:04.0: quirk: waiting for thunderbolt to reestablish PCI tunnels...
[203546.221044] pcieport 0000:06:06.0: quirk: waiting for thunderbolt to reestablish PCI tunnels...
[203546.221046] pcieport 0000:06:05.0: quirk: waiting for thunderbolt to reestablish PCI tunnels...
[203546.221054] pcieport 0000:06:03.0: quirk: waiting for thunderbolt to reestablish PCI tunnels...
[203546.237170] thunderbolt 0000:07:00.0: control channel starting...
[203546.237172] thunderbolt 0000:07:00.0: starting TX ring 0
[203546.237186] thunderbolt 0000:07:00.0: enabling interrupt at register 0x38200 bit 0 (0x0 -> 0x1)
[203546.237188] thunderbolt 0000:07:00.0: starting RX ring 0
[203546.237202] thunderbolt 0000:07:00.0: enabling interrupt at register 0x38200 bit 12 (0x1 -> 0x1001)
[203546.237205] thunderbolt 0000:07:00.0: resuming...
[203546.237206] thunderbolt 0000:07:00.0: resetting switch at 0
[203546.237749] thunderbolt 0000:07:00.0: 0: resuming switch
[203546.268745] thunderbolt 0000:07:00.0: resume finished
[203546.338354] thunderbolt 0000:07:00.0: resetting error on 0:b.
[203546.338366] thunderbolt 0000:07:00.0: 0:b: hotplug: scanning
[203546.338367] thunderbolt 0000:07:00.0: resetting error on 0:c.
[203546.338368] thunderbolt 0000:07:00.0: 0:b: hotplug: no switch found
[203546.338370] thunderbolt 0000:07:00.0: 0:c: hotplug: scanning
[203546.338371] thunderbolt 0000:07:00.0: 0:c: hotplug: no switch found
[203547.331026] ACPI: EC: event unblocked
[203547.331167] brcmfmac: brcmf_fil_cmd_data: bus is down. we have nothing to do.
[203547.331171] brcmfmac: brcmf_fil_cmd_data: bus is down. we have nothing to do.
[203547.331361] brcmfmac: brcmf_fil_cmd_data: bus is down. we have nothing to do.
[203547.331363] brcmfmac: brcmf_cfg80211_get_channel: chanspec failed (-5)
[203547.351394] sd 0:0:0:0: [sda] Starting disk
[203547.436948] pciehp 0000:06:00.0:pcie204: Device 0000:07:00.0 already exists at 0000:07:00, cannot hot-add
[203547.436951] pciehp 0000:06:00.0:pcie204: Cannot add device at 0000:07:00
[203547.510684] brcmfmac: brcmf_fw_map_chip_to_name: using brcm/brcmfmac43602-pcie.bin for chip 0x00aa52(43602) rev 0x000001
[203547.510728] brcmfmac 0000:03:00.0: Direct firmware load for brcm/brcmfmac43602-pcie.txt failed with error -2
[203547.684046] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[203547.684280] ata1.00: unexpected _GTF length (8)
[203547.684712] ata1.00: unexpected _GTF length (8)
[203547.684842] ata1.00: configured for UDMA/133
[203547.763471] OOM killer enabled.
[203547.763472] Restarting tasks ... done.
[203547.880622] video LNXVIDEO:00: Restoring backlight state
[203547.880764] PM: suspend exit
[203548.000087] brcmfmac: brcmf_c_preinit_dcmds: Firmware version = wl0: Nov 10 2015 06:38:10 version 7.35.177.61 (r598657) FWID 01-ea662a8c
[203548.044971] brcmfmac 0000:03:00.0 wlp3s0: renamed from wlan0
[203548.087975] IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready
[203548.131324] IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready
[203548.656922] IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready
[203548.742492] brcmfmac: brcmf_p2p_create_p2pdev: set p2p_disc error
[203548.742498] brcmfmac: brcmf_cfg80211_add_iface: add iface p2p-dev-wlp3s0 type 10 failed: err=-16
[203548.745078] IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready
[203551.857054] IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready
[203557.475239] IPv6: ADDRCONF(NETDEV_CHANGE): wlp3s0: link becomes ready

Also the screen backlight always seems to be reset to a lower value upon waking, though that's potentially unrelated.

Any ideas? Thanks!

Last edited by samhh (2018-01-21 00:30:48)

Offline

#2 2018-01-18 14:51:11

thisischuck
Member
Registered: 2018-01-18
Posts: 1

Re: [SOLVED] Laptop suspend immediately resumes

While I am somewhat of a newbie myself, I think I found the solution to your issue.  The systemctl command doesn't run all of the hooks that are connected to `sleeping` a laptop that we're looking for.  Using the power management utilities `pm-utils` might be the solution there.

Additionally, it could be that you've got something like Wake-on-lan enabled, and access to the network is causing an automatic wake up: https://wiki.archlinux.org/index.php/Wake-on-LAN

Let me know if either of these work!

Offline

#3 2018-01-18 16:36:54

chicha
Member
From: France
Registered: 2007-04-20
Posts: 271

Re: [SOLVED] Laptop suspend immediately resumes

Hello,

You can maybe consider this issue on the power management wiki page. Also systemd suspend/hibernate can conflict with your desktop environment.

To eliminate the latter I would jump to a TTY, stop your desktop environment and session manager (gdm, kdm, ...) and run the systemctl suspend again to see if the conflict is due to the desktop environment. This was the case for me with gdm+gnome: I just do not use systemctl suspend and let Gnome do the job when I close the lid, or using the suspend button.

Offline

#4 2018-01-21 00:30:29

samhh
Member
Registered: 2017-12-25
Posts: 18

Re: [SOLVED] Laptop suspend immediately resumes

Aha, it appears to be the first issue you posted chicha! Although in my case it was "LID0" causing it.

Thanks guys!! :-)

Offline

Board footer

Powered by FluxBB