<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 - [HSW MST] Warning...process_single_tx_qlock"
href="https://bugs.freedesktop.org/show_bug.cgi?id=87100">87100</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>[HSW MST] Warning...process_single_tx_qlock
</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>consume.noise@gmail.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=110565" name="attach_110565" title="dmesg drm-intel-nightly 3.18.0-00343-gfc7bddc">attachment 110565</a> <a href="attachment.cgi?id=110565&action=edit" title="dmesg drm-intel-nightly 3.18.0-00343-gfc7bddc">[details]</a></span>
dmesg drm-intel-nightly 3.18.0-00343-gfc7bddc
(The same setup as in <a class="bz_bug_link
bz_status_NEW "
title="NEW - [HSW MST] Warning...drm_dp_mst_get_validated_mstb_ref_locked, possible circular locking dependency detected"
href="show_bug.cgi?id=87099">bug #87099</a>, but the monitor at the VGA port was
unplugged, leading to a different backtrace. Opening a different bug, because
closing one is more easy then untangling two.)
Hardware:
- Lenovo ThinkPad T440s + ThinkPad Pro Dock 40A1
- 1. monitor (Dell U2410 1920x1200) at DP of docking station
- 2. monitor (Dell U2413 1920x1200) at VGA of docking station
If I boot this setup with both monitor attached to the console and remove the
monitor (unplug the connector) at the VGA, then I can reproduce the attached
backtrace (not?) always.
This happens with v3.17.6, v3.18 and current drm-intel-nightly (fc7bddc
drm-intel-nightly: 2014y-12m-08d-12h-45m-52s UTC integration manifest). The
dmesg log has been captured with drm-intel-nightly.
[ 32.989502] [drm:drm_dp_mst_wait_tx_reply] timedout msg send
ffff88030a3e8000 2 1
[ 32.997033] [drm:drm_dp_dpcd_access] too many retries, giving up
[ 33.004354] [drm:drm_dp_dpcd_access] too many retries, giving up
[ 33.011308] [drm:drm_dp_dpcd_access] too many retries, giving up
[ 33.018235] [drm:drm_dp_dpcd_access] too many retries, giving up
[ 33.025125] [drm:drm_dp_dpcd_access] too many retries, giving up
[ 33.032064] [drm:drm_dp_dpcd_access] too many retries, giving up
[ 33.033205] [drm:drm_dp_send_sideband_msg] failed to dpcd write 13 -5
[ 33.034044] ------------[ cut here ]------------
[ 33.034767] WARNING: CPU: 0 PID: 128 at
drivers/gpu/drm/drm_dp_mst_topology.c:1259 process_single_tx_qlock+0x5ee/0x650
[drm_kms_helper]()
...
[ 33.085617] ---[ end trace 2bb04b47e83116a7 ]---
[ 33.086539] [drm:process_single_tx_qlock] sideband msg failed to send
[ 33.087466] [drm:process_single_down_tx_qlock] failed to send msg in q -5
...</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 on the CC list for the bug.</li>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>