<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body><table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Priority</th>
<td>high
</td>
</tr>
<tr>
<th>Bug ID</th>
<td><a class="bz_bug_link
bz_status_NEW "
title="NEW --- - [BSW]Run some piglit cases sporadically report *ERROR* Failed to reset chip: -110"
href="https://bugs.freedesktop.org/show_bug.cgi?id=81203">81203</a>
</td>
</tr>
<tr>
<th>CC</th>
<td>intel-gfx-bugs@lists.freedesktop.org
</td>
</tr>
<tr>
<th>Assignee</th>
<td>intel-gfx-bugs@lists.freedesktop.org
</td>
</tr>
<tr>
<th>Summary</th>
<td>[BSW]Run some piglit cases sporadically report *ERROR* Failed to reset chip: -110
</td>
</tr>
<tr>
<th>QA Contact</th>
<td>intel-gfx-bugs@lists.freedesktop.org
</td>
</tr>
<tr>
<th>Severity</th>
<td>critical
</td>
</tr>
<tr>
<th>Classification</th>
<td>Unclassified
</td>
</tr>
<tr>
<th>OS</th>
<td>Linux (All)
</td>
</tr>
<tr>
<th>Reporter</th>
<td>huax.lu@intel.com
</td>
</tr>
<tr>
<th>Hardware</th>
<td>All
</td>
</tr>
<tr>
<th>Status</th>
<td>NEW
</td>
</tr>
<tr>
<th>Version</th>
<td>XOrg CVS
</td>
</tr>
<tr>
<th>Component</th>
<td>DRM/Intel
</td>
</tr>
<tr>
<th>Product</th>
<td>DRI
</td>
</tr></table>
<p>
<div>
<pre>System Environment:
--------------------------
Platform: BSW
Libdrm:
(master)libdrm-2.4.54-17-ge8c3c1358ecaf4e90f7d43762357ae6f8e2022b6
Mesa: (master)50bbe49c330095ba451d0f48c56759d148a609c2
Xserver:
(master)xorg-server-1.15.99.902-121-g2f5cf9ff9a0f713b7e038636484c77f113a5f10a
Xf86_video_intel:(master)2.99.912-227-g8587b2fff218537c6ff568ac3ef561f0d39f03ff
Libva: (master)c61d8c6ce9ffc27320e9e177c1e1123d5f1b5014
Libva_intel_driver:(master)c5cb17ea86f0065a939d3636dd26651c93d497c8
Kernel: drm-intel-nightly/16025dad8e9964a5810385f755d43f1c48d6fdcc
Bug detailed description:
-------------------------
Many Piglit cases report <3>[ 146.267151] [drm:i915_reset] *ERROR* Failed to
reset chip: -110. It happens on -queued and -nightly kernel. Run it 20 cycles
on -fixes kernel, it works well.
This error blocks other piglit cases.
[root@x-bsw01 piglit]# bin/shader_runner
/home/GFX/Test/Piglit/piglit/generated_tests/spec/glsl-1.30/execution/built-in-functions/vs-op-lshift-ivec2-uvec2.shader_test
-auto
PIGLIT: {"result": "pass" }
[root@x-bsw01 piglit]# bin/shader_runner
/home/GFX/Test/Piglit/piglit/generated_tests/spec/glsl-1.30/execution/built-in-functions/vs-op-lshift-ivec2-uvec2.shader_test
-auto
PIGLIT: {"result": "pass" }
[root@x-bsw01 piglit]# bin/shader_runner
/home/GFX/Test/Piglit/piglit/generated_tests/spec/glsl-1.30/execution/built-in-functions/vs-op-lshift-ivec2-uvec2.shader_test
-auto
PIGLIT: {"result": "pass" }
[root@x-bsw01 piglit]# bin/shader_runner
/home/GFX/Test/Piglit/piglit/generated_tests/spec/glsl-1.30/execution/built-in-functions/vs-op-lshift-ivec2-uvec2.shader_test
-auto
Probe color at (0,0)
Expected: 0.000000 1.000000 0.000000 1.000000
Observed: 0.000000 0.000000 0.000000 0.000000
Probe color at (1,0)
Expected: 0.000000 1.000000 0.000000 1.000000
Observed: 0.000000 0.000000 0.000000 0.000000
Probe color at (2,0)
Expected: 0.000000 1.000000 0.000000 1.000000
Observed: 0.000000 0.000000 0.000000 0.000000
intel_do_flush_locked failed: Input/output error
[root@x-bsw01 piglit]# bin/shader_runner
/home/GFX/Test/Piglit/piglit/generated_tests/spec/glsl-1.30/execution/built-in-functions/vs-op-lshift-ivec2-uvec2.shader_test
-auto
intel_do_flush_locked failed: Input/output error
Reproduce steps:
-------------------------
1. xinit
2. gnome-session
3. bin/shader_runner
generated_tests/spec/glsl-1.30/execution/built-in-functions/vs-op-lshift-ivec2-uvec2.shader_test
-auto</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>