<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 - Hangcheck timer too agressive to pass dEQP for SNBGT1"
   href="https://bugs.freedesktop.org/show_bug.cgi?id=93029">93029</a>
          </td>
        </tr>

        <tr>
          <th>Summary</th>
          <td>Hangcheck timer too agressive to pass dEQP for SNBGT1
          </td>
        </tr>

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

        <tr>
          <th>Version</th>
          <td>XOrg git
          </td>
        </tr>

        <tr>
          <th>Hardware</th>
          <td>x86-64 (AMD64)
          </td>
        </tr>

        <tr>
          <th>OS</th>
          <td>Linux (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>mark.a.janes@intel.com
          </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>Mesa began running Google's dEQP validation suite on older platforms, and found
that spurious/random GPU hangs occured on SNB, especially SNBGT1.

Turning off gpu reset did not prevent GPU HANGS as reported in dmesg.  In spite
of the detected hangs, the test suite completed without error.  If the GPU were
*really* hung, we would be able to see which dEQP test was stuck.  However, the
test suite completed without incident.

Disabling hang check on SNB systems has eliminated these spurious dEQP failures
entirely.

Google's suite includes some tests which are intended to generate GPU Hangs (we
skip those) and others which have long-running shaders that may not appear to
make progress.

Based on this behavior, it seems reasonable to tailor the hangcheck timer to
the platform.

Passing dEQP is important because Google uses the suite to validate platforms
for ChromeOS.  Sandy bridge is an important ChromeOS platform.  We don't want a
stabel Mesa release to be blocked from release because of spurious GPU Hangs on
SNB.</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>