<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - [nv20] glx-swap-event hangs X server" href="https://bugs.freedesktop.org/show_bug.cgi?id=101323#c1">Comment # 1</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - [nv20] glx-swap-event hangs X server" href="https://bugs.freedesktop.org/show_bug.cgi?id=101323">bug 101323</a> from <a class="email" href="mailto:imirkin@alum.mit.edu" title="Ilia Mirkin <imirkin@alum.mit.edu>"> Ilia Mirkin</a> <pre>A few things you may be interested in: (a) The pid always comes back as Xorg, since that's who opens the FD, even in a dri3 scenario. Only time that it's the real application is when you're using DRI3 *and* running on a secondary GPU. (b) Hangs in nouveau_bo_wait indicate that the GPU hung. Basically it's an ioctl that stalls until a fence is hit (the command for writing the fence is sent by the kernel on command submission). If it never returns, that means the fence is never hit. [Or there's a bug in our fence logic... I wonder if there's some sort of 32-bit wraparound sadness in there which is helped by piglit.] Since you have a reproducible hang, might want to check dmesg *before* running the test, and then seeing what happens. FWIW I always run piglit with "-x glx" -- that stuff never ends well on any generation with nouveau, and I've never had the desire to investigate it.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are the assignee for the bug.</li> </ul> </body> </html>