amdgpu.dc dual monitor issues when trying to sleep / power off the monitors

Bug #1790861 reported by Giacomo Graziosi
24
This bug affects 4 people
Affects Status Importance Assigned to Milestone
GNOME Settings Daemon
Unknown
Unknown
Linux
Unknown
Unknown
linux (Ubuntu)
Medium
Unassigned

Bug Description

I have a problem with my dual monitor setup on an AMD RX 580: when I lock the screen and Gnome try to power off both monitors the following happens:
1) the second monitor goes to sleep before the first one, this is normal and expected because the first monitor has a longer time to sleep
2) after some seconds the second monitor turn on back again and prevents the first one to sleep at all
3) gnome detects inactivity on the lock screen for some time and try to power off the monitors again
4) step 1 all over again in an infinite loop

When I login back from the lock screen the windows inside my Gnome session can sometimes be rearranged from one screen to the other.

After discovering this behavior I tried to power off the monitors manually with `xset dpms force off` and I can confirm that the same happens: the monitors wont really power off because the second one turns back on and prevents the first one to sleep.

My guess was that somehow when the second monitor was turning off it delivered some kind of "monitors changed, you should reset" message to the GPU which in order did some kind of "reset everything and power on the monitors back again" action.

Searching for a fix to this problem I tried to upgrade my amdgpu mesa drivers using the oibaf/graphics-drivers ppa and after this I tried to upgrade my whole distribution too, moving from bionic to cosmic.

Nothing worked.

In the end I discovered the existence of amdgpu.dc and tried to disable it with `GRUB_CMDLINE_LINUX_DEFAULT="amdgpu.dc=0"`, this did the trick but it is still a workaround.

I'm not sure this is the right place to report this kind of issues but as the issue is somehow critical (the first I entered the power on/off loop I didn't notice it and my monitor cycled power for two hours) I hope this will help other people.
---
ProblemType: Bug
AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.17.0-9-generic.
ApportVersion: 2.20.10-0ubuntu9
Architecture: amd64
Card0.Amixer.info:
 Card hw:0 'PCH'/'HDA Intel PCH at 0xf7f10000 irq 30'
   Mixer name : 'Realtek ALC892'
   Components : 'HDA:10ec0892,104385b0,00100302'
   Controls : 50
   Simple ctrls : 22
Card1.Amixer.info:
 Card hw:1 'HDMI'/'HDA ATI HDMI at 0xf7e60000 irq 31'
   Mixer name : 'ATI R6xx HDMI'
   Components : 'HDA:1002aa01,00aa0100,00100700'
   Controls : 42
   Simple ctrls : 6
CurrentDesktop: GNOME
DistroRelease: Ubuntu 18.10
HibernationDevice: RESUME=UUID=7cd1c323-140b-4412-a67a-c46d90a91ff2
InstallationDate: Installed on 2018-09-01 (3 days ago)
InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
MachineType: ASUS All Series
Package: linux (not installed)
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.17.0-9-generic root=UUID=edb6f869-3d1b-4726-bbf1-44b736abfe2b ro amdgpu.dc=0
ProcVersionSignature: Ubuntu 4.17.0-9.10-generic 4.17.17
RelatedPackageVersions:
 linux-restricted-modules-4.17.0-9-generic N/A
 linux-backports-modules-4.17.0-9-generic N/A
 linux-firmware 1.174
RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
Tags: cosmic
Uname: Linux 4.17.0-9-generic x86_64
UpgradeStatus: Upgraded to cosmic on 2018-09-04 (0 days ago)
UserGroups: adm audio cdrom dip lpadmin lxd plugdev sambashare sudo vboxusers
_MarkForUpload: True
dmi.bios.date: 08/15/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2103
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: Z87-C
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2103:bd08/15/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ87-C:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.family: ASUS MB
dmi.product.name: All Series
dmi.product.version: System Version
dmi.sys.vendor: ASUS

Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1790861

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Giacomo Graziosi (g.graziosi) wrote : AlsaDevices.txt

