[amdgpu] Screen freeze when monitor turned off and on

[cbrok]

I have two monitors on a Radeon R9 380X, one is connected to HDMI, the other is connected to DVI.
When I turn off the left monitor, nothing happens.
Only when you turn it on again does the entire picture move to the right monitor and Ubuntu does not react to keyboard or mouse input.
The problem only occurs once I've logged in. Even if I've locked the screen again.

Hard reboot is required.

======================================================

Ubuntu:
Description: Ubuntu 20.04.1 LTS
Release: 20.04

xorg:
  Installiert: 1:7.7+19ubuntu14
  Installationskandidat: 1:7.7+19ubuntu14
  Versionstabelle:
 *** 1:7.7+19ubuntu14 500
        500 http://de.archive.ubuntu.com/ubuntu focal/main amd64 Packages
        100 /var/lib/dpkg/status

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
Uname: Linux 5.4.0-54-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.12
Architecture: amd64
BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Tue Nov 24 09:44:57 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GpuHangFrequency: Very infrequently
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Tonga XT / Amethyst XT [Radeon R9 380X / R9 M295X] [1002:6938] (rev f1) (prog-if 00 [VGA controller])
   Subsystem: PC Partner Limited / Sapphire Technology Radeon R9 380X Nitro 4G D5 [174b:e308]
InstallationDate: Installed on 2019-09-15 (435 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
MachineType: MSI MS-7978
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-54-generic root=UUID=876f1728-1e76-4498-a415-504e1078f473 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/24/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: C.70
dmi.board.asset.tag: Default string
dmi.board.name: H170 GAMING M3 (MS-7978)
dmi.board.vendor: MSI
dmi.board.version: 2.0
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: MSI
dmi.chassis.version: 2.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrC.70:bd07/24/2016:svnMSI:pnMS-7978:pvr2.0:rvnMSI:rnH170GAMINGM3(MS-7978):rvr2.0:cvnMSI:ct3:cvr2.0:
dmi.product.family: Default string
dmi.product.name: MS-7978
dmi.product.sku: Default string
dmi.product.version: 2.0
dmi.sys.vendor: MSI
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

[Daniel van Vugt (vanvugt)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps:

1. Look in /var/crash for crash files and if found run:
    ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.

2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us.

3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1.

Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself.

[Daniel van Vugt (vanvugt)]

If the above steps fail then please:

1. Reproduce the freeze again.

2. Wait 10 seconds.

3. Reboot.

4. Open a terminal and run:

   journalctl -b-1 > prevboot.txt

5. Attach the resulting text file here.

[cbrok (cbrok)]

Step 2 of your first message succeeded.
The last crash in the last 10 days is from firefox, but I'm very sure it has nothing to do with the bug. Here it is: https://errors.ubuntu.com/oops/5c5f16b6-2daa-11eb-b88b-fa163e102db1

Continuing with your second message.

[cbrok (cbrok)]

Added the file. Last messages came from gdm3, should I collect more data from that package?

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This change was made by a bot.