<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body><span class="vcard"><a class="email" href="mailto:przanoni@gmail.com" title="Paulo Zanoni <przanoni@gmail.com>"> <span class="fn">Paulo Zanoni</span></a>
</span> changed
<a class="bz_bug_link
bz_status_NEEDINFO "
title="NEEDINFO - Screen Flickering on Intel Card"
href="https://bugs.freedesktop.org/show_bug.cgi?id=95010">bug 95010</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;">CC</td>
<td>
</td>
<td>przanoni@gmail.com
</td>
</tr></table>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEEDINFO "
title="NEEDINFO - Screen Flickering on Intel Card"
href="https://bugs.freedesktop.org/show_bug.cgi?id=95010#c30">Comment # 30</a>
on <a class="bz_bug_link
bz_status_NEEDINFO "
title="NEEDINFO - Screen Flickering on Intel Card"
href="https://bugs.freedesktop.org/show_bug.cgi?id=95010">bug 95010</a>
from <span class="vcard"><a class="email" href="mailto:przanoni@gmail.com" title="Paulo Zanoni <przanoni@gmail.com>"> <span class="fn">Paulo Zanoni</span></a>
</span></b>
<pre>(In reply to Carlo Abelli from <a href="show_bug.cgi?id=95010#c9">comment #9</a>)
<span class="quote">> As reported in the initial bug report I stated that enable_rc6 does resolve
> my issue, but I believe it to be a temporary fix for some. I believe it is
> temporary as Francisco Lopes mentioned that this helps his primary display
> but is not a fix for a secondary display. I'm not sure about enable_rc5, but
> if it works for some it might also be a valid temporary fix.</span >
Hello Carlo. Is the problem fixed for you, specifically, without the use of
i915.enable_rc6?
A note to everybody: we are aware of multiple problems that end up in "FIFO
underrun" messages on Skylake. The problem is that bugs get really hard to
manage when there are multiple users with multiple machines claiming they all
have the same bug, then some users claiming that the bug got fixed for them,
some other users claiming the bug still happens. It's much easier for us
developers to close duplicates than to "fork" multiple bugs in a single report.
So my proposal here is: if Carlo confirms the bug is indeed fixed for him, we
close this bug report and ask everybody else to submit new bug reports with the
relevant information for their specific systems.
Also, for everybody else still affected, please test the latest
drm-intel-nightly tree since we recently merged some more fixes related to this
(these fixes are going to land in stable Kernels at some point, but it's better
if you can test now and report any remaining issues).</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>
</ul>
</body>
</html>