[Bug 93029] New: Hangcheck timer too agressive to pass dEQP for SNBGT1
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Thu Nov 19 15:02:10 PST 2015
https://bugs.freedesktop.org/show_bug.cgi?id=93029
Bug ID: 93029
Summary: Hangcheck timer too agressive to pass dEQP for SNBGT1
Product: DRI
Version: XOrg git
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: DRM/Intel
Assignee: intel-gfx-bugs at lists.freedesktop.org
Reporter: mark.a.janes at intel.com
QA Contact: intel-gfx-bugs at lists.freedesktop.org
CC: intel-gfx-bugs at lists.freedesktop.org
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.
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are on the CC list for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20151119/ce23b76e/attachment.html>
More information about the intel-gfx-bugs
mailing list