<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body><table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Priority</th>
<td>medium
</td>
</tr>
<tr>
<th>Bug ID</th>
<td><a class="bz_bug_link
bz_status_NEW "
title="NEW --- - [HSW]I-G-T [drm:intel_dp_aux_wait_done] *ERROR* dp aux hw did not signal timeout when run gem_fence_thrash/bo-write-verify-threaded-x"
href="https://bugs.freedesktop.org/show_bug.cgi?id=64661">64661</a>
</td>
</tr>
<tr>
<th>CC</th>
<td>yangweix.shui@intel.com
</td>
</tr>
<tr>
<th>Assignee</th>
<td>intel-gfx-bugs@lists.freedesktop.org
</td>
</tr>
<tr>
<th>Summary</th>
<td>[HSW]I-G-T [drm:intel_dp_aux_wait_done] *ERROR* dp aux hw did not signal timeout when run gem_fence_thrash/bo-write-verify-threaded-x
</td>
</tr>
<tr>
<th>QA Contact</th>
<td>intel-gfx-bugs@lists.freedesktop.org
</td>
</tr>
<tr>
<th>Severity</th>
<td>normal
</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>unspecified
</td>
</tr>
<tr>
<th>Component</th>
<td>DRM/Intel
</td>
</tr>
<tr>
<th>Product</th>
<td>DRI
</td>
</tr></table>
<p>
<div>
<pre>Created <span class=""><a href="attachment.cgi?id=79378" name="attach_79378" title="dmesg">attachment 79378</a> <a href="attachment.cgi?id=79378&action=edit" title="dmesg">[details]</a></span>
dmesg
System Environment:
--------------------------
Arch: x86_64
Platform: Haswell
Kernel: (drm-intel-fixes) e6c6992522d3f74341f032bda2c76266057cc53b
Bug detailed description:
-------------------------
It happens on haswell with drm-intel-fixes kernel and drm-intel-next-queued
kernel.
It happens 3 times in 5 runs.
igt/gem_fence_thrash/bo-write-verify-threaded-y also has this issue.
output:
write-verify: threads 64, fences 32, tiling 1, surfaces per thread 2
write-verify: threads 160, fences 32, tiling 1, surfaces per thread 2
write-verify: threads 320, fences 32, tiling 1, surfaces per thread 2
write-verify: threads 640, fences 32, tiling 1, surfaces per thread 2
ERROR in dmesg:
<3>[ 841.280866] [drm:intel_dp_aux_wait_done] *ERROR* dp aux hw did not signal
timeout (has irq: 1)!
<3>[ 841.280916] [drm:intel_dp_aux_ch] *ERROR* dp_aux_ch not done status
0xa145004a
<3>[ 863.359327] [drm:intel_dp_aux_wait_done] *ERROR* dp aux hw did not signal
timeout (has irq: 1)!
<3>[ 867.474189] [drm:intel_dp_aux_wait_done] *ERROR* dp aux hw did not signal
timeout (has irq: 1)!
<3>[ 878.394119] [drm:intel_dp_aux_wait_done] *ERROR* dp aux hw did not signal
timeout (has irq: 1)!
<3>[ 881.852162] [drm:intel_dp_aux_wait_done] *ERROR* dp aux hw did not signal
timeout (has irq: 1)!
<3>[ 889.526997] [drm:intel_dp_aux_wait_done] *ERROR* dp aux hw did not signal
timeout (has irq: 1)!
<3>[ 892.958625] [drm:intel_dp_aux_wait_done] *ERROR* dp aux hw did not signal
timeout (has irq: 1)!
<3>[ 900.478867] [drm:intel_dp_aux_wait_done] *ERROR* dp aux hw did not signal
timeout (has irq: 1)!
<3>[ 904.527499] [drm:intel_dp_aux_wait_done] *ERROR* dp aux hw did not signal
timeout (has irq: 1)!
<3>[ 904.542026] [drm:intel_dp_aux_wait_done] *ERROR* dp aux hw did not signal
timeout (has irq: 1)!
<3>[ 907.930553] [drm:intel_dp_aux_wait_done] *ERROR* dp aux hw did not signal
timeout (has irq: 1)!
<3>[ 934.148787] [drm:intel_dp_aux_wait_done] *ERROR* dp aux hw did not signal
timeout (has irq: 1)!
<3>[ 934.149825] [drm:intel_dp_aux_ch] *ERROR* dp_aux_ch not done status
0xa145004a
<3>[ 937.528233] [drm:intel_dp_aux_wait_done] *ERROR* dp aux hw did not signal
timeout (has irq: 1)!
<3>[ 940.999809] [drm:intel_dp_aux_wait_done] *ERROR* dp aux hw did not signal
timeout (has irq: 1)!
<3>[ 941.030577] [drm:intel_dp_aux_wait_done] *ERROR* dp aux hw did not signal
timeout (has irq: 1)!
Reproduce steps:
----------------
1. ./gem_fence_thrash --run-subtest bo-write-verify-threaded-x
2. dmesg -r | egrep "<[1-6]>" |grep drm</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>