[Bug 202799] New: amd/dc: right monitor sometimes never comes back up on dual-display setup after locking session
https://bugzilla.kernel.org/show_bug.cgi?id=202799
Bug ID: 202799 Summary: amd/dc: right monitor sometimes never comes back up on dual-display setup after locking session Product: Drivers Version: 2.5 Kernel Version: 5.0 Hardware: All OS: Linux Tree: Mainline Status: NEW Severity: normal Priority: P1 Component: Video(DRI - non Intel) Assignee: drivers_video-dri@kernel-bugs.osdl.org Reporter: libcg@protonmail.com Regression: No
Created attachment 281547 --> https://bugzilla.kernel.org/attachment.cgi?id=281547&action=edit xrandr --props output
- linux 5.0 (4.20 also had the same issue) - xf86-video-amdgpu 18.1.0 - GNOME 3.30
Left screen is a Dell U2412M (1920x1200), right screen is a Dell P2715Q (4K monitor set at 2560x1440, primary). GPU is RX 580.
Steps to reproduce: - Lock session, screens turn off - After a while, press a key to turn the screens back on again - When the left screen lights up first, the system only displays an image on the left screen. The right screen lights up afterwards but goes back to sleep because it's getting no signal, although xrandr still recognizes it. I need to manually turn off the right screen and back on again to get it to reconfigure.
When using `amdgpu.dc=0`, this issue disappears.
https://bugzilla.kernel.org/show_bug.cgi?id=202799
Michel Dänzer (michel@daenzer.net) changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |harry.wentland@amd.com, | |nicholas.kazlauskas@amd.com
--- Comment #1 from Michel Dänzer (michel@daenzer.net) --- Please attach the corresponding Xorg log file and full output of dmesg, preferably captured after the problem occurred.
https://bugzilla.kernel.org/show_bug.cgi?id=202799
--- Comment #2 from Clément Guérin (libcg@protonmail.com) --- Created attachment 281577 --> https://bugzilla.kernel.org/attachment.cgi?id=281577&action=edit dmesg output
https://bugzilla.kernel.org/show_bug.cgi?id=202799
--- Comment #3 from Clément Guérin (libcg@protonmail.com) --- Created attachment 281587 --> https://bugzilla.kernel.org/attachment.cgi?id=281587&action=edit Xorg.1.log
Logs after the bug was triggered.
https://bugzilla.kernel.org/show_bug.cgi?id=202799
--- Comment #4 from Clément Guérin (libcg@protonmail.com) --- Hi Michel, is there anything else you need to debug this?
https://bugzilla.kernel.org/show_bug.cgi?id=202799
--- Comment #5 from Michel Dänzer (michel@daenzer.net) --- I have to defer to the DC guys in the CC list.
https://bugzilla.kernel.org/show_bug.cgi?id=202799
--- Comment #6 from Nicholas Kazlauskas (nicholas.kazlauskas@amd.com) --- It might be useful to have a dmesg log from after the problem occurred with drm.debug=4 set in your kernel boot parameters.
https://bugzilla.kernel.org/show_bug.cgi?id=202799
--- Comment #7 from Clément Guérin (libcg@protonmail.com) --- Created attachment 281855 --> https://bugzilla.kernel.org/attachment.cgi?id=281855&action=edit dmesg drm.debug=4
Here's the log as requested.
https://bugzilla.kernel.org/show_bug.cgi?id=202799
--- Comment #8 from Clément Guérin (libcg@protonmail.com) --- Do you need anything else?
https://bugzilla.kernel.org/show_bug.cgi?id=202799
--- Comment #9 from Clément Guérin (libcg@protonmail.com) --- I'm still seeing this bug with linux 5.1.
https://bugzilla.kernel.org/show_bug.cgi?id=202799
--- Comment #10 from Clément Guérin (libcg@protonmail.com) --- This is still a problem on Linux 5.2.
https://bugzilla.kernel.org/show_bug.cgi?id=202799
Clément Guérin (libcg@protonmail.com) changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |OBSOLETE
--- Comment #11 from Clément Guérin (libcg@protonmail.com) --- I switched to wayland months ago and haven't hit that bug since.
dri-devel@lists.freedesktop.org
-
bugzilla-daemon＠bugzilla.kernel.org