<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body><table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Bug ID</th>
<td><a class="bz_bug_link
bz_status_NEW "
title="NEW - Screen blanking (DP link reset?) when working in terminals"
href="https://bugs.freedesktop.org/show_bug.cgi?id=97264">97264</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>Screen blanking (DP link reset?) when working in terminals
</td>
</tr>
<tr>
<th>Product</th>
<td>DRI
</td>
</tr>
<tr>
<th>Version</th>
<td>DRI git
</td>
</tr>
<tr>
<th>Hardware</th>
<td>x86-64 (AMD64)
</td>
</tr>
<tr>
<th>OS</th>
<td>Linux (All)
</td>
</tr>
<tr>
<th>Status</th>
<td>NEW
</td>
</tr>
<tr>
<th>Severity</th>
<td>normal
</td>
</tr>
<tr>
<th>Priority</th>
<td>medium
</td>
</tr>
<tr>
<th>Component</th>
<td>DRM/Intel
</td>
</tr>
<tr>
<th>Assignee</th>
<td>intel-gfx-bugs@lists.freedesktop.org
</td>
</tr>
<tr>
<th>Reporter</th>
<td>freedesktop-bugzilla@rivera.za.net
</td>
</tr>
<tr>
<th>QA Contact</th>
<td>intel-gfx-bugs@lists.freedesktop.org
</td>
</tr>
<tr>
<th>CC</th>
<td>intel-gfx-bugs@lists.freedesktop.org
</td>
</tr></table>
<p>
<div>
<pre>Created <span class=""><a href="attachment.cgi?id=125648" name="attach_125648" title="Full dmesg, including multiple monitor blanks">attachment 125648</a> <a href="attachment.cgi?id=125648&action=edit" title="Full dmesg, including multiple monitor blanks">[details]</a></span>
Full dmesg, including multiple monitor blanks
Reported in Debian too: <a href="https://bugs.debian.org/833478">https://bugs.debian.org/833478</a>
Hardware: Lenovo X250 (Intel Broadwell-U Integrated Graphics), with 2x Dell
U2713HM connected via docking station's Display Ports.
Software: Debian amd64, with Debian Linux kernel 4.6.0-1 and with
drm-intel-next-2016-08-08.
Since upgrading to the modesetting driver, the monitor I'm currently focussed
on often goes blank for a second, while I'm working. The others are unaffected.
I'm assuming that the Display Port connection is resetting, because if I have a
monitor menu up, when triggering the bug, it gets closed, as the screen blanks.
Nothing gets logged.
It seems to be usually caused by opening a terminal or pressing a key in a
terminal just after switching focus, but I can't explain any of that :)
It seems to happen less often if I turn one of the 3 monitors off. And I've
never seen it happen on the internal eDP panel, only on the DP Dell monitors.
Using the intel driver avoids the problem, but it seems to have picked up other
odd rendering bugs around the same time. Windows flicker between previous and
old contents.
With drm.debug=0x1e on drm-intel-next-2016-08-08 I see these events appear when
a monitor blanks:
[ 68.609827] [drm:drm_atomic_state_init] Allocated atomic state
ffff8804244c5000
[ 68.609843] [drm:drm_atomic_get_plane_state] Added [PLANE:29:cursor B]
ffff8804246b5180 state to ffff8804244c5000
[ 68.609848] [drm:drm_atomic_get_crtc_state] Added [CRTC:30:pipe B]
ffff880410ee9000 state to ffff8804244c5000
[ 68.609850] [drm:drm_atomic_set_crtc_for_plane] Link plane state
ffff8804246b5180 to [NOCRTC]
[ 68.609853] [drm:drm_atomic_set_fb_for_plane] Set [NOFB] for plane state
ffff8804246b5180
[ 68.609855] [drm:drm_atomic_check_only] checking ffff8804244c5000
[ 68.609862] [drm:intel_plane_atomic_calc_changes] [CRTC:30:pipe B] has
[PLANE:29:cursor B] with fb -1
[ 68.609865] [drm:intel_plane_atomic_calc_changes] [PLANE:29:cursor B]
visible 1 -> 0, off 1, on 0, ms 0
[ 68.609871] [drm:drm_atomic_commit] commiting ffff8804244c5000
[ 68.609904] [drm:drm_atomic_state_default_clear] Clearing atomic state
ffff8804244c5000
[ 68.609908] [drm:drm_atomic_state_free] Freeing atomic state
ffff8804244c5000</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>