after upgrade to 5.4.0-66 monitor remains black after off/on cycle

[Günter Woigk]

i updated today to linux kernel 5.4.0-66-generic.
since then the monitor (HDMI) remains black when switched off and on again.
this can be corrected once, if a virtual text console hasn't been used so far by switching to a virtual text console and then back to the desktop.

Ubuntu 5.4.0-66.74-generic 5.4.86 (Linux Mint 20, Cinnamon 4.6.7)
lspci-vnvn.log attached

Asrock DeskMini A300
AMD Ryzen 5 2400G with Radeon Vega Graphics × 4
Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series]
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC2: kio 1177 F.... pulseaudio
 /dev/snd/controlC1: kio 1177 F.... pulseaudio
 /dev/snd/controlC0: kio 1177 F.... pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: X-Cinnamon
DistroRelease: Linux Mint 20
InstallationDate: Installed on 2020-07-24 (216 days ago)
InstallationMedia: Linux Mint 20 "Ulyana" - Release amd64 20200624
IwConfig:
 lo no wireless extensions.

 enp3s0 no wireless extensions.
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
Package: linux (not installed)
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-66-generic root=UUID=c96f03d4-1951-4c06-8d5d-61bd5b22b308 ro quiet splash
ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86
RelatedPackageVersions:
 linux-restricted-modules-5.4.0-66-generic N/A
 linux-backports-modules-5.4.0-66-generic N/A
 linux-firmware 1.187.9
RfKill:

Tags: ulyana
Uname: Linux 5.4.0-66-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo www-data
_MarkForUpload: True
dmi.bios.date: 05/15/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P3.50
dmi.board.name: A300M-STX
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP3.50:bd05/15/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnA300M-STX:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: To Be Filled By O.E.M.
dmi.product.sku: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.

[Matias N. Goldberg (dark-sylinc)]

As a workaround you can try booting with "amdgpu.dc=0"

Although I don't know if Vega supports disabling DC.
With DC disabled, the GPU cannot know if your monitor has been turned off.

Another possible solution is to use an SSH session to try to restore your monitor, typing:

DISPLAY=:0.0 xrandr --auto

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

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 1916919

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.

[Günter Woigk (megatokio)]

apport information

[Günter Woigk (megatokio)]

apport information

[Günter Woigk (megatokio)]

apport information

[Günter Woigk (megatokio)]

apport information

[Günter Woigk (megatokio)]

apport information

[Günter Woigk (megatokio)]

apport information

[Günter Woigk (megatokio)]

apport information

[Günter Woigk (megatokio)]

apport information

[Günter Woigk (megatokio)]

apport information

[Günter Woigk (megatokio)]

apport information

[Günter Woigk (megatokio)]

apport information

[Günter Woigk (megatokio)]

apport information

[Günter Woigk (megatokio)]

apport information

[Günter Woigk (megatokio)]

apport information

[Günter Woigk (megatokio)]

apport information

[Günter Woigk (megatokio)]

apport information

[Günter Woigk (megatokio)]

apport information

[Ben Fenner (benfenner)]

I can confirm I have the same issue. I've reverted the kernel back to 5.4.0-65 to temporarily solve the issue.

I have all of the logs and details posted here: https://forums.linuxmint.com/viewtopic.php?f=59&t=343546&p=1977800#p1977800

The most important being:

Feb 25 15:46:06 meritwork-linux kernel: [drm:dce112_get_pix_clk_dividers [amdgpu]] *ERROR* dce112_get_pix_clk_dividers: Invalid parameters!!
Feb 25 15:46:06 meritwork-linux kernel: [drm:dm_restore_drm_connector_state [amdgpu]] *ERROR* Restoring old state failed with -22

[Ben Fenner (benfenner)]

I'm back to say that kernel 5.4.0-66-generic works for me again after applying the grub default `amdgpu.dc=0` work-around mentioned above.

This is for a Radeon RX 580 if that helps.

[Christian Pernegger (fallenguru)]

I'm also affected, this is with a Radeon VII.

The VT switching workaround can take many tries to work.
This morning, when it didn't after ~20, I found this bug and tried the "DISPLAY=:0.0 xrandr --auto" tip via ssh. That in itself did not revive the display, but afterwards switching VTs suddenly helped. No idea if it's a coincidence.

Since this is a work machine that I need to stay up and usable, I'm reverting to the previous kernel for now.