Suspend stopped working since kernel 5.4 (ubuntu 20.04)

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1910927

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

You can check whether s2idle or suspend (s3) is used by kernel 5.4 & kernel 4.15 by

$ cat /sys/power/mem_sleep
s2idle [deep]

where deep is s3

Switching one to another can be done by "echo deep | sudo tee /sys/power/mem_sleep" or "echo s2idle ...").

If switching to "deep" fixes your problem, you can make it permanent by adding "mem_sleep_default=deep" to your kernel parameters.

Please test latest mainline kernel:
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.11-rc3/amd64/

@alexhung

Deep is already selected "s2idle [deep]". If I select s2idle, it looks like the same problem.

@kaihengfeng

Same problem with mainline kernel 5.11.0-051100rc3 (build binaries verified).

As a temporary workaround, exists a lts kernel ppa from ubuntu 18.04 which I can use at 20.04?

I JUST got the "you have a new version available" and clicked update last night. From ~21.xx to 21.10 and it won't come back from deep sleep.

Acer C740P laptop with Ubuntu desktop.

Switching to:

echo shallow | sudo tee /sys/power/mem_sleep

from the previous comment allows me to come back. However, I'm almost certain this is a lesser level of suspend than WAS working on 21.xx because now it comes back on _instantly_ and it never did it that fast before. So I imagine that means my computer is barely suspended at all in this mode.

The last line of dmesg was :

acpi: EC: interrupt blocked

using:
$ journalctl -o short-precise -k -b -1

to get the previous dmesg log. But that ACPI line may be innocuous and not the key failure.

I'm not aware of any other useful log locations. Also a tool called pm-suspend seem to sleep and come back just fine.

Okay, so I added to my GRUB kernel parameters string:

acpi_sleep=s3_bios,s3_mode

per here:
 - http://powersave.sourceforge.net/powersave/Suspend2Ram.html
 - https://wiki.ubuntu.com/Kernel/KernelBootParameters

and ran GRUB config. And set myself back to:

echo deep | sudo tee /sys/power/mem_sleep

And it appears to be working!

I noticed SOMETHING seemed off because when my computer would "go to sleep" in the new version, the power light would stay bright blue (just like when it was on). So it seems to be crashing on suspend somewhere. Because now, when I hit suspend, it does the normal blinking yellow for the same LED.

NOPE, NEVERMIND. The issue is still happening. I thought I did a full reboot, with [deep], and came back. But I just came back after an hour or two and the BACKLIGHT turned on, but it still wouldn't come back from suspend.

This seems like it attempted to come back online:

$ journalctl -o short-precise -k -b -1

Nov 06 06:48:08.615902 sedna kernel: ACPI: EC: EC stopped
Nov 06 06:48:08.615935 sedna kernel: PM: Saving platform NVS memory
Nov 06 06:48:08.615965 sedna kernel: Disabling non-boot CPUs ...
Nov 06 06:48:08.616002 sedna kernel: IRQ 41: no longer affine to CPU1
Nov 06 06:48:08.616039 sedna kernel: IRQ 42: no longer affine to CPU1
Nov 06 06:48:08.616071 sedna kernel: IRQ 43: no longer affine to CPU1
Nov 06 06:48:08.616104 sedna kernel: smpboot: CPU 1 is now offline
Nov 06 06:48:08.616136 sedna kernel: ACPI: Low-level resume complete
Nov 06 06:48:08.616165 sedna kernel: ACPI: EC: EC started
Nov 06 06:48:08.616199 sedna kernel: PM: Restoring platform NVS memory
Nov 06 06:48:08.616230 sedna kernel: Enabling non-boot CPUs ...
Nov 06 06:48:08.616255 sedna kernel: x86: Booting SMP configuration:
Nov 06 06:48:08.616284 sedna kernel: smpboot: Booting Node 0 Processor 1 APIC 0x2
Nov 06 06:48:08.616313 sedna kernel: CPU1 is up
Nov 06 06:48:08.616338 sedna kernel: ACPI: Waking up from system sleep state S3
Nov 06 06:48:08.616374 sedna kernel: ACPI: EC: interrupt unblocked
Nov 06 06:48:08.616405 sedna kernel: ACPI: EC: event unblocked
Nov 06 06:48:08.616435 sedna kernel: sd 0:0:0:0: [sda] Starting disk
Nov 06 06:48:08.616612 sedna kernel: elan_i2c i2c-ELAN0000:00: invalid report id data (ff)
Nov 06 06:48:08.616821 sedna kernel: usb 1-3: reset high-speed USB device number 2 using xhci_hcd
Nov 06 06:48:08.617097 sedna kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Nov 06 06:48:08.617134 sedna kernel: ata1.00: configured for UDMA/133
Nov 06 06:48:08.617164 sedna kernel: OOM killer enabled.
Nov 06 06:48:08.617198 sedna kernel: Restarting tasks ... done.
Nov 06 06:48:08.617227 sedna kernel: PM: suspend exit
Nov 06 06:48:12.073184 sedna kernel: wlp1s0: authenticate with 1c:3b:f3:4c:6b:6f
Nov 06 06:48:12.081030 sedna kernel: wlp1s0: send auth to 1c:3b:f3:4c:6b:6f (try 1/3)
Nov 06 06:48:12.081106 sedna kernel: wlp1s0: authenticated
Nov 06 06:48:12.081155 sedna kernel: wlp1s0: associate with 1c:3b:f3:4c:6b:6f (try 1/3)
Nov 06 06:48:12.083802 sedna kernel: wlp1s0: RX AssocResp from 1c:3b:f3:4c:6b:6f (capab=0x1511 status=0 aid=3)
Nov 06 06:48:12.089026 sedna kernel: wlp1s0: associated
Nov 06 06:48:12.139628 sedna kernel: IPv6: ADDRCONF(NETDEV_CHANGE): wlp1s0: link becomes ready
[there are no more entries]

[then the reboot] $ sudo dmesg

Nov 06 06:49:04.835437 sedna kernel: microcode: microcode updated early to revision 0x2f, date = 2019-11-12
Nov 06 06:49:04.835488 sedna kernel: Linux version 5.13.0-20-generic (buildd@lgw01-amd64-013) (gcc (Ubuntu 11.2.0-7ubuntu2) 11.2.0, GNU ld (GNU Binut>
Nov 06 06:49:04.835508 sedna kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.13.0-20-generic root=UUID=afb97784-f7dc-4891-8f9b-f6c22831a037 ro mitig>
Nov 06 06:49:04.835521 sedna kernel: KERNEL supported cpus:
Nov 06 06:49:04.835533 sedna kernel: In...

To be clear, the last dmesg is from after I rebooted the "frozen" computer (which wouldn't respond to Control-Alt-F1/F8/etc or any other keys). Since it shows kernel version, etc.

I pushed some keys, the backlight came on like it was going to boot, and then it just stopped there. But I think the power LEDs were set to suspend like proper.

Switching back from Kernel 5.13.0 to 5.11.0 has fixed the issue. So this appears to be a kernel regression.

Recently I installed Ubuntu 20.04.3 LTS on an old Lenovo laptop (T61p). I was disappointed to discover that suspend did not work (as described in this report, black screen and no way to recover). I tried two version 5 kernels (5.13.0-27-generic and 5.8.0-43-generic).

As a wild guess I downloaded 4.19.0-041900-generic and suspend works for me with that kernel.

I would prefer to run a newer kernel but I need suspend.

Ah, I see the report refers to a Core Duo processor and that is what the T61p has too (Intel T7700 to be precise).