Bug 202799
| Summary: | amd/dc: right monitor sometimes never comes back up on dual-display setup after locking session | ||
|---|---|---|---|
| Product: | Drivers | Reporter: | Clément Guérin (libcg) |
| Component: | Video(DRI - non Intel) | Assignee: | drivers_video-dri |
| Status: | RESOLVED OBSOLETE | ||
| Severity: | normal | CC: | harry.wentland, nicholas.kazlauskas |
| Priority: | P1 | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Kernel Version: | 5.0 | Subsystem: | |
| Regression: | No | Bisected commit-id: | |
| Attachments: |
xrandr --props output
dmesg output Xorg.1.log dmesg drm.debug=4 |
||
Please attach the corresponding Xorg log file and full output of dmesg, preferably captured after the problem occurred. Created attachment 281577 [details]
dmesg output
Created attachment 281587 [details]
Xorg.1.log
Logs after the bug was triggered.
Hi Michel, is there anything else you need to debug this? I have to defer to the DC guys in the CC list. It might be useful to have a dmesg log from after the problem occurred with drm.debug=4 set in your kernel boot parameters. Created attachment 281855 [details]
dmesg drm.debug=4
Here's the log as requested.
Do you need anything else? I'm still seeing this bug with linux 5.1. This is still a problem on Linux 5.2. I switched to wayland months ago and haven't hit that bug since. |
Created attachment 281547 [details] 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.