[Bug 92308] New: Lenovo X1 OneLink Pro Dock + Lenovo 4k monitor fail

[bugzilla-daemon at freedesktop.org]

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

            Bug ID: 92308
           Summary: Lenovo X1 OneLink Pro Dock + Lenovo 4k monitor fail
           Product: DRI
           Version: DRI git
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: DRM/Intel
          Assignee: intel-gfx-bugs at lists.freedesktop.org
          Reporter: benh at kernel.crashing.org
        QA Contact: intel-gfx-bugs at lists.freedesktop.org
                CC: intel-gfx-bugs at lists.freedesktop.org

Machine: Lenovo X1 Gen 3 with OneLink Pro dock
Monitor: Lenovo 4k monitor "Pro 2480mD"

If I connect the monitor using the X1's built-in mini-DP with a DP1.2
compatible mini-DP to DP cable, things work fine (more/less, the monitor
sometimes fails to come back from idle blanking but I'll file that as a
separate issue).

If I connect the monitor to the dock using the DP-DP cable coming with the
monitor, the monitor doesn't sync. It displays an error about no sync. dmesg
fills up with error messages from the driver which I will attach.

$ uname -a
Linux pasglop 4.3.0-rc4+ #1 SMP Tue Oct 6 11:46:15 AEDT 2015 x86_64 x86_64
x86_64 GNU/Linux

git head is 1ff47c81ae9fcf16e40292478b7dd8c1d68130c1 from the drm-intel git
tree
using the nightly branch.

If I use xrandr to use a lower resolution (1080p for example), I had it working
once or twice. I tried to use 4k at 30Hz but that resulted in a driver crash
taking out  the internal panel as well (reproduceable) with a previous 4.3-rc
kernel.

I will update this with more tests of the above using this latest kernel.

-- 
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/20151006/c522018e/attachment-0001.html>