<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 - 4k eDP display blanks on intel-drm-nightly"
href="https://bugs.freedesktop.org/show_bug.cgi?id=93772">93772</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>4k eDP display blanks on intel-drm-nightly
</td>
</tr>
<tr>
<th>Product</th>
<td>DRI
</td>
</tr>
<tr>
<th>Version</th>
<td>DRI git
</td>
</tr>
<tr>
<th>Hardware</th>
<td>Other
</td>
</tr>
<tr>
<th>OS</th>
<td>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>sami.liedes@vincit.com
</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=121132" name="attach_121132" title="dmesg">attachment 121132</a> <a href="attachment.cgi?id=121132&action=edit" title="dmesg">[details]</a></span>
dmesg
Possibly related: <a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED FIXED - [BDW Regression]dmesg error "<3>[ 1.954836] [drm:gen8_irq_handler] *ERROR* The master control interrupt lied (SDE)!" after boot"
href="show_bug.cgi?id=80896">Bug 80896</a>, <a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED FIXED - [BDW][drm:gen8_irq_handler [i915]] *ERROR* The master control interrupt lied (SDE)!"
href="show_bug.cgi?id=92084">Bug 92084</a>
On a Dell Latitude E7450, using a drm-intel-nightly kernel from today, an
external 4k display shows picture on display manager login screen, but quickly
blanks after typing credentials and starting KDE.
Reproduction is easy: This practically always happens within 10 seconds after
trying to log in.
The mbim-proxy soft lockup BUG in the dmesg is probably not related; I'm only
seeing that on drm-intel-nightly, not on mainline 4.4 or drm-intel-next.
The same outward symptoms are present on ubuntu's 4.2 kernel, 4.4,
drm-intel-next and drm-intel-nightly.
dmesg with drm.debug=0xe and xrandr --verbose output from drm-intel-nightly
boot attached.
*Sometimes* changing the external display's resolution to 1920x1080 helps wake
the display up.</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>