apport information

tags: added: apport-collected cosmic
description: updated
Revision history for this message
Giacomo Graziosi (g.graziosi) wrote : AplayDevices.txt

apport information

Revision history for this message
Giacomo Graziosi (g.graziosi) wrote : ArecordDevices.txt

apport information

Revision history for this message
Giacomo Graziosi (g.graziosi) wrote : AudioDevicesInUse.txt

apport information

Revision history for this message
Giacomo Graziosi (g.graziosi) wrote : CRDA.txt

apport information

Revision history for this message
Giacomo Graziosi (g.graziosi) wrote : Card0.Amixer.values.txt

apport information

Revision history for this message
Giacomo Graziosi (g.graziosi) wrote : Card0.Codecs.codec.0.txt

apport information

Revision history for this message
Giacomo Graziosi (g.graziosi) wrote : Card1.Amixer.values.txt

apport information

Revision history for this message
Giacomo Graziosi (g.graziosi) wrote : Card1.Codecs.codec.0.txt

apport information

Revision history for this message
Giacomo Graziosi (g.graziosi) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Giacomo Graziosi (g.graziosi) wrote : Lspci.txt

apport information

Revision history for this message
Giacomo Graziosi (g.graziosi) wrote : Lsusb.txt

apport information

Revision history for this message
Giacomo Graziosi (g.graziosi) wrote : PciMultimedia.txt

apport information

Revision history for this message
Giacomo Graziosi (g.graziosi) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Giacomo Graziosi (g.graziosi) wrote : ProcCpuinfoMinimal.txt

apport information

Revision history for this message
Giacomo Graziosi (g.graziosi) wrote : ProcEnviron.txt

apport information

Revision history for this message
Giacomo Graziosi (g.graziosi) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Giacomo Graziosi (g.graziosi) wrote : ProcModules.txt

apport information

Revision history for this message
Giacomo Graziosi (g.graziosi) wrote : PulseList.txt

apport information

Revision history for this message
Giacomo Graziosi (g.graziosi) wrote : UdevDb.txt

apport information

Revision history for this message
Giacomo Graziosi (g.graziosi) wrote : WifiSyslog.txt

apport information

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.19 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19-rc2

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
Revision history for this message
Giacomo Graziosi (g.graziosi) wrote :

Did the test on 4.19.0-041900rc2-generic, issue is still there.

tags: added: bug-exists-upstream
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
mikk351 (mikk351) wrote :

Same problem here with kernel 4.19 and 4.18, rx580 and vega 8 (ryzen 2200G).

Revision history for this message
TooManyErrors (toomanyerrors) wrote :

I'm using an RX 480 and also have the same problem on kernels 4.18 and 4.20 (tested using 4.20.0-042000 from https://kernel.ubuntu.com/~kernel-ppa/mainline/v4.20/). Adding "amdgpu.dc=0" to GRUB fixes the problem in both cases.

Revision history for this message
TooManyErrors (toomanyerrors) wrote :

I've since tested Linux v5.0-rc1 (https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.0-rc1/) and the issue still hasn't been fixed.

Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

Please file an upstream bug at https://bugs.freedesktop.org/
Product: DRI
Component: DRM/amdgpu

Revision history for this message
TooManyErrors (toomanyerrors) wrote :
Brad Figg (brad-figg)
tags: added: cscc
Revision history for this message
oh (jigglywiggly) wrote :

I am having the same issue on my rx570, I am on kernel 5.1.21

Revision history for this message
oh (jigglywiggly) wrote :

I am using one displayport 4k monitor, and one hdmi 1080p monitor. They keep waking each other up. When I used an adapter to make the 1080p monitor connect via a displayport > hdmi adapter, they both just output black when trying to sleep and cannot be woken up. They are still outputting black, they did not go to sleep.

Revision history for this message
oh (jigglywiggly) wrote :

With amdgpu.dc=0 I get random mouse lag after moving my mouse quickly. The cursor will just stop moving. I turned amdgpu.dc=1 and it went away.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.