Suspend stopped working since a few days


#1

Since a few days suspend does not work. Two display flashes , then the system is back on again. Here is what I have unsuccessfully tried so far to correct this:

  • Script provided in this post.
  • Downgrading Kernel to 416 (and also to 414).

Here is output of journalctl -b -g suspend

[tomas@pc ~]$ journalctl -b -g suspend
– Logs begin at Fri 2018-12-07 06:36:34 CET, end at Fri 2018-12-07 08:21:07 CE>
dec 07 06:36:45 pc /usr/lib/gdm-x-session[614]: (II) AIGLX: Suspending AIGLX cl>
dec 07 07:40:00 pc systemd[1]: Starting TLP suspend/resume…
dec 07 07:40:01 pc systemd[1]: Started TLP suspend/resume.
dec 07 07:40:01 pc systemd[1]: Starting Suspend…
dec 07 07:40:01 pc systemd-sleep[2543]: Suspending system…
dec 07 07:40:01 pc kernel: PM: suspend entry (deep)
dec 07 07:40:02 pc kernel: Suspending console(s) (use no_console_suspend to deb>
dec 07 07:40:02 pc kernel: dpm_run_callback(): usb_dev_suspend+0x0/0x10 returns>
dec 07 07:40:02 pc kernel: PM: Device usb2 failed to suspend async: error -16
dec 07 07:40:02 pc kernel: PM: Some devices failed to suspend, or early wake ev>
dec 07 07:40:02 pc kernel: PM: suspend exit
dec 07 07:40:02 pc kernel: PM: suspend entry (s2idle)
dec 07 07:40:07 pc kernel: Suspending console(s) (use no_console_suspend to deb>
dec 07 07:40:07 pc kernel: dpm_run_callback(): usb_dev_suspend+0x0/0x10 returns>
dec 07 07:40:07 pc kernel: PM: Device usb2 failed to suspend async: error -16
dec 07 07:40:07 pc kernel: PM: Some devices failed to suspend, or early wake ev>
dec 07 07:40:07 pc kernel: PM: suspend exit
dec 07 07:40:07 pc systemd[1]: systemd-suspend.service: Main process exited, co>
dec 07 07:40:07 pc systemd[1]: systemd-suspend.service: Failed with result 'exi>
dec 07 07:40:07 pc systemd[1]: Failed to start Suspend.
dec 07 07:40:07 pc systemd[1]: Dependency failed for Suspend.
dec 07 07:40:07 pc systemd[1]: suspend.target: Job suspend.target/start failed >

This is my system:

System:
Host: pc Kernel: 4.19.6-1-MANJARO x86_64 bits: 64 Desktop: Gnome 3.30.2
Distro: Manjaro Linux
Machine:
Type: Laptop Mobo: INTEL model: CRESCENTBAY serial:
UEFI: American Megatrends v: 5.6.5 date: 08/29/2015
CPU:
Topology: Dual Core model: Intel Core i5-5257U bits: 64 type: MT MCP
L2 cache: 3072 KiB
Speed: 798 MHz min/max: 500/3100 MHz Core speeds (MHz): 1: 798 2: 798
3: 798 4: 797
Graphics:
Device-1: Intel Iris Graphics 6100 driver: i915 v: kernel
Display: x11 server: X.org 1.20.3 driver: i915
resolution:
OpenGL: renderer: Mesa DRI Intel Iris 6100 (Broadwell GT3)
v: 4.5 Mesa 18.2.6
Audio:
Device-1: Intel Broadwell-U Audio driver: snd_hda_intel
Device-2: Intel Wildcat Point-LP High Definition Audio
driver: snd_hda_intel
Device-3: Z-Star Micro type: USB driver: snd-usb-audio,uvcvideo
Sound Server: ALSA v: k4.19.6-1-MANJARO
Network:
Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
driver: r8168
IF: enp2s0 state: up speed: 1000 Mbps duplex: full mac: 00:e0:4c:68:04:97
Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
driver: r8168

Maybe the problem has something to do with usb, but then the script from this post should have helped?

I probably need some other suggestions to solve this issue.


Manjaro will not suspend/hibernate at all
#2

You can safely use the script provided by @tbg

if it doesn’t work, then you can try the one i provided above that post.


#3

I am sorry, but please read in my post what I have already tried.

Here is what I have unsuccessfully tried so far to correct this:

  • Script provided in this post.
  • Downgrading Kernel to 416 (and also to 414).

#4

There are two scripts in that post … Did you tried both?


#5

Tried this one (with no effect)

This did not work when placed in /lib/systemd/system-sleep/


#6

But you did chmod them? Is an important step … :slight_smile: And after the reboot you have to test the suspend.
Just making sure.


#7

Yes I did chmod. But I did not re-boot, trying that now.
(I will be gone for a while now)
Post my experience later.


#8

The script I posted would have to be split in half. The first part to unload the USB bus would need to be run before suspend. The remainder of the script reloading the USB would need to set to run after resume. That would probably require 2 systemd service files to be written.


#9

Have now tried both scripts, and this is what is happening when trying to suspend. The behavior is the same for both scripts (also with tbg script split in half):

The computer briefly actually goes to sleep for about one second, but then it comes back on again.

Without any of the scripts in place, the only thing that happens when trying to suspend is the display flashing.


#10

Let’s see what you have in:
journalctl -b -g suspend


#11

This is with script in place.

[tomas@pc ~]$ journalctl -b -g suspend
– Logs begin at Fri 2018-12-07 09:17:57 CET, end at Fri 2018-12-07 10:44:18 CE>
dec 07 10:17:30 pc /usr/lib/gdm-x-session[580]: (II) AIGLX: Suspending AIGLX cl>
dec 07 10:19:44 pc systemd[1]: Starting TLP suspend/resume…
dec 07 10:19:44 pc systemd[1]: Started TLP suspend/resume.
dec 07 10:19:44 pc systemd[1]: Starting Suspend…
dec 07 10:19:44 pc systemd-sleep[2116]: /usr/lib/systemd/system-sleep/usb_suspe>
dec 07 10:19:45 pc systemd-sleep[2116]: Suspending system…
dec 07 10:19:45 pc kernel: PM: suspend entry (deep)
dec 07 10:19:50 pc kernel: Suspending console(s) (use no_console_suspend to deb>
dec 07 10:19:50 pc kernel: PM: suspend exit
dec 07 10:19:50 pc systemd-sleep[2116]: 0000:00:14.0/usr/lib/systemd/system-sle>
dec 07 10:19:50 pc systemd[1]: Started Suspend.
dec 07 10:19:50 pc audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294>
dec 07 10:19:50 pc audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=42949>
dec 07 10:19:50 pc systemd[1]: Stopping TLP suspend/resume…
dec 07 10:19:50 pc systemd[1]: Reached target Suspend.
dec 07 10:19:50 pc systemd[1]: suspend.target: Unit not needed anymore. Stoppin>
dec 07 10:19:50 pc systemd[1]: Stopped target Suspend.
dec 07 10:19:50 pc kernel: audit: type=1130 audit(1544174390.366:64): pid=1 uid>
dec 07 10:19:50 pc kernel: audit: type=1131 audit(1544174390.366:65): pid=1 uid>
dec 07 10:19:50 pc systemd[1]: Stopped TLP suspend/resume.
dec 07 10:30:10 pc systemd[1]: Starting TLP suspend/resume…
dec 07 10:30:10 pc systemd[1]: Started TLP suspend/resume.
dec 07 10:30:10 pc systemd[1]: Starting Suspend…
dec 07 10:30:10 pc systemd-sleep[3445]: Suspending system…
dec 07 10:30:10 pc kernel: PM: suspend entry (deep)
dec 07 10:30:11 pc kernel: Suspending console(s) (use no_console_suspend to deb>
dec 07 10:30:11 pc kernel: dpm_run_callback(): usb_dev_suspend+0x0/0x10 returns>
dec 07 10:30:11 pc kernel: PM: Device usb2 failed to suspend async: error -16
dec 07 10:30:11 pc kernel: PM: Some devices failed to suspend, or early wake ev>
dec 07 10:30:11 pc kernel: PM: suspend exit
dec 07 10:30:11 pc kernel: PM: suspend entry (s2idle)
dec 07 10:30:14 pc kernel: Suspending console(s) (use no_console_suspend to deb>
dec 07 10:30:14 pc kernel: dpm_run_callback(): usb_dev_suspend+0x0/0x10 returns>
dec 07 10:30:14 pc kernel: PM: Device usb2 failed to suspend async: error -16
dec 07 10:30:14 pc kernel: PM: Some devices failed to suspend, or early wake ev>
dec 07 10:30:14 pc kernel: PM: suspend exit
dec 07 10:30:14 pc kernel: audit: type=1130 audit(1544175014.675:73): pid=1 uid>
dec 07 10:30:14 pc audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294>
dec 07 10:30:14 pc systemd[1]: systemd-suspend.service: Main process exited, co>
dec 07 10:30:14 pc systemd[1]: systemd-suspend.service: Failed with result 'exi>
dec 07 10:30:14 pc systemd[1]: Failed to start Suspend.
dec 07 10:30:14 pc systemd[1]: Dependency failed for Suspend.
dec 07 10:30:14 pc systemd[1]: suspend.target: Job suspend.target/start failed >
dec 07 10:30:14 pc systemd[1]: Stopping TLP suspend/resume…
dec 07 10:30:16 pc systemd[1]: Stopped TLP suspend/resume.
dec 07 10:37:53 pc org.gnome.Shell.desktop[1038]: Window manager warning: Buggy>
dec 07 10:37:53 pc org.gnome.Shell.desktop[1038]: Window manager warning: Buggy>
dec 07 10:41:38 pc systemd[1]: Starting TLP suspend/resume…
dec 07 10:41:39 pc systemd[1]: Started TLP suspend/resume.
dec 07 10:41:39 pc systemd[1]: Starting Suspend…
dec 07 10:41:39 pc systemd-sleep[4080]: /usr/lib/systemd/system-sleep/usb_suspe>
dec 07 10:41:39 pc kernel: PM: suspend entry (deep)
dec 07 10:41:39 pc systemd-sleep[4080]: Suspending system…
dec 07 10:41:42 pc kernel: Suspending console(s) (use no_console_suspend to deb>
dec 07 10:41:42 pc kernel: PM: suspend exit
dec 07 10:41:42 pc systemd-sleep[4080]: 0000:00:14.0/usr/lib/systemd/system-sle>
dec 07 10:41:42 pc systemd[1]: Started Suspend.
dec 07 10:41:42 pc audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294>
dec 07 10:41:42 pc kernel: audit: type=1130 audit(1544175702.808:83): pid=1 uid>
dec 07 10:41:42 pc kernel: audit: type=1131 audit(1544175702.808:84): pid=1 uid>
dec 07 10:41:42 pc audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=42949>
dec 07 10:41:42 pc systemd[1]: Stopping TLP suspend/resume…
dec 07 10:41:42 pc systemd[1]: Reached target Suspend.
dec 07 10:41:42 pc systemd[1]: suspend.target: Unit not needed anymore. Stoppin>
dec 07 10:41:42 pc systemd[1]: Stopped target Suspend.
dec 07 10:41:43 pc systemd[1]: Stopped TLP suspend/resume.
lines 45-67/67 (END)


#12

Indeed nothing changed from the previous journal.
But what is strange:

One way would be to remove tlp - but i honestly don’t know how that works on laptops.

Let’s see what gives:
cat /sys/power/mem_sleep


#13

[tomas@pc ~]$ cat /sys/power/mem_sleep
s2idle [deep]


#14

I don’t see anything in your logs to indicated a network issue preventing suspend, but that is often one of the main reasons for suspend problems.

You can test for this problem by stopping network manager, rmmoding your network drivers, then lowering your network adapters prior to suspending.


#15

Just tried suspend when running a live USB-Manjaro (manjaro-gnome-18.0-stable-x86_64.iso) on the very same computer. Suspend works perfectly. I also did journalctl -b -g suspend on the live:

[manjaro@manjaro-gnome ~]$ journalctl -b -g suspend
– Logs begin at Fri 2018-12-07 09:58:03 UTC, end at Fri 2018-12-07 10:00:48 UT>
Dec 07 10:00:30 manjaro-gnome systemd[1]: Starting TLP suspend/resume…
Dec 07 10:00:30 manjaro-gnome systemd[1]: Started TLP suspend/resume.
Dec 07 10:00:30 manjaro-gnome systemd[1]: Starting Suspend…
Dec 07 10:00:30 manjaro-gnome systemd-sleep[2541]: Suspending system…
Dec 07 10:00:41 manjaro-gnome kernel: PM: suspend entry (deep)
Dec 07 10:00:41 manjaro-gnome kernel: Suspending console(s) (use no_console_sus>
Dec 07 10:00:42 manjaro-gnome kernel: PM: suspend exit
Dec 07 10:00:42 manjaro-gnome kernel: audit: type=1130 audit(1544176841.993:60)>
Dec 07 10:00:42 manjaro-gnome kernel: audit: type=1131 audit(1544176841.993:61)>
Dec 07 10:00:41 manjaro-gnome audit[1]: SERVICE_START pid=1 uid=0 auid=42949672>
Dec 07 10:00:41 manjaro-gnome audit[1]: SERVICE_STOP pid=1 uid=0 auid=429496729>
Dec 07 10:00:41 manjaro-gnome systemd[1]: Started Suspend.
Dec 07 10:00:41 manjaro-gnome systemd[1]: Stopping TLP suspend/resume…
Dec 07 10:00:41 manjaro-gnome systemd[1]: Reached target Suspend.
Dec 07 10:00:41 manjaro-gnome systemd[1]: suspend.target: Unit not needed anymo>
Dec 07 10:00:41 manjaro-gnome systemd[1]: Stopped target Suspend.
Dec 07 10:00:43 manjaro-gnome systemd[1]: Stopped TLP suspend/resume.

To compare with from my installed (from that same USB) system and without any extra script in /lib/systemd/system-sleep/:

[tomas@pc ~]$ journalctl -b -g suspend
– Logs begin at Fri 2018-12-07 10:01:53 CET, end at Fri 2018-12-07 11:03:03 CE>
dec 07 10:57:34 pc /usr/lib/gdm-x-session[557]: (II) AIGLX: Suspending AIGLX cl>
dec 07 11:02:52 pc systemd[1]: Starting TLP suspend/resume…
dec 07 11:02:52 pc systemd[1]: Started TLP suspend/resume.
dec 07 11:02:52 pc systemd[1]: Starting Suspend…
dec 07 11:02:52 pc systemd-sleep[2060]: Suspending system…
dec 07 11:02:52 pc kernel: PM: suspend entry (deep)
dec 07 11:02:53 pc kernel: Suspending console(s) (use no_console_suspend to deb>
dec 07 11:02:53 pc kernel: dpm_run_callback(): usb_dev_suspend+0x0/0x10 returns>
dec 07 11:02:53 pc kernel: PM: Device usb2 failed to suspend async: error -16
dec 07 11:02:53 pc kernel: PM: Some devices failed to suspend, or early wake ev>
dec 07 11:02:53 pc kernel: PM: suspend exit
dec 07 11:02:53 pc kernel: PM: suspend entry (s2idle)
dec 07 11:02:57 pc kernel: Suspending console(s) (use no_console_suspend to deb>
dec 07 11:02:57 pc kernel: dpm_run_callback(): usb_dev_suspend+0x0/0x10 returns>
dec 07 11:02:57 pc kernel: PM: Device usb2 failed to suspend async: error -16
dec 07 11:02:57 pc kernel: PM: Some devices failed to suspend, or early wake ev>
dec 07 11:02:57 pc kernel: PM: suspend exit
dec 07 11:02:57 pc systemd[1]: systemd-suspend.service: Main process exited, co>
dec 07 11:02:57 pc systemd[1]: systemd-suspend.service: Failed with result 'exi>
dec 07 11:02:57 pc systemd[1]: Failed to start Suspend.
dec 07 11:02:57 pc systemd[1]: Dependency failed for Suspend.
dec 07 11:02:57 pc systemd[1]: suspend.target: Job suspend.target/start failed >
dec 07 11:02:57 pc audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294>
dec 07 11:02:57 pc systemd[1]: Stopping TLP suspend/resume…
dec 07 11:02:57 pc kernel: audit: type=1130 audit(1544176977.062:62): pid=1 uid>
dec 07 11:02:58 pc systemd[1]: Stopped TLP suspend/resume.
lines 5-27/27 (END)

Any help to solve this is much wanted and appreciated, thanks.


#16

Could this issue be related to that one here?


#17

Not sure, but I will take a look. Thanks anyway!


#19

[UPDATE]:
This problem still exists for me. Tried everything suggested in this post without success. In my frustration I removed Manjaro and installed Ubuntu 18.10 on the same computer. After trying Ubuntu extensively for about one week especially with suspend there were no problems at all, suspend worked as expected (so I’ll guess one can roll out my hardware as being the problem). But as I very much prefer Manjaro over Ubuntu, I re-installed my Manjaro Gnome 18.0, only to once more be faced with the fact that suspend does not work.

So: Ubuntu works with suspend, Manjaro does not. There must be a way to fix this?

Note: Suspend in Manjaro also worked up until about a month ago, when this problem started (Also: Please go through what has already been commented in this post before replying, thanks).


#20

I made this suggestion over a week ago. You went to the lengths of installing Ubuntu to correct this, but did you even attempt my suggestion.

I have helped correct suspend issues for many people on the forum by writing a systemd service to correct suspend problems. The forums search function is your friend. You are generally never the first to encounter a specific issue, the answer has usually already been discussed on the forum if you search for it.

I have many other posts on this topic if you search the forum.

https://forum.manjaro.org/t/kernel-4-19-0-3-not-network-after-suspending-gnome-edition/63544/2

https://forum.manjaro.org/t/wifi-adapter-tp-link-tl-wn823n-must-be-reconnected-for-it-to-work/52968/19

https://forum.manjaro.org/t/surface-pro-1796-wifi-not-resuming-after-suspend/48133/47

https://forum.manjaro.org/t/thinkpad-x230t-wont-suspend-under-kernel-419rc4-4-18-4-17-4-14-4-9/59798/21

Here are some external links with excellent systemd reference material:

The ArchWiki - systemd

Red Hat - systemd-targets

Red Hat - systemd unit files

Systemd manpage


#21

It seems to me that tracking down the exact offending hardware would be the quickest way to a solution.