(non) Update with BIOS 3.09: I tested removing the "acpi_osi=!Windows 2020"
kernel command line parameter, it consistently regresses to being unable to enter s2idle, so no change in behavior for me.
FWIW here’s my full kernel command line under Fedora 36:
$ cat /proc/cmdline
BOOT_IMAGE=(hd1,gpt2)/vmlinuz-5.18.10-200.fc36.x86_64 root=UUID=f58ce626-0077-11ed-ab80-dfc16885529e ro rootflags=subvol=root rd.luks.uuid=luks-f66b1586-0077-11ed-af5c-934ee0d4a0c5 rhgb quiet "acpi_osi=!Windows 2020" nvme.noacpi=1
So with the acpi_osi
cmdline parameter included, I haven’t experienced the inability to enter suspend or spontaneous wakeups that @Usernames and @Edwin_van_Ouwerkerk have reported here. Perhaps related, the default ACPI wakeup settings seem a bit liberal to be, they include the external USB keyboard for example:
$ cat /proc/acpi/wakeup |grep enabled
PEG0 S4 *enabled pci:0000:00:06.0
XHCI S4 *enabled pci:0000:00:14.0
RP10 S4 *enabled pci:0000:00:1d.0
TXHC S4 *enabled pci:0000:00:0d.0
TDM0 S4 *enabled pci:0000:00:0d.2
TDM1 S4 *enabled pci:0000:00:0d.3
TRP0 S4 *enabled pci:0000:00:07.0
TRP1 S4 *enabled pci:0000:00:07.1
TRP2 S4 *enabled pci:0000:00:07.2
TRP3 S4 *enabled pci:0000:00:07.3
PWRB S4 *enabled platform:PNP0C0C:00
Maybe there’s a USB mouse in the mix somewhere that produces these failures to sleep/spontaneous resumes?