Suspend stopped working since a few days

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.

1 Like

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.

Could this issue be related to that one here?

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

[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).

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://archived.forum.manjaro.org/t/kernel-4-19-0-3-not-network-after-suspending-gnome-edition/63544/2

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

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

https://archived.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

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

I posted a link to a thread with a very similar issue above... not sure whether OP bothered to read it.
In any case, may I suggest you try removing the offending USB device if that's possible, and see if it helps?

Sounds like general laziness to me. User expecting an answer served up on a silver platter without having to do any work or provide any feedback.

In his/her defense there were scripts being applied and tried at least. Also there is a long history of suspend not working on some linux based machines.

I know suspend issues are rampant on Linux laptops, but unless it is the video driver responsible for the issue, there is generally a workaround that can be applied.

Thanks for your comment. But since I have deleted my Manjaro install and replaced it with Ubuntu 18.10 (on the very same computer and all peripherals exactly in the same configuration) with the result that suspend worked perfectly, I don't see that it could be a hardware problem.

This was not a nice comment. I have tried all I can think of (even replaced my system with Ubuntu), also carefully read and tried all helpful tips I have got sofar in this topic. I am stuck with a non functional suspend, and that's bad. Just trying to get some help here, and I think the general atmosphere in this forum should be friendly. Please give that a thought @tbg

Perhaps if you were more proactive in responding to the suggestions that were made by many, you would not get stuff like that tossed at you. When suggestions are made and you do not respond to there implementation, one can only assume the suggestion was ignored. If you do not want people helping on the forum to think you are are not being lazy then have the courtesy to respond to their suggestions. If you do not respond to suggestions that are put forward, then people will naturally assume you are not doing your due diligence.

It is not only rude to not respond to those who have put forward suggestions, it also discourages others from making helpful suggestions when the find a user who treats helpers in this manner.

Look in the mirror , you only have your own behaviour to blame for this impression.

So does your laptop have an LTE modem?
More specifically, one from Huawei?

Hi, actually it's not a laptop. It's a desktop "mini" computer. There is no Huawei in it. See my computer specs in the top post.

Okay, any other USB devices?
Try lsusb

Please help me, what is wrong with you @tbg . If you read through all member suggests that I have got, you can clearly see that I have both responded and have given back the result. So, please stop your harassment.

btw...Merry Christmas

I have actually already tried to disconnect all usb-peripherals. It didn't make any difference.

[tomas@tomas-pc ~]$ lsusb
Bus 001 Device 002: ID 8087:8001 Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 003: ID 2537:1066
Bus 003 Device 004: ID 0951:1666 Kingston Technology DataTraveler 100 G3/G4/SE9 G2
Bus 003 Device 002: ID 2109:0813 VIA Labs, Inc.
Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 010: ID 05e3:0723 Genesys Logic, Inc. GL827L SD/MMC/MS Flash Card Reader
Bus 002 Device 013: ID 045e:0745 Microsoft Corp. Nano Transceiver v1.0 for Bluetooth
Bus 002 Device 012: ID 062a:4101 MosArt Semiconductor Corp. Wireless Keyboard/Mouse
Bus 002 Device 011: ID 1058:0704 Western Digital Technologies, Inc. My Passport Essential (WDME)
Bus 002 Device 009: ID 05e3:0608 Genesys Logic, Inc. Hub
Bus 002 Device 003: ID 0ac8:3500 Z-Star Microelectronics Corp.
Bus 002 Device 004: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
Bus 002 Device 002: ID 2109:2813 VIA Labs, Inc.
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Given that error messages is:

dec 07 11:02:57 pc kernel: PM: Device usb2 failed to suspend async: error -16

Could this give any clue?

Hmm ok. I don't know I'm afraid, I thought there might have been a problematic USB device but since you already tested without any, it must be something else (or the entire USB hub)...

Forum kindly sponsored by