PC frequently fails to wake from suspend with kernel 5.4

[Christian Henz]

Ever since upgrading from Bionic to Focal, my machine frequently (multiple times per week) fails to wake up from suspend with the default 5.4 kernel (linux-image-generic).

When booting the 4.15 kernel from Bionic that I still have installed (linux-image-4.15.0-46-generic), suspend and wake-up works reliably again.

The symptoms of the failure to wake up are that the machine powers up (fans, LEDs), but the screen stays black. Num lock LED on the keyboard is ON and cannot be toggled. The Machine cannot be pinged.

After hard-resetting the machine, the last entry in journalctl from the previous boot is "kernel: PM: suspend entry (deep)".

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-generic 5.4.0.152.149
ProcVersionSignature: Ubuntu 5.4.0-152.169-generic 5.4.235
Uname: Linux 5.4.0-152-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.27
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC2: christian 2130 F.... pulseaudio
 /dev/snd/controlC1: christian 2130 F.... pulseaudio
 /dev/snd/controlC0: christian 2130 F.... pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: XFCE
Date: Tue Jun 27 09:02:07 2023
InstallationDate: Installed on 2014-09-16 (3205 days ago)
InstallationMedia: Ubuntu 12.04.5 LTS "Precise Pangolin" - Release amd64 (20140807.1)
MachineType: Gigabyte Technology Co., Ltd. H97M-D3H
ProcFB: 0 nouveaudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-152-generic root=UUID=ef54dd1e-0d88-4541-a64c-71f83163f2f2 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-5.4.0-152-generic N/A
 linux-backports-modules-5.4.0-152-generic N/A
 linux-firmware 1.187.39
RfKill:

SourcePackage: linux
UpgradeStatus: Upgraded to focal on 2023-04-03 (84 days ago)
dmi.bios.date: 06/03/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F3
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: H97M-D3H
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF3:bd06/03/2014:svnGigabyteTechnologyCo.,Ltd.:pnH97M-D3H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH97M-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: H97M-D3H
dmi.product.sku: To be filled by O.E.M.
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

[Christian Henz (chrhenz)]

The issue persists also with the 5.8 and 5.15 kernels that are installable on Focal.

It actually looks like the machine wakes up, but Xorg does not. I was able to shut down the machine gracefully by pressing the power button.

Looking at the log files after rebooting, it looks like there is a problem with nouveau:

Jul 04 08:08:50 christian-homeoffice kernel: pci_bus 0000:05: Allocating resources
Jul 04 08:08:50 christian-homeoffice kernel: pci 0000:04:00.0: bridge window [mem 0x00100000-0x000fffff 64bit pref] to [bus 05] add_size 200000 add_align 100000
Jul 04 08:08:50 christian-homeoffice kernel: pci 0000:04:00.0: BAR 15: no space for [mem size 0x00200000 64bit pref]
Jul 04 08:08:50 christian-homeoffice kernel: pci 0000:04:00.0: BAR 15: failed to assign [mem size 0x00200000 64bit pref]
Jul 04 08:08:50 christian-homeoffice kernel: pci 0000:04:00.0: BAR 15: no space for [mem size 0x00200000 64bit pref]
Jul 04 08:08:50 christian-homeoffice kernel: pci 0000:04:00.0: BAR 15: failed to assign [mem size 0x00200000 64bit pref]
Jul 04 08:08:50 christian-homeoffice kernel: done.
Jul 04 08:08:50 christian-homeoffice kernel: PM: suspend exit
Jul 04 08:08:50 christian-homeoffice kernel: nouveau 0000:01:00.0: gr: TRAP ch 3 [003fbc6000 Xorg[1162]]
Jul 04 08:08:50 christian-homeoffice kernel: nouveau 0000:01:00.0: gr: UNK6 80000001 [TEMP_TOO_SMALL]
Jul 04 08:08:50 christian-homeoffice kernel: nouveau 0000:01:00.0: gr: TRAP UNHANDLED 00000020
Jul 04 08:08:50 christian-homeoffice kernel: nouveau 0000:01:00.0: fifo: read fault at bad0ac1000 engine 00 [PGRAPH] client 05 [CTXCTL] reason 00 [PT_NOT_PRESENT] on channel 3 [003fbc6000 Xorg[1162]]
Jul 04 08:08:50 christian-homeoffice kernel: nouveau 0000:01:00.0: fifo: gr engine fault on channel 3, recovering...
Jul 04 08:08:50 christian-homeoffice kernel: nouveau 0000:01:00.0: Xorg[1162]: nv50cal_space: -16
Jul 04 08:08:46 christian-homeoffice systemd-sleep[150344]: System resumed.
Jul 04 08:08:50 christian-homeoffice kernel: nouveau 0000:01:00.0: Xorg[1162]: nv50cal_space: -16
Jul 04 08:08:50 christian-homeoffice kernel: nouveau 0000:01:00.0: Xorg[1162]: nv50cal_space: -16
Jul 04 08:08:51 christian-homeoffice kernel: nouveau 0000:01:00.0: Xorg[1162]: nv50cal_space: -16
Jul 04 08:08:51 christian-homeoffice kernel: nouveau 0000:01:00.0: Xorg[1162]: nv50cal_space: -16
Jul 04 08:08:51 christian-homeoffice systemd[1]: systemd-suspend.service: Succeeded.
Jul 04 08:08:51 christian-homeoffice systemd[1]: Finished Suspend.
Jul 04 08:08:51 christian-homeoffice systemd[1]: Stopped target Sleep.
Jul 04 08:08:51 christian-homeoffice systemd[1]: Reached target Suspend.
Jul 04 08:08:51 christian-homeoffice systemd[1]: Stopped target Suspend.
Jul 04 08:08:51 christian-homeoffice systemd-logind[926]: Operation 'sleep' finished.
Jul 04 08:08:51 christian-homeoffice kernel: nouveau 0000:01:00.0: Xorg[1162]: nv50cal_space: -16
Jul 04 08:08:52 christian-homeoffice kernel: nouveau 0000:01:00.0: Xorg[1162]: nv50cal_space: -16
Jul 04 08:08:52 christian-homeoffice kernel: nouveau 0000:01:00.0: Xorg[1162]: nv50cal_space: -16
Jul 04 08:08:52 christian-homeoffice kernel: nouveau 0000:01:00.0: Xorg[1162]: nv50cal_space: -16
Jul 04 08:08:52 ...

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This change was made by a bot.

[Christian Henz (chrhenz)]

I found the change that caused this regression.

Reported upstream: https://gitlab.freedesktop.org/drm/nouveau/-/issues/362