<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body><span class="vcard"><a class="email" href="mailto:conselvan2@gmail.com" title="Ander Conselvan de Oliveira <conselvan2@gmail.com>"> <span class="fn">Ander Conselvan de Oliveira</span></a>
</span> changed
<a class="bz_bug_link
bz_status_ASSIGNED "
title="ASSIGNED - [IVB Bisected] Both DVI/DP monitors are black after X rotation + S3"
href="https://bugs.freedesktop.org/show_bug.cgi?id=90468">bug 90468</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>ASSIGNED
</td>
</tr>
<tr>
<td style="text-align:right;">See Also</td>
<td>
</td>
<td>https://bugs.freedesktop.org/show_bug.cgi?id=90396
</td>
</tr>
<tr>
<td style="text-align:right;">Assignee</td>
<td>intel-gfx-bugs@lists.freedesktop.org
</td>
<td>conselvan2@gmail.com
</td>
</tr></table>
<p>
<div>
<b><a class="bz_bug_link
bz_status_ASSIGNED "
title="ASSIGNED - [IVB Bisected] Both DVI/DP monitors are black after X rotation + S3"
href="https://bugs.freedesktop.org/show_bug.cgi?id=90468#c19">Comment # 19</a>
on <a class="bz_bug_link
bz_status_ASSIGNED "
title="ASSIGNED - [IVB Bisected] Both DVI/DP monitors are black after X rotation + S3"
href="https://bugs.freedesktop.org/show_bug.cgi?id=90468">bug 90468</a>
from <span class="vcard"><a class="email" href="mailto:conselvan2@gmail.com" title="Ander Conselvan de Oliveira <conselvan2@gmail.com>"> <span class="fn">Ander Conselvan de Oliveira</span></a>
</span></b>
<pre>(In reply to Jani Nikula from <a href="show_bug.cgi?id=90468#c18">comment #18</a>)
<span class="quote">> Just that we'll need to either a) identify and backport the fix from
> drm-intel-next-queued (currently aimed at v4.3) to drm-intel-next-fixes
> (currently aimed at v4.2), *or* if that's not feasible,</span >
Unfortunately the fix in -nightly was one of the patches that was reverted
because of causing other issues.
<span class="quote">> b) write a different fix for drm-intel-next-fixes.</span >
The root cause here is the same as <a class="bz_bug_link
bz_status_NEEDINFO "
title="NEEDINFO - [PNV/HSW/BDW/BSW] force restore modeset fails with multiple connectors ( [drm:drm_atomic_helper_check_modeset] enabled/connectors mismatch)"
href="show_bug.cgi?id=90396">bug 90396</a>. The way the atomic state is set
up causes the call to intel_crtc_restore_mode() to be aborted, since it tries
to enable more than once CRTC but only sets up the encoders for one of them.
I tested a simple fix for the issue above today, but it uncovered another
issue. The modeset path now copies the atomic state to the staged config. But
the force restore path does up to 3 modesets, and each of those need to have
the staged config from before the suspend. Since that's overwritten, we only
restore the mode correctly for pipe A.</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 on the CC list for the bug.</li>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>