-
Notifications
You must be signed in to change notification settings - Fork 215
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[NVIDIA] Explicit sync on nested Wayland with gamescope upscaling crashes from vkImportSemaphoreFdKHR failed
#1662
Comments
I haven't looked yet, but GameScope isn't by chance trying to directly import a DRM timeline syncobj FD into Vulkan as a timeline semaphore is it? That's definitely not allowed by any current spec, but probably works on Mesa drivers and not ours. Even if that's the case, we're not allowed to crash, so it'd still be a driver bug. Just wanted to see if it's a possibility. |
For future reference, I've filed NV-internal bug 5007734 to track this issue. |
this is probably best answered by @misyltoad or someone with a better understanding of the code than myself |
That is exactly what we are doing, works fine on Mesa. Why would this be forbidden by the spec? To my knowledge, there is no language that forbids importing a syncobj just because it's timeline -- it is just explicit that the type must match:
It's only forbidden to import timelines from syncobjs temporarily, which we don't do.
|
There is no language that allows importing a syncobj in the first place. OPAQUE_FD does not mean syncobj. It would be welcome if you could propose a new extension that provided a SYNCOBJ_FD handle type. |
It has long been decided that OPAQUE_FD is syncobj compatible on Linux. |
Is there an existing issue for this?
Are you using any gamescope patches or a forked version of gamescope?
Current Behavior
Using gamescope on NVIDIA with 555 series drivers or later causes gamescope to coredump after briefly launching but only showing a black window. The issue only occurs while using gamescope's upscaling, which implements explicit sync since #1463 was merged
This issue no longer occurs if you do one of several things:
ENABLE_GAMESCOPE_WSI=0 gamescope -F fsr -- vkcube
works, but you lose HDR without Gamescope WSIgamescope/src/Backends/DRMBackend.cpp
Line 72 in 6330a32
The issue also does not occur on the Vulkan developer driver series.
Steps To Reproduce
gamescope -F fsr -- vkcube
or any other upscaling methodHardware information
Software information
Which gamescope backends have the issue you are reporting?
Logging, screenshots, or anything else
Looking at my logs, it seems like it happens after Gamecope WSI establishes its swapchain.
It generates the following coredump:
nvidia-bug-report.log.gz
The text was updated successfully, but these errors were encountered: