-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Sway fails to release GPU on udev remove command #8097
Comments
That's expected: |
Are you sure about that? Sway still reacts on udev command and disables output, this worked before and there is error message now (I've checked old logs). I've tried to run sway without |
Hm, yeah, nevermind, we still listen for the udev remove event in that case. cc @kennylevinsen for the libseat bits |
I suspect these errors are just because logind reacted to the event in parallel, removing the devices from the seat before we tried to clean them up. Neither libseat nor wlroots considers them fatal and proceeds with cleanup. My gut-feeling would be the renderer's fd, which is a lease off the master fd. I imagine it's invalidated when the master status is lost, but that does not close it. |
But a renderer is only created for the primary DRM device, not for secondary devices? |
Sway Version:
sway version 1.9 (debian 1.9-1+b1)
Debug Log:
Configuration File:
Reproduceable with default config file
Stack Trace:
N/A
Description:
Hi, I'm running into problems with swaywm releasing videocard DRI device.
I'm running sway on two AMD GPU virtualization setup, one is for host system (
card0
), other one is dynamically plugged/unplugged for guest(card1
).They are configured on start via
WLR_DRM_DEVICES=/dev/dri/card0:/dev/dri/card1
.When I need to release latter GPU for guest VM, I run udev command:
and then check for GPU release with:
Some time ago this trick stopped working, now on udev command sway shutdown second display, but still keep it's device open. Log messages indicate that sway cannot release GPU for some reason:
TLDR Steps to reproduce:
The text was updated successfully, but these errors were encountered: