<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 - [i915, Surface Pro 4] Regression: No display port output in kernel 4.8"
href="https://bugs.freedesktop.org/show_bug.cgi?id=97991">97991</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>[i915, Surface Pro 4] Regression: No display port output in kernel 4.8
</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>critical
</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>mikael@djurfeldt.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=126907" name="attach_126907" title="dmesg output when booting the drm-nightly kernel">attachment 126907</a> <a href="attachment.cgi?id=126907&action=edit" title="dmesg output when booting the drm-nightly kernel">[details]</a></span>
dmesg output when booting the drm-nightly kernel
I have been able to use both builtin screen and an external monitor on my
Surface Pro 4 up until and including kernel 4.7. However 4.8-rc8 as well as
drm-nightly from Thursday evening (Sept 29) does not at all present the
external monitor when I do xrandr and it is black.
x86_64
4.8.0-rc8-mssp4+
Debian Stretch
Surface Pro 4
eDP-1 works but DP-1 is not visible (as it is for 4.7)
Attaching dmesg.</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 assignee for the bug.</li>
<li>You are the QA Contact for the bug.</li>
</ul>
</body>
</html>