[Ubuntu-x-swat] [Bug 1997178] Re: Black screen after wake from S3 suspend on Nvidia proprietary driver redux
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. ** Package changed: xorg (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1997178 Title: Black screen after wake from S3 suspend on Nvidia proprietary driver redux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1997178/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1997178] Re: Black screen after wake from S3 suspend on Nvidia proprietary driver redux
** Attachment added: "journalctl log of sleep-wake-forced reboot around Nov 20 10:28:37" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1997178/+attachment/5631722/+files/reboot.txt ** Description changed: 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). This makes me think the issue - is around Nvidia driver <-> Linux kernel communication. + 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 mid- - upgrade (first time this has happened to me on Linux in at least 5 + 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..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) + 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] + 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= - LANG=en_US.UTF-8 - SHELL=/usr/bin/zsh + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + 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.
[Ubuntu-x-swat] [Bug 1997178] [NEW] Black screen after wake from S3 suspend on Nvidia proprietary driver redux
Public bug reported: 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..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= 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 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug freeze jammy ubuntu -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed
[Ubuntu-x-swat] [Bug 1987134] Re: Black screen after wake from S3 suspend on Nvidia proprietary driver
Tried installing the Nvidia 390 driver since that is another commonly cited workaround, but once pass the filesystem encryption password prompts the screen goes black. No useful error messages in journalctl that I can see. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1987134 Title: Black screen after wake from S3 suspend on Nvidia proprietary driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1987134/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1987134] [NEW] Black screen after wake from S3 suspend on Nvidia proprietary driver
Public bug reported: An Nvidia driver upgrade in Ubuntu 20.04 caused waking from S3 suspend to lead to a black screen. Upgrading to Ubuntu 22.04 using latest stable Nvidia driver 515.65.01 did not resolve the issue. There are several Nvidia sleep tickets that at first seem related, but mention dmesg entries that I am not seeing which makes me suspect I have a different issue: * https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-510/+bug/1970088 * https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1946303 Workaround dhenry mentions in 1970088 of disabling the nvidia suspend and hibernate systemd services makes no difference for me. Currrently running Ubuntu 22.04, Nvidia GTX 970 on driver 515.65.01, AMD Ryzen 7 5800X. Here are journalctl excerpts during the reboot process, with and without nvidia systemd suspend services. dmesg and /var/log/kern.log show no errors as are mentioned in the above tickets. With disabled nvidia suspend systemd services: Aug 19 12:42:37 uf-panacea ModemManager[2731]: [sleep-monitor] system is about to suspend Aug 19 12:42:37 uf-panacea NetworkManager[2617]: [1660938157.8491] manager: NetworkManager state> Aug 19 12:42:37 uf-panacea systemd[1]: Reached target Sleep. Aug 19 12:42:37 uf-panacea systemd[1]: Starting Record successful boot for GRUB... Aug 19 12:42:37 uf-panacea systemd[1]: Starting System Suspend... Aug 19 12:42:37 uf-panacea systemd-sleep[13048]: Entering sleep state 'suspend'... Aug 19 12:42:37 uf-panacea systemd[1]: grub-common.service: Deactivated successfully. Aug 19 12:42:37 uf-panacea systemd[1]: Finished Record successful boot for GRUB. With enabled nvidia suspend systemd services: Aug 19 12:12:25 uf-panacea systemd[1]: Starting NVIDIA system suspend actions... Aug 19 12:12:25 uf-panacea suspend[15998]: nvidia-suspend.service Aug 19 12:12:25 uf-panacea logger[15998]: <13>Aug 19 12:12:25 suspend: nvidia-suspend.service Aug 19 12:12:25 uf-panacea systemd[1]: grub-common.service: Deactivated successfully. Aug 19 12:12:25 uf-panacea systemd[1]: Finished Record successful boot for GRUB. Aug 19 12:12:25 uf-panacea systemd[1]: Starting GRUB failed boot detection... Aug 19 12:12:25 uf-panacea systemd[1]: grub-initrd-fallback.service: Deactivated successfully. Aug 19 12:12:25 uf-panacea systemd[1]: Finished GRUB failed boot detection. Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (**) Option "fd" "40" Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (II) event1 - Power Button: device removed Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (**) Option "fd" "43" Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (II) event0 - Power Button: device removed Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (**) Option "fd" "44" Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (II) event4 - USB Mouse OKLIC: device removed Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (**) Option "fd" "45" Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (II) event5 - USB Mouse OKLIC Mouse: device removed Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (**) Option "fd" "46" Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (II) event6 - USB Mouse OKLIC System Control: device removed Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (**) Option "fd" "47" Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (II) event7 - USB Mouse OKLIC Consumer Control: device removed Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (**) Option "fd" "53" Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (**) Option "fd" "53" Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (II) event11 - Valve Software Steam Controller: device removed Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (**) Option "fd" "50" Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (**) Option "fd" "50" Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (II) event9 - Logitech G305: device removed Aug 19 12:12:25 uf-panacea rtkit-daemon[3286]: Supervising 10 threads of 4 processes of 1 users. Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (**) Option "fd" "51" Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (**) Option "fd" "51" Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (II) event13 - Corsair Corsair STRAFE RGB Gaming Keyboard: device removed Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (**) Option "fd" "52" Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (II) event2 - C-Media Electronics Inc. USB Audio Device: device removed Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (**) Option "fd" "89" Aug 19 12:12:25 uf-panacea /usr/libexec/gdm-x-session[4092]: (II) event3 - DCMT Technology USB Condenser Microphone: device removed Aug 19 12:12:25 uf-panace
[Ubuntu-x-swat] [Bug 857615] Re: ~/.xmodmaprc has been renamed ~/.Xmodmap
On Ubuntu 14.04, xmodmap is not called after resuming from suspend, making this still broken compared to the old behavior. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to x11-xserver-utils in Ubuntu. https://bugs.launchpad.net/bugs/857615 Title: ~/.xmodmaprc has been renamed ~/.Xmodmap To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/x11-xserver-utils/+bug/857615/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 857615] Re: ~/.xmodmaprc has been renamed ~/.Xmodmap
Same as comment #10 on Ubuntu 13.04. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to x11-xserver-utils in Ubuntu. https://bugs.launchpad.net/bugs/857615 Title: ~/.xmodmaprc has been renamed ~/.Xmodmap To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/x11-xserver-utils/+bug/857615/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp