[Bug 87100] New: [HSW MST] Warning...process_single_tx_qlock

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Mon Dec 8 06:12:55 PST 2014


https://bugs.freedesktop.org/show_bug.cgi?id=87100

            Bug ID: 87100
           Summary: [HSW MST] Warning...process_single_tx_qlock
           Product: DRI
           Version: DRI git
          Hardware: Other
                OS: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: DRM/Intel
          Assignee: intel-gfx-bugs at lists.freedesktop.org
          Reporter: consume.noise at gmail.com
        QA Contact: intel-gfx-bugs at lists.freedesktop.org
                CC: intel-gfx-bugs at lists.freedesktop.org

Created attachment 110565
  --> https://bugs.freedesktop.org/attachment.cgi?id=110565&action=edit
dmesg drm-intel-nightly 3.18.0-00343-gfc7bddc

(The same setup as in bug #87099, 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
...

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are on the CC list for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20141208/16e87d13/attachment.html>


More information about the intel-gfx-bugs mailing list