Thanks a lot for this fix! At least I think it was this fix? I had this issue on my Optimus laptop (Acer Predator G3-572). I think it only happened with kernel modesetting turned on. And it only happened with GDM, not LightDM.
What's interesting to me is that my GPU (1060 mobile) does not even have RTD3 capability. I had spent a lot of time googling potential fixes until I gave up and switched to LightDM. After reading the changelog for this update and installing it, I tried out GDM again and it always works now. Thanks again! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/1949026 Title: System hangs on purple screen Status in OEM Priority Project: Fix Released Status in nvidia-graphics-drivers-470 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-470 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-470 source package in Focal: Fix Released Status in nvidia-graphics-drivers-470 source package in Hirsute: Fix Released Status in nvidia-graphics-drivers-470 source package in Impish: Fix Released Bug description: [Impact] * In some race condition, the GDM starts before gdm-udev rule be applied. * That's because somehow the nvidia driver takes more times to do the runtime resume. Thus, apply the workaround to postpone to enable RTD3. [Test Plan] 1. In problematic machine, warn/cold boot the system. 2.1 System hangs on GDM login shell 2.2 After apply this patch, the system can enter the login screen. [Where problems could occur] * Postpone to enable RTD3 when binding driver should not impact the functionality since the power consumption usually not be consider in booting stage. --- We are facing an issue that GDM starts with Wayland instead of Xorg, despite of 61-gdm.rules' gdm-disable-wayland for NVIDIA graphics. The issue happens because gdm-disable-wayland is executed after GDM has started. The reason why the udev rules takes so long is because the the runtime suspended NVIDIA GFX takes more than 1 second to runtime resume, hence the driver starts the probing routine rather late. The proper solution is to impose a barrier like systemd-udev-settle.service before GDM, but limits to the GFX device only to avoid waiting for all udev rules are finished. Since such mechanism isn't available right now, workaround the issue by enabling runtime PM after driver is bound to avoid the runtime resume delay, and hope GDM always starts after the probing is done. Please backport below patch to supported nvidia-drivers: https://github.com/tseliot/nvidia-graphics-drivers/pull/41/commits/7e9e4d4a827dc9da0e27058871034245ae4b7508 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1949026/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
