<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_RESOLVED bz_closed"
title="RESOLVED DUPLICATE - [CI][DRMTIP] igt@kms_flip@dpms-vs-vblank-race - fail - Failed assertion: drmModeConnectorSetProperty(fd, connector->connector_id, dpms, mode) == 0"
href="https://bugs.freedesktop.org/show_bug.cgi?id=111775">bug 111775</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;">Status</td>
<td>NEW
</td>
<td>RESOLVED
</td>
</tr>
<tr>
<td style="text-align:right;">Resolution</td>
<td>---
</td>
<td>DUPLICATE
</td>
</tr></table>
<p>
<div>
<b><a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED DUPLICATE - [CI][DRMTIP] igt@kms_flip@dpms-vs-vblank-race - fail - Failed assertion: drmModeConnectorSetProperty(fd, connector->connector_id, dpms, mode) == 0"
href="https://bugs.freedesktop.org/show_bug.cgi?id=111775#c2">Comment # 2</a>
on <a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED DUPLICATE - [CI][DRMTIP] igt@kms_flip@dpms-vs-vblank-race - fail - Failed assertion: drmModeConnectorSetProperty(fd, connector->connector_id, dpms, mode) == 0"
href="https://bugs.freedesktop.org/show_bug.cgi?id=111775">bug 111775</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>Another link training failure that results in us not being able to drive the
requested mode. The IGT signature is slightly different this time because the
failure happens while using the legacy ConnectorSetProperty() interface to
toggle DPMS, rather than the more common modesetting interfaces, but the end
result is the same --- the underlying atomic transaction is rejected and EINVAL
(22) is propagated up to userspace as the error code.
In this case the modeline being attempted is
"1920x1080": 60 148500 1920 2008 2052 2200 1080 1084 1089 1125 0x48 0x5
The 148500 clock on this mode * a minimum RGB bpp of 18 means that we require a
data rate of 2683000/8 = 334125 to drive this mode. However the previous link
training gave us
<7> [354.746236] [drm:intel_dp_compute_config [i915]] DP link computation with
max lane count 2 max rate 162000 max bpp 24 pixel clock 148500KHz
Since 334125 > 2*162000, we don't have enough bandwidth to drive the desired
mode.
*** This bug has been marked as a duplicate of <a class="bz_bug_link
bz_status_NEW "
title="NEW - [CI][DRMTIP] Random tests - fail - Failed assertion: ret == 0, error: -22 != 0"
href="show_bug.cgi?id=111185">bug 111185</a> ***</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
<li>You are the QA Contact for the bug.</li>
<li>You are on the CC list for the bug.</li>
</ul>
</body>
</html>