[amdgpu] Display does not come on after suspend (amdgpu crashes)

[Nick]

After coming out of suspend the display is not receiving any data and stays in power saving mode. Only power cycling the system brings it back. Unsure whether this is related to amdgpu or something else.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.6
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sat Aug 8 12:51:28 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] [1002:731f] (rev c4) (prog-if 00 [VGA controller])
   Subsystem: Gigabyte Technology Co., Ltd Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] [1458:2314]
InstallationDate: Installed on 2020-01-08 (212 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200106)
MachineType: System manufacturer System Product Name
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=d1ce6274-5a98-4eab-93b4-393469cec0d9 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/05/2020
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2603
dmi.board.asset.tag: Default string
dmi.board.name: TUF GAMING X570-PLUS (WI-FI)
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2603:bd08/05/2020:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFGAMINGX570-PLUS(WI-FI):rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
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 N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2
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)]

After the problem happens again and you power cycle, please run:

  journalctl -b-1 > prevboot.txt

and attach the resulting text file here.

[Nick (biangbiangmian)]

Hello, here is the log as requested

[Daniel van Vugt (vanvugt)]

Perfect, thanks. It appears to be the 'amdgpu' driver crashing in the kernel.

[Daniel van Vugt (vanvugt)]

Please test this kernel:

https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.8/amd64/

[Nick (biangbiangmian)]

Tested, however the issue persists

[Daniel van Vugt (vanvugt)]

Can you please try again on kernel 5.8 and gather another log?

The problem with the log in comment #6 is that it ends too early -- when the system suspends. And doesn't show anything about trying to resume from suspend. This is a common issue with these kinds of bugs. To make it more likely that a complete log is written please hit these keys after resuming from suspend (when the display isn't coming on):

  Alt + SysRq + S

and then reboot. Or you can do it all in one:

  (Holding Alt+SysRq) R,E,I,S,U,B

https://en.wikipedia.org/wiki/Magic_SysRq_key

[Nick (biangbiangmian)]

Thank you, attached log 1/2

[Nick (biangbiangmian)]

1/2

[Nick (biangbiangmian)]

2/2

[Daniel van Vugt (vanvugt)]

Perfect, thanks. That shows the 'amdgpu' kernel driver is crashing in a couple of ways.

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

This change was made by a bot.

[Kai-Heng Feng (kaihengfeng)]

Does kernel parameter "pci=noats" help?

[Nick (biangbiangmian)]

Thanks, but no, the screen still did not come on. Log file attached.

[Nick (biangbiangmian)]

That log is after booting with GRUB_CMDLINE_LINUX_DEFAULT="quiet splash pci=noats"

[Kai-Heng Feng (kaihengfeng)]

Please test latest mainline kernel:
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.9-rc3/amd64/

And file an upstream bug if issue persists:
https://gitlab.freedesktop.org/drm/amd/issues

[Nick (biangbiangmian)]

After installing today's updates the issue is no longer occurring.

[Nick (biangbiangmian)]

This issue is back. I am on 5.4.0-66-lowlatency #74-Ubuntu SMP PREEMPT Wed Jan 27 23:41:42 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux.

After the display goes off after the automatic timeout it will not come back on.