<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO - [skl] GPU hang in sway, unknown cause" href="https://bugs.freedesktop.org/show_bug.cgi?id=110135#c20">Comment # 20</a> on <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO - [skl] GPU hang in sway, unknown cause" href="https://bugs.freedesktop.org/show_bug.cgi?id=110135">bug 110135</a> from <a class="email" href="mailto:contact@emersion.fr" title="emersion <contact@emersion.fr>"> emersion</a> <pre>Hi, sway dev here. i915 devs: let me know if you need info about userspace. Our DRM code behaves more or less like Weston, so I'm not sure what could be wrong here. However I see that the Intel card is card1 and there are nouveau logs. What is your setup exactly? Is card0 a NVIDIA card? You could also e.g. run <a href="https://github.com/ascent12/drm_info">https://github.com/ascent12/drm_info</a> on your device to get information about what cards are plugged in and what are their capabilities. On multi-GPU setups we render on one primary GPU and use DMA-BUFs to copy buffers from the primary GPU to the secondary one (we don't do direct scan-out yet, this really is a copy). If you could share sway debug logs (sway -d >sway.log 2>&1) that would help figuring out the exact setup sway/wlroots runs on. If you connect all monitors to one card, you could force sway/wlroots to use only this card. This might or might not help, and will hide connectors of the other cards. You can do so by exporting WLR_DRM_DEVICES=/dev/dri/card0 (or card1).</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are on the CC list for the bug.</li> </ul> </body> </html>