System freezes immediately on suspending, where do I investigate?

0

0

I've just tried to suspend my newly installed Xubuntu 19.10 machine, a Lenovo S340 Ideapad. Upon pressing suspend while logged in, the system freezes instantly. The screen does not go black and even after half an hour, the machine accepts no inputs other than the classic REISUB combo. I can't even move the mouse or change tty. This happens whenever I attempt to suspend, even with systemctl suspend and xfce4-session-logout --suspend.

Where can I investigate the cause of this problem? kern.log shows the entry PM: suspend entry (deep) at what looks like the appropriate time, but nothing comes before this other than what I was doing many minutes before and nothing comes after until the reboot has started. On the other hand, syslog.log shows more activity, and I have reproduced this below. Everything before and after the given point in time is too far out to be relevant:

Feb 12 22:55:17 MyPC NetworkManager[1198]: <info>  [1581548117.3612] device (p2p-dev-wlp2s0): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
Feb 12 22:55:17 MyPC whoopsie[1521]: [22:55:17] offline
Feb 12 22:55:17 MyPC NetworkManager[1198]: <info>  [1581548117.3616] manager: NetworkManager state is now ASLEEP
Feb 12 22:55:17 MyPC systemd[1]: Reached target Sleep.
Feb 12 22:55:17 MyPC systemd[1]: Starting Suspend...
Feb 12 22:55:17 MyPC kernel: [ 8812.324175] PM: suspend entry (deep)
Feb 12 22:55:17 MyPC systemd-sleep[16039]: Suspending system...

journalctl is similarly unhelpful:

Feb 12 22:55:17 MyPC NetworkManager[1198]: <info>  [1581548117.3612] device (p2p-dev-wlp2s0): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
Feb 12 22:55:17 MyPC whoopsie[1521]: [22:55:17] offline
Feb 12 22:55:17 MyPC NetworkManager[1198]: <info>  [1581548117.3616] manager: NetworkManager state is now ASLEEP
Feb 12 22:55:17 MyPC systemd[1]: Reached target Sleep.
Feb 12 22:55:17 MyPC systemd[1]: Starting Suspend...
Feb 12 22:55:17 MyPC systemd-sleep[16039]: Suspending system...
Feb 12 22:55:17 MyPC kernel: PM: suspend entry (deep)
-- Reboot --

As for solving this problem, nothing that I've seen on AskUbuntu has worked:

  • Blacklisting Intel modules such as mei has changed nothing of relevance.
  • To my knowledge, I have no NVDIA modules to blacklist. In fact, I don't even have any options to install the drivers on the Additional Drivers menu. If there's an easy way to double-check, please comment.
  • lsmod | grep nouveau suggests that I'm not running the notoriously buggy nouveau module.
  • apt list --installed | grep light suggests that I'm not running the buggy lightlocker package.
  • I am already using lightdm, so gdm can't be to blame.
  • cat /sys/power/mem_sleep returns s2idle [deep]. I believe that this is the expected result.
  • Making changes to Grub's GRUB_CMDLINE_LINUX_DEFAULT settings for the PCIe connection to my SSD has done nothing. I have tried many other suggestions for changing Grub's settings, but I've failed to keep a log of them.
  • Editing SuspendState in /etc/systemd/sleep.conf has done nothing.
  • Changing to older kernels, even as far back as 5.0.21-050021.201906040731 or as far forward as 5.3.0-18.19+1, has changed nothing.
  • I am aware of some similar bugs in some 4.x kernels, but I'm under the impression that they've been patched in the 5.x kernels, so they shouldn't be relevant.
  • Lenovo is giving me contradictory dates for when the latest BIOS update was released, but my version number (ALCN28WW(V2.05)) matches theirs and the release date that sudo dmidecode gives me matches the date that's in their readme (November 25th 2019, contrary to their website's claim of December 16th 2019).

J. Mini

Posted 2020-02-12T23:58:01.927

Reputation: 97

You might look for answers in http://askubuntu.com as well; please, however, do not double-post.

