Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 830604 - >=x11-drivers/nvidia-drivers-460.91.03-r2: Display engine push buffer channel allocation failed
Summary: >=x11-drivers/nvidia-drivers-460.91.03-r2: Display engine push buffer channel...
Status: RESOLVED UPSTREAM
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Ionen Wolkens
URL: https://forums.developer.nvidia.com/t...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-01-04 17:32 UTC by Oliver Freyermuth
Modified: 2022-01-04 18:26 UTC (History)
2 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Oliver Freyermuth 2022-01-04 17:32:47 UTC
The last functional nvidia-driver on my system appears to be 455.45.01-r2, which is not in portage anymore. 

An in-depth nvidia-bugreport is linked. 

To summarize:
- Hardware is NVIDIA Corporation GK104M [GeForce GTX 880M] (i.e. not supported anymore by >=495)
- With recent drivers, I observe a black screen with backlight being turned on and off, until finally the system ends up with a black screen (also on VTs), similar to 809482
- Unlike 809482, I also observe this with 460.91.03 and get the following messages in kernel logs:

Jan 10 19:05:20 localhost kernel: [   35.249151] nvidia-modeset: ERROR: GPU:0: Display engine push buffer channel allocation failed: 0x65 (Call timed out [NV_ERR_TIMEOUT])
Jan 10 19:05:20 localhost kernel: [   35.249945] nvidia-modeset: ERROR: GPU:0: Failed to allocate display engine core DMA push buffer

Reproducible: Always

Steps to Reproduce:
1. Install any >=x11-drivers/nvidia-drivers-460.91.03-r2 and regenerate initrd. 
2. Boot up. 
Actual Results:  
Observe black screen turning off and on, finally staying off and black, and error message in kernel log. 


I use nvidia-drm.modeset=1 (but the issue also turns up without that). 
According to the nvidia forums, several users are affected by this, and it does not seem to be card-related, but related to initialization order of the graphics hardware (potentially BIOS involved). 
Some users only experience this when exiting suspend-to-ram, some (like me) are affected right when booting up.
Comment 1 Ionen Wolkens gentoo-dev 2022-01-04 18:19:42 UTC
Sorry, I'm aware >=460 was still affected by some issues regarding suspend after power management changes, but 455.45.01 is from 2020 and is affected by several security vulnerabilities (450.119.03 would be a bit better but is also affected) -- which led me to remove 450 either way.

Like 460.xx branch they are also stuck on older Xorg and would have to be removed sooner or later either way.

So unfortunately I'd rather not officially restore them, and it'll have to wait for NVIDIA to release a fixed version.
Comment 2 Oliver Freyermuth 2022-01-04 18:26:41 UTC
Thanks for the quick response, that is completely understandable. 

Just to emphasize: In my case, this is not purely a power management issue, but it affects me (and also some others in the nvidia forums) directly on boot. So the system graphics is completely unusable with any more recent nvidia driver, i.e. those affected by the problem need to stay also with older Xorg (as long as possible) or migrate to nouveau - or newer hardware.