Resume fails siliently after suspend to RAM


My laptop will not resume after suspend to RAM (low battery, or lid closed etc.). From user observation only, suspend seems to work normally, then resume “tries” (there’s a time when it looks as if it will work as previously) but then it reboots instead. This started after updates ~21st June. Further updates have been applied without success. The journal records a reboot (literally “-- Reboot --”) after lines indicating the system was put into sleep mode (e.g. last line before the reboot starts “systemd-sleep[16973]: preparing boot-loader: selecting entry openSUSE Tumbleweed”), and lastlog indicates a resume starts and then the system shuts down:

11676-  OK  ] Started Show Plymouth Boot Screen.
11677-  OK  ] Found device PM951 NVMe SAMSUNG 512GB primary.
11678-         Starting Resume from hiber…using device /dev/nvme0n1p2...
11679-  OK  ] Reached target Paths.
11680-  OK  ] Started Forward Password R…s to Plymouth Directory Watch.
11681-  OK  ] Started Resume from hibern…n using device /dev/nvme0n1p2.
11682-  OK  ] Reached target Local File Systems (Pre).
11683-  OK  ] Reached target Local File Systems.
11684-  OK  ] Reached target System Initialization.
11685-  OK  ] Reached target Basic System.
11686-  OK  ] Found device PM951 NVMe SAMSUNG 512GB primary.
11687-  OK  ] Reached target Initrd Root Device.
11688-         Starting File System Check…152f-4b0d-b1f4-ae8be0fe4241...
11689-  OK  ] Started File System Check on /dev/disk/by-uuid/c4750d41-152f-4b0d-b1f4-ae8be0fe4241.
11690-         Mounting /sysroot...
11691-  OK  ] Mounted /sysroot.
11692-  OK  ] Reached target Initrd Root File System.
11693-         Starting Reload Configuration from the Real Root...
11694-  OK  ] Started Reload Configuration from the Real Root.
11695-  OK  ] Reached target Initrd File Systems.
11696-  OK  ] Reached target Initrd Default Target.
11697-         Starting Cleaning Up and Shutting Down Daemons...
11698-  OK  ] Stopped target Remote File Systems.
11699-  OK  ] Stopped target Initrd Default Target.

Suspend/resume has normally worked without fail, since this (Dell XPS13) laptop was first installed in 2015. Any ideas?

This is a long shot but are you running Chrome or Chromium when you try to Suspend to RAM? I have had periodic issues with those applications which is why I have stopped using them in favor of Firefox and Falkon for web browsers. I realize that is not a good solution but it is working for me.

Another thought, has anything else changed as of 21st of June on your system?