<html>
    <head>
      <base href="https://bugs.freedesktop.org/">
    </head>
    <body><span class="vcard"><a class="email" href="mailto:bruce.cherniak@intel.com" title="Bruce Cherniak <bruce.cherniak@intel.com>"> <span class="fn">Bruce Cherniak</span></a>
</span> changed
          <a class="bz_bug_link 
          bz_status_NEW "
   title="NEW - [swr] often gets stuck in piglit's glx-multi-context-single-window test"
   href="https://bugs.freedesktop.org/show_bug.cgi?id=103732">bug 103732</a>
          <br>
             <table border="1" cellspacing="0" cellpadding="8">
          <tr>
            <th>What</th>
            <th>Removed</th>
            <th>Added</th>
          </tr>

         <tr>
           <td style="text-align:right;">Component</td>
           <td>Mesa core
           </td>
           <td>Drivers/Gallium/swr
           </td>
         </tr></table>
      <p>
        <div>
            <b><a class="bz_bug_link 
          bz_status_NEW "
   title="NEW - [swr] often gets stuck in piglit's glx-multi-context-single-window test"
   href="https://bugs.freedesktop.org/show_bug.cgi?id=103732#c7">Comment # 7</a>
              on <a class="bz_bug_link 
          bz_status_NEW "
   title="NEW - [swr] often gets stuck in piglit's glx-multi-context-single-window test"
   href="https://bugs.freedesktop.org/show_bug.cgi?id=103732">bug 103732</a>
              from <span class="vcard"><a class="email" href="mailto:bruce.cherniak@intel.com" title="Bruce Cherniak <bruce.cherniak@intel.com>"> <span class="fn">Bruce Cherniak</span></a>
</span></b>
        <pre>I'll take a look into this.  The first thing I notice, is that you are running
with the DRI drivers.  Most of our customers use only the standalone GLX
drivers.  We do not test DRI heavily.

You appear to be running a debug build (from the stderr output) of either mesa
or llvm.  Does this occur with release build as well?  And, is there a reason
you are running with a debug build?

>From the very complete BT (thank you!), it appears that the api thread is
waiting for a fence to complete, but all of the worker threads are sitting in
idle -- suggesting that the fence should be complete.  Once you hit this stuck
loop, can you step into swr_is_fence_done and "print *fence".

Thanks.  I'll report back as soon as I find anything.

(assigning back to Gallium/swr until something suggests otherwise)</pre>
        </div>
      </p>


      <hr>
      <span>You are receiving this mail because:</span>

      <ul>
          <li>You are the assignee for the bug.</li>
          <li>You are the QA Contact for the bug.</li>
      </ul>
    </body>
</html>