<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_RESOLVED bz_closed"
title="RESOLVED FIXED - [SKL] Flashing black screen ([drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun)"
href="https://bugs.freedesktop.org/show_bug.cgi?id=94605">bug 94605</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;">Resolution</td>
<td>---
</td>
<td>FIXED
</td>
</tr>
<tr>
<td style="text-align:right;">Status</td>
<td>NEEDINFO
</td>
<td>RESOLVED
</td>
</tr></table>
<p>
<div>
<b><a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED FIXED - [SKL] Flashing black screen ([drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun)"
href="https://bugs.freedesktop.org/show_bug.cgi?id=94605#c112">Comment # 112</a>
on <a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED FIXED - [SKL] Flashing black screen ([drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun)"
href="https://bugs.freedesktop.org/show_bug.cgi?id=94605">bug 94605</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>So here's the problem with this bug report:
- It was created in March.
- The original bug reporter seems to be gone (no response to confirm/deny our
fixes).
- There's a lot of people with "me too" in the bug report.
- 111 comments.
- Since then, we fixed dozens of patches addressing problems that could cause
Skylake screen flickerings.
Usually I'd close the bug report if the original reporter confirmed his problem
was solved, then I'd ask everybody else to file new bug reports in case their
problems were not solved. Another process we have is that we close bugs if the
reporter stops responding us after some time.
Since I believe the problems of most people here should really be fixed in the
latest development tree, and since the original bug reporter stopped
responding, I'll just go ahead and mark this bug as fixed.
If you think the bug still happens to you, please make sure you test the latest
drm-tip tree (<a href="https://cgit.freedesktop.org/drm-tip">https://cgit.freedesktop.org/drm-tip</a> branch drm-tip), then open a
new bug report describing your specific problem. Make sure you boot with
drm.debug=0xe log_buf_len=1M, reproduce the problem, then attach the dmesg
output.
It's much easier for us to work on multiple bug reports about the same bug
instead of working on a single bug report with multiple actual bugs, so please
help us get everything organized so we can focus more on solving the bugs
instead of having spend time trying to extract information from a 100+ comment
bug report.
Thanks for your comprehension,
Paulo</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>