<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 - [SKL] GPU hangs in all benchmarks using compute shaders with drm-tip v4.19 kernel"
href="https://bugs.freedesktop.org/show_bug.cgi?id=108820">108820</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>[SKL] GPU hangs in all benchmarks using compute shaders with drm-tip v4.19 kernel
</td>
</tr>
<tr>
<th>Product</th>
<td>Mesa
</td>
</tr>
<tr>
<th>Version</th>
<td>git
</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>Keywords</th>
<td>regression
</td>
</tr>
<tr>
<th>Severity</th>
<td>normal
</td>
</tr>
<tr>
<th>Priority</th>
<td>medium
</td>
</tr>
<tr>
<th>Component</th>
<td>Drivers/DRI/i965
</td>
</tr>
<tr>
<th>Assignee</th>
<td>intel-3d-bugs@lists.freedesktop.org
</td>
</tr>
<tr>
<th>Reporter</th>
<td>eero.t.tamminen@intel.com
</td>
</tr>
<tr>
<th>QA Contact</th>
<td>intel-3d-bugs@lists.freedesktop.org
</td>
</tr></table>
<p>
<div>
<pre>Setup:
* SKL GT2 / GT3e
* Ubuntu 18.04
* *drm-tip* v4.19 kernel
* Mesa & X git head
Test-case:
* Run a test-case using compute shaders
Expected output:
* No GPU hangs (like with earlier Mesa commits)
Actual output:
* Recoverable GPU hangs in compute shader using test-cases:
- GfxBench Aztec Ruins, CarChase and Manhattan 3.1
- Sacha Willems' Vulkan compute demos
- SynMark CSDof / CSCloth
* Vulkan compute demos fail to run (other tests run successfully despite hangs)
This seems to be SKL specific, it's not visible on other HW.
This regression happened between following Mesa commits:
* dca35c598d: 2018-11-19 15:57:41: intel/fs,vec4: Fix a compiler warning
* a999798daa: 2018-11-20 17:09:22: meson: Add tests to suites
It also seems to be specific to *drm-tip* v4.19.0 kernel as I don't see it with
latest drm-tip v4.20.0-rc3 kernel. So it's also possible that it's a bug in
i915, that just gets triggered by Mesa change, and which got fixed later.
Sacha Willems' Vulkan Raytracing demo outputs following on first run:
---------------------------------
SPIR-V WARNING:
In file src/compiler/spirv/vtn_variables.c:1897
Source and destination types of SpvOpStore do not have the same ID (but are
compatible): 225 vs 212
14920 bytes into the SPIR-V binary
SPIR-V WARNING:
In file src/compiler/spirv/vtn_variables.c:1897
Source and destination types of SpvOpStore do not have the same ID (but are
compatible): 225 vs 212
10300 bytes into the SPIR-V binary
SPIR-V WARNING:
In file src/compiler/spirv/vtn_variables.c:1897
Source and destination types of SpvOpStore do not have the same ID (but are
compatible): 269 vs 256
10944 bytes into the SPIR-V binary
SPIR-V WARNING:
In file src/compiler/spirv/vtn_variables.c:1897
Source and destination types of SpvOpStore do not have the same ID (but are
compatible): 225 vs 212
11920 bytes into the SPIR-V binary
INTEL-MESA: error: src/intel/vulkan/anv_device.c:2091: GPU hung on one of our
command buffers (VK_ERROR_DEVICE_LOST)
vulkan_raytracing: base/vulkanexamplebase.cpp:651: void
VulkanExampleBase::submitFrame(): Assertion `res == VK_SUCCESS' failed.
-----------------------------
(Other runs show just the error and assert.)</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 the assignee for the bug.</li>
</ul>
</body>
</html>