– K7AAY – 2020-02-13T00:33:30.103

@K7AAY My search engine pointed there, but nothing helped or matched my problem. In fact, most info seems outdated. For example, pm-suspend is a thing of the past. – J. Mini – 2020-02-13T00:34:51.923

Even a blind pig finds an acorn now and then. Good that you checked. Good luck. – K7AAY – 2020-02-13T00:36:09.857

Have you tested to see if it is supported ? http://manpages.org/pm-is-supported

– vssher – 2020-02-13T03:51:27.867

Also, "pm-aciton" http://manpages.ubuntu.com/manpages/precise/man8/pm-action.8.html

– vssher – 2020-02-13T03:57:39.327

What type of machine are you running? Also, there is an AskUbuntu page (don't know if you came across it, 2019) waltinator has a good script there you might want to try https://askubuntu.com/questions/1199148/ubuntu-19-10-freeze-when-waking-from-suspension

– vssher – 2020-02-13T04:01:57.977

@vssher To the best of my awareness, pm stuff is defunct. I don't even have pm-utils installed. As for my machine, it's a Lenovo Ideapad S340. – J. Mini – 2020-02-13T11:37:42.263

Ever see this state: SuspendState=freeze (Note, that it is all Power Management to me) http://man7.org/linux/man-pages/man5/systemd-sleep.conf.5.html

– vssher – 2020-02-13T12:49:59.023

@vssher Everything in my etc/systemd/sleep.conf file is commented out and I lack all three sleep.conf.d directories. – J. Mini – 2020-02-13T12:55:24.403

@vssher Editing sleep.conf to have SuspendState=freeze changes nothing. – J. Mini – 2020-02-13T13:54:55.910

I was simply asking if that was a setting which was being used in .conf file SuspendState=freeze I thought maybe you should set this to suspend Hope you find your answer(s). – vssher – 2020-02-13T22:41:24.457

There are endless problems with Ubuntu suspend. Check all measures mentioned in the following and add to your post: post1, post2, post3, post4.

– harrymc – 2020-02-22T16:47:07.720

@harrymc Should I follow those posts even if the problems don't match mine, for example, those that only have issues in waking? – J. Mini – 2020-02-22T17:05:52.193

Better be selective, although it's hard to say if the same problem cannot have different symptoms. – harrymc – 2020-02-22T17:35:11.213

@harrymc I've been through those links and made the relevant edits. Sadly, I've made no progress. – J. Mini – 2020-02-22T18:24:29.010

I found a new BIOS update. I suggest verifying suitability by entering your serial number or using Automatic Driver Update. But I'm unsure if Linux is supported.

– harrymc – 2020-02-23T07:47:50.697

@harrymc My BIOS is already up to date. Will edit to reflect. – J. Mini – 2020-02-23T13:37:37.987

Answers

0

I am printing this here because it is to long for the comment section and it is in the format of the original page, except for the BOLD, that is mine.

Immediately before entering system suspend and/or hibernation
systemd-suspend.service (and the other mentioned units, respectively)
will run all executables in /usr/lib/systemd/system-sleep/ and pass
two arguments to them. The first argument will be "pre", the second
either "suspend", "hibernate", or "hybrid-sleep" depending on the
chosen action.  Immediately after leaving system suspend and/or
hibernation the same executables are run, but the first argument is
now "post". All executables in this directory are executed in
parallel, and execution of the action is not continued until all
executables have finished.

Source: http://man7.org/linux/man-pages/man8/systemd-sleep.8.html

Maybe you should not be commenting out items.


I ran a search for /etc/systemd/sleep.conf here at the sister site, with many results.

vssher

Posted 2020-02-12T23:58:01.927

Reputation: 499

Nothing in my /usr/lib/systemd/system-sleep/ directory has commented out lines. – J. Mini – 2020-02-13T13:19:19.280

Asked: 2020-02-12T23:58:01.927

Viewed: 200 times

Active: 2020-02-23T13:41:04.343