<html>
    <head>
      <base href="https://bugs.freedesktop.org/" />
    </head>
    <body>
      <p>
        <div>
            <b><a class="bz_bug_link 
          bz_status_RESOLVED  bz_closed"
   title="RESOLVED FIXED - DRI3 rendering gets stuck waiting for present idle notify event"
   href="https://bugs.freedesktop.org/show_bug.cgi?id=84252#c57">Comment # 57</a>
              on <a class="bz_bug_link 
          bz_status_RESOLVED  bz_closed"
   title="RESOLVED FIXED - DRI3 rendering gets stuck waiting for present idle notify event"
   href="https://bugs.freedesktop.org/show_bug.cgi?id=84252">bug 84252</a>
              from <span class="vcard"><a class="email" href="mailto:rdieter@math.unl.edu" title="Rex Dieter <rdieter@math.unl.edu>"> <span class="fn">Rex Dieter</span></a>
</span></b>
        <pre>I've a downstream user
<a href="https://bugzilla.redhat.com/show_bug.cgi?id=1193742#c45">https://bugzilla.redhat.com/show_bug.cgi?id=1193742#c45</a>
that recently experienced another deadlock (in plasmashell), using the latest
commits referenced in this report.

#0  0x00000035130f666d in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x0000003d9c60a182 in _xcb_conn_wait (__timeout=-1, __nfds=1,
__fds=0x7ffe1eecb730) at /usr/include/bits/poll2.h:46
#2  0x0000003d9c60a182 in _xcb_conn_wait (c=c@entry=0x1007ff0,
cond=cond@entry=0x58bc8f8, vector=vector@entry=0x0, count=count@entry=0x0) at
xcb_conn.c:459
#3  0x0000003d9c60bd49 in xcb_wait_for_special_event (c=c@entry=0x1007ff0,
se=0x58bc8d0) at xcb_in.c:744
#4  0x0000003708e49e72 in dri3_find_back (c=c@entry=0x1007ff0,
priv=priv@entry=0x87cd3a0) at dri3_glx.c:1263
#5  0x0000003708e4ac8f in dri3_get_buffers (driDrawable=0x87cd3a0,
loaderPrivate=0x87cd3a0, buffer_type=dri3_buffer_back, format=4107) at
dri3_glx.c:1289
#6  0x0000003708e4ac8f in dri3_get_buffers
(driDrawable=driDrawable@entry=0x463e0a0, format=4107,
stamp=stamp@entry=0x463e0d0, loaderPrivate=loaderPrivate@entry=0x87cd3a0,
buffer_mask=<optimized out>, buffer_mask@entry=1,
buffers=buffers@entry=0x7ffe1eecb980) at dri3_glx.c:1466
#7  0x00007f09f73ae14b in intel_update_renderbuffers (drawable=0x463e0a0,
brw=0x2b06018) at brw_context.c:1527
#8  0x00007f09f73ae14b in intel_update_renderbuffers
(context=context@entry=0x2af37b0, drawable=drawable@entry=0x463e0a0) at
brw_context.c:1242
#9  0x00007f09f73ae4a1 in intel_prepare_render (brw=brw@entry=0x2b06018) at
brw_context.c:1263
#10 0x00007f09f73a21c0 in brw_clear (ctx=0x2b06018, mask=50) at brw_clear.c:234
#11 0x0000003715f28bfa in QSGBatchRenderer::Renderer::renderBatches()
(this=this@entry=0x8730b40)


Is this the same issue or should we open a separate report?</pre>
        </div>
      </p>
      <hr>
      <span>You are receiving this mail because:</span>
      
      <ul>
          <li>You are the QA Contact for the bug.</li>
          <li>You are the assignee for the bug.</li>
      </ul>
    </body>
</html>