[Solved] Computer suspends twice(!) on lid close

Kernels & Hardware, configuring network, installing services

[Solved] Computer suspends twice(!) on lid close

Postby Hallvor » 2018-09-12 16:37

Suspending from the menu works as expected.

Closing the lid will suspend the computer. The problem is waking it up from suspend. Pressing the power button to wake the computer from suspend will wake it up momentarily, then suspend again.

From the logs you can see that the computer wakes up from suspend, but is then suspended again.

If I disable suspend on lid close in the powersave settings in TDE, suspend will not work (as expected).

Any ideas?

(I am running the Trinity Desktop Environment on Stretch.)

See log below:

Code: Select all
Sep 12 19:04:30 debian-ivarsingamle kernel: [ 5606.864735] PM: resume of devices complete after 2222.973 msecs
Sep 12 19:04:30 debian-ivarsingamle kernel: [ 5606.865183] PM: Finishing wakeup.
Sep 12 19:04:30 debian-ivarsingamle kernel: [ 5606.865186] Restarting tasks ... done.
Sep 12 19:04:31 debian-ivarsingamle kernel: [ 5608.116418] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
Sep 12 19:04:31 debian-ivarsingamle kernel: [ 5608.120425] ata1.00: configured for UDMA/100
Sep 12 19:04:31 debian-ivarsingamle systemd[1]: Time has been changed
Sep 12 19:04:32 debian-ivarsingamle systemd[1]: apt-daily-upgrade.timer: Adding 21min 57.386043s random time.
Sep 12 19:04:32 debian-ivarsingamle systemd[1]: anacron.timer: Adding 2min 21.595239s random time.
Sep 12 19:04:32 debian-ivarsingamle systemd-sleep[3441]: /dev/sda:
Sep 12 19:04:32 debian-ivarsingamle systemd-sleep[3441]:  setting Advanced Power Management level to 0xfe (254)
Sep 12 19:04:32 debian-ivarsingamle systemd-sleep[3441]:  APM_level#011= 254
Sep 12 19:04:32 debian-ivarsingamle systemd[1]: apt-daily.timer: Adding 4h 25min 58.088132s random time.
Sep 12 19:04:32 debian-ivarsingamle systemd[1]: inetd.service: Watchdog timeout (limit 5s)!
Sep 12 19:04:32 debian-ivarsingamle systemd[1]: inetd.service: Killing process 504 (inetd) with signal SIGABRT.
Sep 12 19:04:32 debian-ivarsingamle systemd[1]: inetd.service: Main process exited, code=killed, status=6/ABRT
Sep 12 19:04:32 debian-ivarsingamle systemd[960]: Time has been changed
Sep 12 19:04:32 debian-ivarsingamle systemd[1]: inetd.service: Unit entered failed state.
Sep 12 19:04:32 debian-ivarsingamle systemd[1]: inetd.service: Failed with result 'watchdog'.
Sep 12 19:04:32 debian-ivarsingamle systemd-sleep[3441]: System resumed.
Sep 12 19:04:32 debian-ivarsingamle systemd[1]: inetd.service: Service hold-off time over, scheduling restart.
Sep 12 19:04:32 debian-ivarsingamle systemd[1]: Stopped Internet superserver.
Sep 12 19:04:32 debian-ivarsingamle systemd[1]: Starting Internet superserver...
Sep 12 19:04:32 debian-ivarsingamle systemd[1]: Started Suspend.
Sep 12 19:04:32 debian-ivarsingamle systemd[1]: sleep.target: Unit not needed anymore. Stopping.
Sep 12 19:04:32 debian-ivarsingamle systemd[1]: Stopped target Sleep.
Sep 12 19:04:32 debian-ivarsingamle kernel: [ 5608.407076] IPv6: ADDRCONF(NETDEV_UP): enp1s0f0: link is not ready
Sep 12 19:04:32 debian-ivarsingamle kernel: [ 5608.408154] IPv6: ADDRCONF(NETDEV_UP): enp1s0f0: link is not ready
Sep 12 19:04:32 debian-ivarsingamle kernel: [ 5608.410824] IPv6: ADDRCONF(NETDEV_UP): wlp5s0: link is not ready
Sep 12 19:04:32 debian-ivarsingamle systemd[1]: Reached target Suspend.
Sep 12 19:04:32 debian-ivarsingamle systemd[1]: suspend.target: Unit is bound to inactive unit systemd-suspend.service. Stopping, too.
Sep 12 19:04:32 debian-ivarsingamle systemd[1]: Stopped target Suspend.
Last edited by Hallvor on 2018-09-12 17:52, edited 1 time in total.
HP Elitebook 2570p, Intel Core i5 3320-M CPU @ 2.60 GHz, 6 GB RAM, Intel HD 4000 graphics, 240 GB SSD, Debian Stretch (KDE)
User avatar
Hallvor
 
Posts: 840
Joined: 2009-04-16 18:35
Location: Norway

Re: Computer suspends twice(!) on lid close

Postby Hallvor » 2018-09-12 17:50

I think I just might have solved this one... It works now.

For anyone having the same problem:

Edit /etc/systemd/logind.conf

Change HandleLidSwitch=suspend to HandleLidSwitch=ignore

Save and exit.

Finally:

systemctl restart systemd-logind

Marking thread solved.
HP Elitebook 2570p, Intel Core i5 3320-M CPU @ 2.60 GHz, 6 GB RAM, Intel HD 4000 graphics, 240 GB SSD, Debian Stretch (KDE)
User avatar
Hallvor
 
Posts: 840
Joined: 2009-04-16 18:35
Location: Norway

Re: [Solved] Computer suspends twice(!) on lid close

Postby Head_on_a_Stick » 2018-09-13 16:56

If this happens again, try this command to reveal the inner workings:
Code: Select all
systemd-inhibit
ESTRAGON: We always find something, eh, Didi, to give us the impression we exist?
VLADIMIR (impatiently): Yes, yes, we're magicians.
User avatar
Head_on_a_Stick
 
Posts: 7893
Joined: 2014-06-01 17:46
Location: /dev/chair

Re: [Solved] Computer suspends twice(!) on lid close

Postby Hallvor » 2018-09-14 19:21

Thanks, I'll remember that.
HP Elitebook 2570p, Intel Core i5 3320-M CPU @ 2.60 GHz, 6 GB RAM, Intel HD 4000 graphics, 240 GB SSD, Debian Stretch (KDE)
User avatar
Hallvor
 
Posts: 840
Joined: 2009-04-16 18:35
Location: Norway


Return to System configuration

Who is online

Users browsing this forum: No registered users and 2 guests

fashionable