<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - glmark2-es2-wayland shortly freezes on some frames with egl_dri2 backend (Nouveau/GK20A)" href="https://bugs.freedesktop.org/show_bug.cgi?id=86690#c9">Comment # 9</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - glmark2-es2-wayland shortly freezes on some frames with egl_dri2 backend (Nouveau/GK20A)" href="https://bugs.freedesktop.org/show_bug.cgi?id=86690">bug 86690</a> from <a class="email" href="mailto:gnurou@gmail.com" title="Alexandre Courbot <gnurou@gmail.com>"> Alexandre Courbot</a> <pre>(been reminded we should have a drink one of these days! ;)) Mmm, since this happens *only* for Wayland EGL programs (e.g. no problem with DRM), I was hoping to see unexpected things happening at the Wayland level. But what seems even stranger is that I think I can see the fence release pushbuffers being queued *and* run by the GPU from the kernel side. So it may also be that the screen's fence value is properly updated but the new value not seen by user-space because of some memory incoherency.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>