<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 - [drm/i915/icl]media driver see gpu hang issue caused by WaEnableStateCacheRedirectToCS context workaround configure for the L3 cache"
href="https://bugs.freedesktop.org/show_bug.cgi?id=110470">110470</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>[drm/i915/icl]media driver see gpu hang issue caused by WaEnableStateCacheRedirectToCS context workaround configure for the L3 cache
</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 (IA32)
</td>
</tr>
<tr>
<th>OS</th>
<td>Linux (All)
</td>
</tr>
<tr>
<th>Status</th>
<td>NEW
</td>
</tr>
<tr>
<th>Severity</th>
<td>major
</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>carry.lv@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>Created <span class=""><a href="attachment.cgi?id=144044" name="attach_144044" title="attached finding root cause">attachment 144044</a> <a href="attachment.cgi?id=144044&action=edit" title="attached finding root cause">[details]</a></span>
attached finding root cause
Media driver see gpu hang randomly for VME cases.
The issue is root caused. The reason is conflicting Settings of L3 were used in
UMD and KMD.
In picture 1 is the setting of KMD in function icl_ctx_workarounds_init, which
enabled State Cache redirect to CS Command buffer section(bit11 of MMIO
0x731C). However, the L3 configuration of UMD(in Picture2) didn't assign any
space for CS Command buffer.
I tried to remove the WaEnableStateCacheRedirectToCS in KMD, the issue is gone.
WaEnableStateCacheRedirectToCS context workaround configures the L3 cache to
benefit 3d workloads but media has different requirements.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are on the CC list for the bug.</li>
<li>You are the assignee for the bug.</li>
<li>You are the QA Contact for the bug.</li>
</ul>
</body>
</html>