[Bug 112400] MST configuration breaks after resume with monitor switched to different source

[bugzilla-daemon at freedesktop.org]

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

Lakshmi <lakshminarayana.vudum at intel.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |NEEDINFO
      i915 features|                            |display/DP MST
         Whiteboard|                            |Triaged

--- Comment #6 from Lakshmi <lakshminarayana.vudum at intel.com> ---
(In reply to Simon Richter from comment #0)
> I use a MST based dual monitor setup where the first monitor in the chain
> has multiple inputs and allows me to switch between input sources.
> 
> When switching away from my Linux box, there is a good chance that
> afterwards the configuration will be invalid, and after switching back, no
> picture will be shown.
> 
> I usually hibernate the machines at night, and resuming with the monitor
> switched to the other source always triggers this condition (while switching
> away during normal operation only has a high probability).
> 
> Hibernating again and making sure to boot up with the monitor set to the
> right source does not fix the problem -- the firmware correctly shows the
> logo on both monitors, a text mode screen with a blinking cursor is shown
> during resume, then the invalid configuration is reloaded.
> 
> Attached kernel log is with a Debian standard kernel,
> 
> Linux debian 4.19.0-6-amd64 #1 SMP Debian 4.19.67-2+deb10u1 (2019-09-20)
> x86_64 GNU/Linux
> 
>  - Normal boot
>  - X start
>  - hibernate
>  - resume
>  - X shutdown
>  - X restart

Which platform is this? I couldn't find it from the kernel log.

-- 
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/20191127/2b802605/attachment.html>