[Bug 107967] New: [SKL] Connector states are not updated after resume

[bugzilla-daemon at freedesktop.org]

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

            Bug ID: 107967
           Summary: [SKL] Connector states are not updated after resume
           Product: DRI
           Version: unspecified
          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: harn-solo at gmx.de
        QA Contact: intel-gfx-bugs at lists.freedesktop.org
                CC: intel-gfx-bugs at lists.freedesktop.org
     i915 platform: SKL
     i915 features: power/suspend-resume

Whenever I switch my work environment with my laptop between my office setup
and my home setup within a suspend/resume-cycle, the connector output states
are not updated.

The laptop involved, is a Lenovo Thinkpad T460p. On both sites a Lenovo
ThinkPad Ultra Dock (type 40A2) is used.

Home monitor setup:
Eizo S2431W 24" in landscape mode, connected to DP3-1

Office monitor setup:
Eizo S2433W 24" in portrait mode, left, connected to DP3-1
Eizo S2431W 24" in landscape mode, right, connected to DP3-2

For details see the attached xrandr outputs.

Lately, at around kernel 4.16, when suspending the laptop in the office setup,
carrying to my home and resuming it there, the connector outputs are not
updated at all.

In this scenario the system shows a 90° rotated lock screen from KDE on the
only connected screen. Presumably the left one of from the office setup. The
xrandr tool still shows that DP3-1 and DP3-2 are connected.

The same happens vice versa, when suspend in the home setup and resuming it in
the office setup, it only displays one screen (on the one that is physically
rotated), probably because the are both connected to DP3-1.

I have attached two kernel outputs showing both suspend/resume cycles, one made
with kernel 4.18.8 and the other one already with drm-tip.

The only known workaround to that problem is to let the laptop resume in an
un-docked state before docking it again.

-- 
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: <https://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20180918/a381a33e/attachment.html>