<html>
    <head>
      <base href="https://bugs.freedesktop.org/" />
    </head>
    <body><table border="1" cellspacing="0" cellpadding="8">
        <tr>
          <th>Bug ID</th>
          <td><a class="bz_bug_link 
          bz_status_NEW "
   title="NEW - Stuck on render ring"
   href="https://bugs.freedesktop.org/show_bug.cgi?id=86626">86626</a>
          </td>
        </tr>

        <tr>
          <th>Summary</th>
          <td>Stuck on render ring
          </td>
        </tr>

        <tr>
          <th>Product</th>
          <td>DRI
          </td>
        </tr>

        <tr>
          <th>Version</th>
          <td>unspecified
          </td>
        </tr>

        <tr>
          <th>Hardware</th>
          <td>Other
          </td>
        </tr>

        <tr>
          <th>OS</th>
          <td>All
          </td>
        </tr>

        <tr>
          <th>Status</th>
          <td>NEW
          </td>
        </tr>

        <tr>
          <th>Severity</th>
          <td>normal
          </td>
        </tr>

        <tr>
          <th>Priority</th>
          <td>medium
          </td>
        </tr>

        <tr>
          <th>Component</th>
          <td>DRM/Intel
          </td>
        </tr>

        <tr>
          <th>Assignee</th>
          <td>intel-gfx-bugs@lists.freedesktop.org
          </td>
        </tr>

        <tr>
          <th>Reporter</th>
          <td>manday@gmx.net
          </td>
        </tr>

        <tr>
          <th>QA Contact</th>
          <td>intel-gfx-bugs@lists.freedesktop.org
          </td>
        </tr>

        <tr>
          <th>CC</th>
          <td>intel-gfx-bugs@lists.freedesktop.org
          </td>
        </tr></table>
      <p>
        <div>
        <pre>On Linux slate 3.16.5-gentoo #6 SMP Sat Nov 22 11:43:01 CET 2014 x86_64
Intel(R) Pentium(R) CPU 997 @ 1.60GHz GenuineIntel GNU/Linux if frequently
happens under X.org running (presumably triggered by firefox-bin) that first,
large portions of the screen render black, a drop in performance, quickly
followed by a deadlock (no SysReq will help). When the first signs of the issue
occur, I manage to drop into TTY and kill firefox which usually stabilizes the
situation. I can then grab dmesg and the error log, which you find attached.
Clearly, I can't assert that they contain everything related to the freeze,
since I can only obtain them if the actual freeze does not occur.

I will try to reproduce the issue with current 3.18 mainline but can not
promise that I'll again be as lucky as being able to grab the logs in the
narrow window before the actual freeze.</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 on the CC list for the bug.</li>
          <li>You are the assignee for the bug.</li>
      </ul>
    </body>
</html>