Black screen after wake from S3 suspend on Nvidia proprietary driver redux

Bug #1997178 reported by Jesse Johnson
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Confirmed
Undecided
Unassigned
nvidia-graphics-drivers-515 (Ubuntu)
New
Undecided
Unassigned

Bug Description

When resuming from suspend in Ubuntu 22.04 with proprietary Nvidia driver 515, screen is black, and never changes after 10 minutes of waiting.

However journalctl shows activity after wake (see attached log excerpt, where wake occurs around Nov 20 10:28:37 with black screen, followed by forced REISUB reboot a couple minutes later when screen failed to update). This makes me think the issue is around Nvidia driver <-> Linux kernel communication.

I [previously reported](https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1987134) similar black screen after wake behavior that seemed resolve with a Linux kernel update, but subsequent Linux kernel and Nvidia driver updates steadily regressed back to the previous behavior. The most recent kernel update from a few days ago (5.15.0-53-generic) never wakes from suspend (so far out of 5 trials). Previous few kernels where regression was first noticed it was 50/50 odds of successful wake, so most recent kernel is a noticeable regression.

Important note: most recent kernel (5.15.0-53) upgrade freezed system mid-upgrade (first time this has happened to me on Linux in at least 5 years!). Damaged GRUB and Nvidia DKMS, requiring reinstallation of GRUB, the kernel, Nvidia drivers, and a GRUB update (in that order).

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-53.59-generic 5.15.64
Uname: Linux 5.15.0-53-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
.proc.driver.nvidia.gpus.0000.0d.00.0: Error: path was not a regular file.
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module 515.65.01 Wed Jul 20 14:00:58 UTC 2022
 GCC version: gcc version 11.3.0 (Ubuntu 11.3.0-1ubuntu1~22.04)
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sun Nov 20 11:20:45 2022
DistUpgraded: Fresh install
DistroCodename: jammy
DistroVariant: ubuntu
DkmsStatus: nvidia/515.65.01, 5.15.0-53-generic, x86_64: installed
ExtraDebuggingInterest: Yes, including running git bisection searches
GpuHangFrequency: Several times a week
GpuHangReproducibility: Occurs more often under certain circumstances
GpuHangStarted: Within the last week or two
GraphicsCard:
 NVIDIA Corporation GM204 [GeForce GTX 970] [10de:13c2] (rev a1) (prog-if 00 [VGA controller])
   Subsystem: PNY GM204 [GeForce GTX 970] [196e:1131]
InstallationDate: Installed on 2022-08-17 (95 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1)
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/usr/bin/zsh
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-53-generic root=UUID=70074436-a9a5-4212-9b57-7600a7dc6843 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/29/2021
dmi.bios.release: 5.17
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P4.70
dmi.board.name: X470 Taichi Ultimate
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP4.70:bd03/29/2021:br5.17:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX470TaichiUltimate:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: To Be Filled By O.E.M.
dmi.product.sku: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.110-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

Revision history for this message
Jesse Johnson (holocronweaver) wrote :
Revision history for this message
Jesse Johnson (holocronweaver) wrote :
description: updated
Revision history for this message
Jesse Johnson (holocronweaver) wrote :

Tested and confirmed that wake from sleep results in a black screen 100% of the time on 5.15.0-53-generic, but only ~10% of the time on 5.15.0-52-generic. Thus on the surface it seems 5.15.0-53-generic caused a regression.

affects: xorg (Ubuntu) → linux (Ubuntu)
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
tags: added: nvidia suspend-resume
Changed in nvidia-graphics-drivers-515 (Ubuntu):
status: New → Confirmed
status: Confirmed → New
Revision history for this message
Jesse Johnson (holocronweaver) wrote :

Suspend still doesn't work on kernel 5.15.0-58-generic, Nvidia driver 525.78.01. No change in behavior.

Revision history for this message
Jesse Johnson (holocronweaver) wrote :

Upgraded to a Nvidia RTX 4090, and initially sleep seemed to work for a few weeks. After the last few kernel updates, sleep again is frequently (but not always) failing to wake, sometimes resulting in a hang at a black screen (responsive to Alt+Print+REISUB), sometimes in a automatic reboot after a couple minutes.

Attaching excerpt from systemd which covers the sleep, though it does not seem to record anything related to attempted wake before the force reboot. Oddly systemd is treating it as a single boot even though the system force rebooted.

Revision history for this message
Jesse Johnson (holocronweaver) wrote :

Worth noting that Windows 10 on this same desktop has never had an issue with sleep and wake - this is a Linux-specific issue.

Revision history for this message
Raphael Mankin (raph-p) wrote :

Still there on 6.5.*

 uname -a
Linux P1 6.5.0-18-generic #18~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Wed Feb 7 11:40:03 UTC 2 x86_64 x86_64 x86_64 GNU/Linux

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.