[Kernel-packages] [Bug 1949026] Re: System hangs on purple screen
This bug was fixed in the package nvidia-graphics-drivers-470 - 470.86-0ubuntu1 --- nvidia-graphics-drivers-470 (470.86-0ubuntu1) jammy; urgency=medium * New upstream release (LP: #1950665): - Fixed a regression which prevented DisplayPort and HDMI 2.1 variable refresh rate (VRR) G-SYNC Compatible monitors from functioning correctly in variable refresh rate mode, resulting in issues such as flickering. -- Alberto Milone Thu, 11 Nov 2021 16:47:27 +0100 ** Changed in: nvidia-graphics-drivers-470 (Ubuntu) Status: Confirmed => Fix Released -- 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: Fix Released 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
[Kernel-packages] [Bug 1949026] Re: System hangs on purple screen
Out of curiosity, I tried reverting this fix in /lib/udev/rules.d/71-nvidia.rules -- and it still works, no freeze on the login screen. So I guess my problem was fixed by something else after all, maybe the driver update itself. Or I was lucky to avoid the race condition... who knows. -- 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
[Kernel-packages] [Bug 1949026] Re: System hangs on purple screen
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers-470 (Ubuntu) Status: New => Confirmed -- 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
[Kernel-packages] [Bug 1949026] Re: System hangs on purple screen
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
[Kernel-packages] [Bug 1949026] Re: System hangs on purple screen
** Changed in: oem-priority Status: Triaged => Fix Released -- 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: New 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
[Kernel-packages] [Bug 1949026] Re: System hangs on purple screen
This bug was fixed in the package nvidia-graphics-drivers-470 - 470.82.00-0ubuntu0.20.04.1 --- nvidia-graphics-drivers-470 (470.82.00-0ubuntu0.20.04.1) focal; urgency=medium * New upstream release (LP: #1948025): - Fixed a bug that can cause a kernel crash in SLI Mosaic configurations. - Added support for the EGL_NV_robustness_video_memory_purge. [ Kai-Heng Feng ] * debian/71-nvidia.rules: - Enable runtime PM after driver is bound (LP: #1949026). -- Alberto Milone Tue, 26 Oct 2021 15:44:04 +0200 ** Changed in: nvidia-graphics-drivers-470 (Ubuntu Focal) Status: Fix Committed => Fix Released -- 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: Triaged Status in nvidia-graphics-drivers-470 package in Ubuntu: New 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
[Kernel-packages] [Bug 1949026] Re: System hangs on purple screen
This bug was fixed in the package nvidia-graphics-drivers-470 - 470.82.00-0ubuntu0.21.04.1 --- nvidia-graphics-drivers-470 (470.82.00-0ubuntu0.21.04.1) hirsute; urgency=medium * New upstream release (LP: #1948025): - Fixed a bug that can cause a kernel crash in SLI Mosaic configurations. - Added support for the EGL_NV_robustness_video_memory_purge. [ Kai-Heng Feng ] * debian/71-nvidia.rules: - Enable runtime PM after driver is bound (LP: #1949026). -- Alberto Milone Tue, 26 Oct 2021 15:42:15 +0200 ** Changed in: nvidia-graphics-drivers-470 (Ubuntu Bionic) Status: Fix Committed => Fix Released -- 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: Triaged Status in nvidia-graphics-drivers-470 package in Ubuntu: New Status in nvidia-graphics-drivers-470 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-470 source package in Focal: Fix Committed 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
[Kernel-packages] [Bug 1949026] Re: System hangs on purple screen
This bug was fixed in the package nvidia-graphics-drivers-470 - 470.82.00-0ubuntu0.21.10.1 --- nvidia-graphics-drivers-470 (470.82.00-0ubuntu0.21.10.1) impish; urgency=medium * New upstream release (LP: #1948025): - Fixed a bug that can cause a kernel crash in SLI Mosaic configurations. - Added support for the EGL_NV_robustness_video_memory_purge. [ Kai-Heng Feng ] * debian/71-nvidia.rules: - Enable runtime PM after driver is bound (LP: #1949026). -- Alberto Milone Tue, 26 Oct 2021 12:39:25 +0200 ** Changed in: nvidia-graphics-drivers-470 (Ubuntu Impish) Status: Fix Committed => Fix Released ** Changed in: nvidia-graphics-drivers-470 (Ubuntu Hirsute) Status: Fix Committed => Fix Released -- 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: Triaged Status in nvidia-graphics-drivers-470 package in Ubuntu: New Status in nvidia-graphics-drivers-470 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-470 source package in Focal: Fix Committed 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
[Kernel-packages] [Bug 1949026] Re: System hangs on purple screen
This bug was fixed in the package nvidia-graphics-drivers-470 - 470.82.00-0ubuntu0.18.04.1 --- nvidia-graphics-drivers-470 (470.82.00-0ubuntu0.18.04.1) bionic; urgency=medium * New upstream release (LP: #1948025): - Fixed a bug that can cause a kernel crash in SLI Mosaic configurations. - Added support for the EGL_NV_robustness_video_memory_purge. [ Kai-Heng Feng ] * debian/71-nvidia.rules: - Enable runtime PM after driver is bound (LP: #1949026). -- Alberto Milone Tue, 26 Oct 2021 15:44:51 +0200 -- 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: Triaged Status in nvidia-graphics-drivers-470 package in Ubuntu: New Status in nvidia-graphics-drivers-470 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-470 source package in Focal: Fix Committed 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
[Kernel-packages] [Bug 1949026] Re: System hangs on purple screen
** Tags added: originate-from-1943787 -- 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: Triaged Status in nvidia-graphics-drivers-470 package in Ubuntu: New Status in nvidia-graphics-drivers-470 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-470 source package in Focal: Fix Committed Status in nvidia-graphics-drivers-470 source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-470 source package in Impish: Fix Committed 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
[Kernel-packages] [Bug 1949026] Re: System hangs on purple screen
Hello jeremyszu, or anyone else affected, Accepted nvidia-graphics-drivers-470 into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/nvidia-graphics- drivers-470/470.82.00-0ubuntu0.18.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: nvidia-graphics-drivers-470 (Ubuntu Bionic) Status: New => Fix Committed ** Tags added: verification-needed-bionic -- 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: Triaged Status in nvidia-graphics-drivers-470 package in Ubuntu: New Status in nvidia-graphics-drivers-470 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-470 source package in Focal: Fix Committed Status in nvidia-graphics-drivers-470 source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-470 source package in Impish: Fix Committed 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
[Kernel-packages] [Bug 1949026] Re: System hangs on purple screen
Hello jeremyszu, or anyone else affected, Accepted nvidia-graphics-drivers-470 into impish-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/nvidia-graphics- drivers-470/470.82.00-0ubuntu0.21.10.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- impish to verification-done-impish. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-impish. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: nvidia-graphics-drivers-470 (Ubuntu Impish) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-impish ** Changed in: nvidia-graphics-drivers-470 (Ubuntu Hirsute) Status: New => Fix Committed ** Tags added: verification-needed-hirsute -- 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: Triaged Status in nvidia-graphics-drivers-470 package in Ubuntu: New Status in nvidia-graphics-drivers-470 source package in Focal: Fix Committed Status in nvidia-graphics-drivers-470 source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-470 source package in Impish: Fix Committed 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
[Kernel-packages] [Bug 1949026] Re: System hangs on purple screen
** Description changed: + [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 -- 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: Triaged Status in nvidia-graphics-drivers-470 package in Ubuntu: New 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
[Kernel-packages] [Bug 1949026] Re: System hangs on purple screen
** Tags removed: originate-from-1943787 -- 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: Triaged Status in nvidia-graphics-drivers-470 package in Ubuntu: New Bug description: 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
