Suspend 'bug' for ubuntu 24.04LTS

just upgraded (with great pains, and a total crash repaired by boot repair) to Ubuntu 24.04LTS (20.04LTS, to 22.04LTS, to 23.10, to 24.04LTS). however, when I run ‘suspend’, it suspends but won’t restore ~ just hangs… BUT, if at boot up when I goto the grub sub menu to choose to boot using 5.15.0-105 generic rather than 6.8.0-31 generic, the suspend/resume works fine.

Also, (side note only) seems the problem with losing my build-in PCI wifi upon resume has been ‘fixed’ with 24.04LTS using the 5.15.0-105 generic as it resumes and the PCI wifi is still running - time after time so far :smiley:

Check log files:
Have you tried to see logs in order to get more information about the suspend issue with the newer kernel. Try the following commands:

sudo journalctl -b | grep -i suspend
OR
sudo journalctl -b | grep -i resume

This might provide you with some hints on what is going on. Also grep for error

Check for Proprietary Drivers:
If your hardware (like graphics cards or network adapters) requires proprietary drivers, the newer kernel might have issues with these. Check if you are using proprietary drivers and if there are updates or recommended configurations:

  • Open “Software & Updates” from the system menu.
  • Go to the “Additional Drivers” tab and see if any drivers are recommended for your hardware components. Although, here I would assume that the upgrade process should take care of this. But its still worth to check.

If you cannot find any solution perhaps stay with the older 5.15 kernel for a time being. Make sure to update your system and you might submit a bug report:

I do notice that when using the 5.15.0-105 kernel and as it shuts down at the black screen, there’s this message:
Failed: failed to start .snap.network-manager.networkmanager.service

it’s network manager that messes with my losing my builtin PCI wifi upon resume back on 20.04LTS… my intel/pro wireless 3945ABG PCI wifi device uses the iwl3945 driver and I found this: “hardware scanning is faster and more reliable and so is recommended for use with Network-Manager“. But unfortunately “iwl3945” driver does not support hardware scanning very well, however it is a default behavior that Network-Manager expects.”

Booting up off of 5.15.0-105 kernel, then going on standby, then resuming:

sudo journalctl -b | grep -i suspend - came up with:
ay 16 07:37:05 batgirl-E-475M systemd-logind[1268]: Suspend key pressed short.
May 16 07:37:05 batgirl-E-475M systemd-logind[1268]: The system will suspend now!
May 16 07:37:07 batgirl-E-475M ModemManager[1428]: [sleep-monitor-systemd] system is about to suspend
May 16 07:37:14 batgirl-E-475M systemd[1]: Starting systemd-suspend.service - System Suspend…
May 16 07:37:16 batgirl-E-475M systemd-sleep[7961]: Performing sleep operation ‘suspend’…
May 16 07:37:16 batgirl-E-475M kernel: PM: suspend entry (deep)
May 16 07:37:26 batgirl-E-475M kernel: printk: Suspending console(s) (use no_console_suspend to debug)
May 16 07:37:27 batgirl-E-475M kernel: PM: suspend exit
May 16 07:37:27 batgirl-E-475M systemd-sleep[7961]: System returned from sleep operation ‘suspend’.
May 16 07:37:29 batgirl-E-475M systemd[1]: systemd-suspend.service: Deactivated successfully.
May 16 07:37:29 batgirl-E-475M systemd[1]: Finished systemd-suspend.service - System Suspend.
May 16 07:37:29 batgirl-E-475M systemd[1]: Reached target suspend.target - Suspend.
May 16 07:37:29 batgirl-E-475M systemd-logind[1268]: Operation ‘suspend’ finished.
May 16 07:37:29 batgirl-E-475M systemd[1]: Stopped target suspend.target - Suspend.

then using:
sudo journalctl -b | grep -i resume, came up with:
May 16 07:05:02 batgirl-E-475M kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.15.0-105-generic root=UUID=fde5b459-7c69-45f7-bfec-070de23cf8d2 ro quiet splash resume=UUID=fde5b459-7c69-45f7-bfec-070de23cf8d2 resume_offset=1914880 vt.handoff=7
May 16 07:05:02 batgirl-E-475M kernel: Kernel command line: BOOT_IMAGE=/boot/vmlinuz-5.15.0-105-generic root=UUID=fde5b459-7c69-45f7-bfec-070de23cf8d2 ro quiet splash resume=UUID=fde5b459-7c69-45f7-bfec-070de23cf8d2 resume_offset=1914880 vt.handoff=7
May 16 07:37:26 batgirl-E-475M kernel: ACPI: PM: Low-level resume complete

of course, booting up with 6.8.0-31 appears to go into standby, but resume just hangs w/black screen doing nothing forcing a reboots so… here is info before trying to standby:
sudo journalctl -b | grep -i suspend gives nothing… while,
sudo journalctl -b | grep -i resume gives:
May 16 07:47:50 batgirl-E-475M kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-6.8.0-31-generic root=UUID=fde5b459-7c69-45f7-bfec-070de23cf8d2 ro quiet splash resume=UUID=fde5b459-7c69-45f7-bfec-070de23cf8d2 resume_offset=1914880 vt.handoff=7
May 16 07:47:50 batgirl-E-475M kernel: Kernel command line: BOOT_IMAGE=/boot/vmlinuz-6.8.0-31-generic root=UUID=fde5b459-7c69-45f7-bfec-070de23cf8d2 ro quiet splash resume=UUID=fde5b459-7c69-45f7-bfec-070de23cf8d2 resume_offset=1914880 vt.handoff=7

well, going into standby, hanging, then rebooting brings:
sudo journalctl -b | grep -i suspend gives nothing, and
sudo journalctl -b | grep -i resume gives this again:
May 16 07:58:36 batgirl-E-475M kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-6.8.0-31-generic root=UUID=fde5b459-7c69-45f7-bfec-070de23cf8d2 ro quiet splash resume=UUID=fde5b459-7c69-45f7-bfec-070de23cf8d2 resume_offset=1914880 vt.handoff=7
May 16 07:58:36 batgirl-E-475M kernel: Kernel command line: BOOT_IMAGE=/boot/vmlinuz-6.8.0-31-generic root=UUID=fde5b459-7c69-45f7-bfec-070de23cf8d2 ro quiet splash resume=UUID=fde5b459-7c69-45f7-bfec-070de23cf8d2 resume_offset=1914880 vt.handoff=7

…not helpful, eh?

…every once in awhile, and not every day, it will try to resume from standby (save to RAM) and instead just crash to terminal displaying ‘Failed: failed to start .snap.network-manager.networkmanager.service’ and below that a bunch of ^@^@^@^@… forcing a reboot ~ so even with the 5.15.0-105 kernel it’s not totally stable doing standby and resume :wink: