<html>
    <head>
      <base href="https://bugs.freedesktop.org/" />
    </head>
    <body><span class="vcard"><a class="email" href="mailto:chris@chris-wilson.co.uk" title="Chris Wilson <chris@chris-wilson.co.uk>"> <span class="fn">Chris Wilson</span></a>
</span> changed
              <a class="bz_bug_link 
          bz_status_RESOLVED  bz_closed"
   title="RESOLVED FIXED - [HD Graphics 4000] Segfault accessing rq->bo->handle"
   href="https://bugs.freedesktop.org/show_bug.cgi?id=91577">bug 91577</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;">Status</td>
           <td>NEW
           </td>
           <td>RESOLVED
           </td>
         </tr>

         <tr>
           <td style="text-align:right;">Resolution</td>
           <td>---
           </td>
           <td>FIXED
           </td>
         </tr></table>
      <p>
        <div>
            <b><a class="bz_bug_link 
          bz_status_RESOLVED  bz_closed"
   title="RESOLVED FIXED - [HD Graphics 4000] Segfault accessing rq->bo->handle"
   href="https://bugs.freedesktop.org/show_bug.cgi?id=91577#c39">Comment # 39</a>
              on <a class="bz_bug_link 
          bz_status_RESOLVED  bz_closed"
   title="RESOLVED FIXED - [HD Graphics 4000] Segfault accessing rq->bo->handle"
   href="https://bugs.freedesktop.org/show_bug.cgi?id=91577">bug 91577</a>
              from <span class="vcard"><a class="email" href="mailto:chris@chris-wilson.co.uk" title="Chris Wilson <chris@chris-wilson.co.uk>"> <span class="fn">Chris Wilson</span></a>
</span></b>
        <pre>Ok, made another tweak based on the new logs.

I think we have addressed the buggy failure handling in submission and the
buggy throttling when hitting resource starvation - but I haven't worked out
where that last segfault was coming from. So there is a crash lurking in there
somewhere with resource starvation. :(

In the meantime however we have stopped spamming the GPU and stopped running
out-of-memory in the first place. Overall, I think I can treat the bug as
resolved...

Thanks for the bug report, all the testing and feedback. Please reopen if you
can find a way to trigger it once more.</pre>
        </div>
      </p>
      <hr>
      <span>You are receiving this mail because:</span>
      
      <ul>
          <li>You are the QA Contact for the bug.</li>
      </ul>
    </body>
</html>