[Regression in 460.27.04,460.32.03,460.39,...] Black screen: nvidia-modeset: ERROR: GPU:0: Failed to allocate display engine core DMA push buffer

The last working driver with my card is 455.45.01. All more recent driver versions break with a black screen after loading of nvidia-modeset: First, the screen goes black, then the backlight is toggled several times (about 10 times), finally it stays blank and dark. Logs show:

[    0.088017] Kernel command line: root=UUID=32278c21-b19c-47e0-8466-420bbb5a1642 ro rd.dm=0 nvidia-drm.modeset=1 net.ifnames=0 pcie_aspm=force initrd=boot\initramfs-5.9.11-gentoo.img
...
[    3.143143] nvidia-nvlink: Nvlink Core is being initialized, major device number 240
[    5.785170] NVRM: loading NVIDIA UNIX x86_64 Kernel Module  460.39  Thu Jan 21 21:54:06 UTC 2021
[    5.788860] nvidia-modeset: Loading NVIDIA Kernel Mode Setting Driver for UNIX platforms  460.39  Thu Jan 21 21:49:04 UTC 2021
[    5.790555] [drm] [nvidia-drm] [GPU ID 0x00000100] Loading driver
[   10.339660] [drm] Initialized nvidia-drm 0.0.0 20160202 for 0000:01:00.0 on minor 0
[   35.303161] nvidia-modeset: ERROR: GPU:0: Display engine push buffer channel allocation failed: 0x65 (Call timed out [NV_ERR_TIMEOUT])
[   35.304615] nvidia-modeset: ERROR: GPU:0: Failed to allocate display engine core DMA push buffer

I’ve attached a fresh nvidia-bugreport here, with 460.39 on kernel 5.9.11:
nvidia-bug-report.log.gz (1.1 MB)

I’ve already reported this with nvidia-bugreport for the older driver releases here:

It had been suggested to enable CSM, but boot via UEFI, which sadly is not possible on this device (and also did not help another user with a similar issue).
Further ideas or an acknowledgement of this regression would be greatly appreciated.

1 Like

Please uninstall the previous driver and install the latest driver cleanly.
Also update SBIOS to latest version and the share test results along with nvidia bug report with us.

Please uninstall the previous driver and install the latest driver cleanly.

I did that (as you can see in the existing report). The report of course also contains ABI mismatch errors from before the failing reboot (since I upgraded from within a graphical session), but all remnants of the old driver were removed cleanly, and the initramdisk was regenerated.

Also update SBIOS to latest version and the share test results along with nvidia bug report with us.

You mean the system BIOS? Indeed, it appears my vendor has released a new version patching a list of CVEs (according to changelog). I will install it today and check if it changes anything, thanks for the idea!

I’ve now updated to the latest available BIOS by my vendor (A17 from 22.7.2019). Sadly, the issue remains: Again, the screen toggles between “black with backlight on” and “black with backlight off” about 5 times, then finally stays dark.

Here’s a newly collected bug report with the new system BIOS and driver 460.39:
nvidia-bug-report.log.gz (1.1 MB)

Please let me know if there is any other information I can provide.

I have the same issue with nvidia-450/-460 and GeForce 920M.

Same issue with nvidia-460 on ubuntu 20 with Quadro M4000M

Again, same issue here: got the latest 460 on my Ubuntu and I now have to power it off every evening!
Please fix this asap!

Still reproducible for me with latest 465.27 (was hopeful since it had slightly related entries in the release notes).
The kernel error messages remain mostly the same:

[    5.795708] [drm] [nvidia-drm] [GPU ID 0x00000100] Loading driver
[   10.145507] [drm] Initialized nvidia-drm 0.0.0 20160202 for 0000:01:00.0 on minor 0
[   14.691126] nvidia-modeset: WARNING: GPU:0: Lost display notification (0:0x00000000); continuing.
[   35.151247] nvidia-modeset: ERROR: GPU:0: Display engine push buffer channel allocation failed: 0x65 (Call timed out [NV_ERR_TIMEOUT])
[   35.152258] nvidia-modeset: ERROR: GPU:0: Failed to allocate display engine core DMA push buffer

I also tried the new 465.27 driver and experience the exact same issue, as was discussed here.
Quadro M1000M on a HP Zbook Studio G3

Any update on this? I recently tried the 470 driver but that unfortunately did not fix the issue for me. (back on 450 now)

Any updates on the issue?

Nvidia has acknowledged the issue and is trying to reproduce it.

No updates from Nvidia since then.