<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body><span class="vcard"><a class="email" href="mailto:ville.syrjala@linux.intel.com" title="Ville Syrjala <ville.syrjala@linux.intel.com>"> <span class="fn">Ville Syrjala</span></a>
</span> changed
<a class="bz_bug_link
bz_status_NEEDINFO "
title="NEEDINFO - [BSW] External HDMI monitor suddenly shows solid color when playing Youtube video at 1080p [fifo underrun]"
href="https://bugs.freedesktop.org/show_bug.cgi?id=97965">bug 97965</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>NEEDINFO
</td>
</tr></table>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEEDINFO "
title="NEEDINFO - [BSW] External HDMI monitor suddenly shows solid color when playing Youtube video at 1080p [fifo underrun]"
href="https://bugs.freedesktop.org/show_bug.cgi?id=97965#c17">Comment # 17</a>
on <a class="bz_bug_link
bz_status_NEEDINFO "
title="NEEDINFO - [BSW] External HDMI monitor suddenly shows solid color when playing Youtube video at 1080p [fifo underrun]"
href="https://bugs.freedesktop.org/show_bug.cgi?id=97965">bug 97965</a>
from <span class="vcard"><a class="email" href="mailto:ville.syrjala@linux.intel.com" title="Ville Syrjala <ville.syrjala@linux.intel.com>"> <span class="fn">Ville Syrjala</span></a>
</span></b>
<pre>Hmm. Even though the cursor wasn't probably a factor, let's try and make sure
by setting a tight watermark for it even when it's disabled:
diff --git a/drivers/gpu/drm/i915/intel_pm.c b/drivers/gpu/drm/i915/intel_pm.c
index 7f1748a1e614..92611d6aaea3 100644
--- a/drivers/gpu/drm/i915/intel_pm.c
+++ b/drivers/gpu/drm/i915/intel_pm.c
@@ -965,6 +965,9 @@ static uint16_t vlv_compute_wm_level(struct intel_plane
*plane,
if (dev_priv->wm.pri_latency[level] == 0)
return USHRT_MAX;
+ if (plane->base.type == DRM_PLANE_TYPE_CURSOR)
+ return 63;
+
if (!state->base.visible)
return 0;
Another interesting thing we could check is whether the problem happens when
the primary display is using pipe B as opposed to pipe A. The hardware has some
warts where the pipes have some invalid linkages between them, so by using
another pipe for the primary display we might be able to avoid some of them.
So something like 'xrandr --output eDP1 --crtc 1' should do it.</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 on the CC list for the bug.</li>
<li>You are the QA Contact for the bug.</li>
</ul>
</body>
</html>