Restart after resume from suspend

[FM33]

Regularly, quite often actually, ubuntu 24.04 restarts after resuming from suspend. This is not just a logout as I can see the MSI logo that usually shows during boot/shutdown. This is not the only issue with ACPI/suspend.

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: gnome-shell 46.0-0ubuntu5.1
ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
Uname: Linux 6.8.0-31-generic x86_64
ApportVersion: 2.28.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Mon Jun 3 21:44:41 2024
DisplayManager: gdm3
InstallationDate: Installed on 2024-05-18 (16 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
ProcEnviron:
 LANG=fr_FR.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=<set>
RelatedPackageVersions: mutter-common 46.0-1ubuntu9
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

[Daniel van Vugt (vanvugt)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps:

1. Run these commands:
    journalctl -b0 > journal.txt
    journalctl -b-1 > prevjournal.txt
and attach the resulting text files here.

2. Look in /var/crash for crash files and if found run:
    ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.

3. If step 2 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us.

Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself.

[FM33 (fm33)]

For the crash reports, there is none for yesterday's incident.
There are 2 from earlier, but I don't recall if it was for this specific problem :
https://errors.ubuntu.com/oops/38e94e8a-1c52-11ef-8b8f-fa163ec8ca8c : gnome-screensaver on may 27
https://errors.ubuntu.com/oops/7b634372-153d-11ef-9e07-fa163ec44ecd : gnome-shell on may 18
https://errors.ubuntu.com/oops/24a3ff48-1b3e-11ef-9e25-fa163ec44ecd : one of 4 occurences for xwayland

[Akash Kollipara (akashkollipara)]

I too am facing same issue with Asus expertcenter PN53.

I tried to check if the suspend issue is present in my installation or even live disk has the same.
It appears the issue is persistent across both.

Later I tried using ubuntu booted to tty2 without gdm3. suspend resume works perfectly fine. I tried exercising this cycle over 20 times, none failed. After this I logged into gdm3 from tty1 and tried running same command `sudo systemctl suspend` and it failed in first go.

with journalctl -b-1 the last log i see is `kernel: PM: suspend entry (s2idle)`

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Akash Kollipara (akashkollipara)]

Also, it would be great to have "wake up source configuration" under power settings to wake the system up from suspend state.

[Frantisek Sklenar (frantisek-sklenar)]

Same for me, ASUS ROG notebook, NVIDIA drivers.
It started 2 days ago after upgrade from 23.10 -> 24.04. Never appeared before.
Seems related to 6.8 kernel, because when I boot to old 6.5 kernel, resume from sleep does not target to reboot.
Reboot after resume from sleep mode occurs every time.

Thank you for your support.

[FM33 (fm33)]

I will need to test it longer to be sure, but the issue seems not to happen when suspending using "sudo pm-suspend" command from gnome-terminal (the command is from pm-utils package).

[Mario Limonciello (superm1)]

If this is AMD Rembrandt, it's probably this bug:

https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.5/+bug/2064595

[Frantisek Sklenar (frantisek-sklenar)]

Yes, CPU on my ASUS notebook is AMD Ryzen 7 6800H, so "Rembrandt".

Command "sudo pm-suspend" does not work properly on my notebook, just blank screen but without going to sleep mode - hard restart needed.

[Mario Limonciello (superm1)]

> Command "sudo pm-suspend" does not work properly on my notebook, just blank screen but without going to sleep mode - hard restart needed.

FYI pm-utils is orphaned and outdated. You should be using `systemctl suspend` to suspend from CLI.

> Yes, CPU on my ASUS notebook is AMD Ryzen 7 6800H, so "Rembrandt".

Then your issue is probably duplicate of https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.5/+bug/2064595.

[FM33 (fm33)]

I tried "systemctl suspend" and it reproduced the issue right away. It must be the command that gnome shell's menu is triggering. So, I will keep using pm-suspend as a workaround until the issue is fixed.

[Mario Limonciello (superm1)]

I can explain your result. The issue is specifically a race condition with the lock screen triggering after the suspend sequence starts. The driver change that helps it flushes content during the suspend sequence to ensure engines are not running when suspend starts.

By using pm utils you don't trigger the lock screen. The proper solution is the patch linked in the bug I referenced.

[Akash Kollipara (akashkollipara)]

I had tried performing suspend after locking the screen and leaving it for a while.
But in few trial run I noticed the crash even after locking.
And not just that, even when you are logged out, that is in login screen of ubuntu, when we perform suspend with gui button, it still fails.

[Mario Limonciello (superm1)]

The GUI button triggers the lock action and dpms. Grab a newer kernel or backport that patch linked in the bug.

[Frantisek Sklenar (frantisek-sklenar)]

This is probably behavior of my notebook https://www.phoronix.com/news/Linux-6.10-rc4-PM-Ryzen-NVMe, because after reboot on resume from sleep, notebook reboots to BIOS and NVMe SSD (NVMe) are not visible. I need to shutdown notebook and start again.
The only thing I don't understand, that Ubuntu 23.04 and 23.10 worked perfectly, no problem with sleep mode.
Which Ubuntu kernel should I use as workaround please (currently 6.8.0-35-generic #35-Ubuntu SMP PREEMPT_DYNAMIC kernel), I've tried some kernels from noble-proposal, but problem still persists.
Thank you.

[Frantisek Sklenar (frantisek-sklenar)]

Report of https://gitlab.freedesktop.org/drm/amd/-/blob/master/scripts/amd_s2idle.py

[Mario Limonciello (superm1)]

#19/#20.

Your issue is not that one that you linked. 6.8.0-38.38 picks up the fix for #2064595. So if that helps, your issue is a duplicate of #2064595. If that doesn't help, you have a different issue. You should open up your own issue for triage in this case.