<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 - Kernel 4.5.0 crashes when docking Lenovo T450s (with external monitor connected)"
href="https://bugs.freedesktop.org/show_bug.cgi?id=94534">94534</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>Kernel 4.5.0 crashes when docking Lenovo T450s (with external monitor connected)
</td>
</tr>
<tr>
<th>Product</th>
<td>DRI
</td>
</tr>
<tr>
<th>Version</th>
<td>unspecified
</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>major
</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>cs_gon@yahoo.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>I have also reported this bug on bugzilla.kernel.org (
<a href="https://bugzilla.kernel.org/show_bug.cgi?id=114601">https://bugzilla.kernel.org/show_bug.cgi?id=114601</a> ), not sure where the best
place to report this is.
When docking the T450s into the docking station (Lenovo Pro Dock) with an
external monitor connected, the kernel frequently crashes.
I have enabled kernel crash dumps and drm.debug=0x1e, and at least got the
dmesg output. But I currently don't have the debugging symbols (the kernel is
from the Ubuntu mainline PPA), so cannot provide a full backtrace at the
moment.
Please let me know if this is needed. And is compiling with CONFIG_DEBUG_INFO=y
enough, or are additional steps needed?
I also tested the drm-intel-nightly kernel
(linux-image-4.5.0-994-generic_4.5.0-994.201603132257_amd64.deb from the Ubuntu
kernel PPA), which causes the same crash (apart from the addresses the exact
same stack trace).</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the QA Contact for the bug.</li>
<li>You are the assignee for the bug.</li>
<li>You are on the CC list for the bug.</li>
</ul>
</body>
</html>