<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body><span class="vcard"><a class="email" href="mailto:matthew.d.roper@intel.com" title="Matt Roper <matthew.d.roper@intel.com>"> <span class="fn">Matt Roper</span></a>
</span> changed
<a class="bz_bug_link
bz_status_NEW "
title="NEW - [CI] igt@* - dmesg-warn - *ERROR* dp aux hw did not signal timeout!"
href="https://bugs.freedesktop.org/show_bug.cgi?id=105128">bug 105128</a>
<br>
<table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>What</th>
<th>Removed</th>
<th>Added</th>
</tr>
<tr>
<td style="text-align:right;">Severity</td>
<td>normal
</td>
<td>minor
</td>
</tr>
<tr>
<td style="text-align:right;">Priority</td>
<td>medium
</td>
<td>low
</td>
</tr>
<tr>
<td style="text-align:right;">i915 platform</td>
<td>
</td>
<td>TGL
</td>
</tr></table>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - [CI] igt@* - dmesg-warn - *ERROR* dp aux hw did not signal timeout!"
href="https://bugs.freedesktop.org/show_bug.cgi?id=105128#c15">Comment # 15</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - [CI] igt@* - dmesg-warn - *ERROR* dp aux hw did not signal timeout!"
href="https://bugs.freedesktop.org/show_bug.cgi?id=105128">bug 105128</a>
from <span class="vcard"><a class="email" href="mailto:matthew.d.roper@intel.com" title="Matt Roper <matthew.d.roper@intel.com>"> <span class="fn">Matt Roper</span></a>
</span></b>
<pre>(In reply to Lakshmi from <a href="show_bug.cgi?id=105128#c12">comment #12</a>)
<span class="quote">> (In reply to Matt Roper from <a href="show_bug.cgi?id=105128#c10">comment #10</a>)
> > Also, all failures within the last month have been on gen9 platforms (KBL or
> > SKL here, and BXT in 111556) so removing g45 from the platform list and
> > adding these three gen9 platforms.
>
> Matt, failures are also seen on TGL. Let me know we need to create a
> separate bug for TGL. If we don't need a separate issue, how do you see the
> severity and priority of this bug?</span >
I think this bug is fine for the TGL failures as well.
As far as I can tell, this bug is harmless. Our driver complains that the
hardware didn't do something we expected it to (report completion of something
that we know has to be complete by this point), but we still detect that
condition and proceed properly. I don't think there would be any visible
impact to an end-user in this case. I think dropping this to low importance is
reasonable here; once the more important issues are dealt with we may want to
work with the hardware guys to figure out if there's anything the driver might
be doing that triggers this behavior occasionally or whether it's just a minor
hardware bug. If it does turn out to be a hardware bug that we can't control
then we'll probably want to downgrade the DRM_ERROR here to a DRM_DEBUG.</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 QA Contact for the bug.</li>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>