amdgpu_device_ip_resume_phase2 errors

Bug #1850744 reported by Kai Groner
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

I am using a Radeon RX 580. This setup was stable with Ubuntu 19.04. Since upgrading to 19.10 it's failed to resume from S3 sleep 3 times out of 15. The console will be unresponsive, but the machine is still accessible over the network.

Here are some of the errors from dmesg (the second block happened on two boots). Complete kernel logs from all three boots are attached.

--
amdgpu 0000:07:00.0: [drm:amdgpu_ring_test_helper [amdgpu]] *ERROR* ring sdma0 test failed (-110)
[drm:amdgpu_device_ip_resume_phase2 [amdgpu]] *ERROR* resume of IP block <sdma_v3_0> failed -110
[drm:amdgpu_device_resume [amdgpu]] *ERROR* amdgpu_device_ip_resume failed (-110).
PM: dpm_run_callback(): pci_pm_resume+0x0/0xa0 returns -110
PM: Device 0000:07:00.0 failed to resume async: error -110
--
amdgpu 0000:07:00.0: [drm:amdgpu_ring_test_helper [amdgpu]] *ERROR* ring gfx test failed (-110)
[drm:amdgpu_device_ip_resume_phase2 [amdgpu]] *ERROR* resume of IP block <gfx_v8_0> failed -110
[drm:amdgpu_device_resume [amdgpu]] *ERROR* amdgpu_device_ip_resume failed (-110).
PM: dpm_run_callback(): pci_pm_resume+0x0/0xa0 returns -110
PM: Device 0000:07:00.0 failed to resume async: error -110

--
The kernel is based on the Ubuntu-5.3.0-20.21 tag of the eoan kernel repo with the below listed patches applied.
 [v2,1/2] x86/amd_nb: Add PCI device IDs for family 17h, model 70h
 [v2,2/2] hwmon/k10temp: Add support for AMD family 17h, model 70h CPUs https://patchwork.kernel.org/patch/11053205/

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: linux-image-5.3.0-19-generic (not installed)
ProcVersionSignature: Ubuntu 5.3.0-19.20+kai1-generic 5.3.1
Uname: Linux 5.3.0-19-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu8
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC3: kai 3355 F.... pulseaudio
 /dev/snd/controlC1: kai 3355 F.... pulseaudio
 /dev/snd/controlC2: kai 3355 F.... pulseaudio
 /dev/snd/controlC0: kai 3355 F.... pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Wed Oct 30 23:21:52 2019
InstallationDate: Installed on 2019-06-18 (135 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
IwConfig:
 lo no wireless extensions.

 enp5s0 no wireless extensions.

 lxdbr0 no wireless extensions.
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcEnviron:
 TERM=tmux-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-19-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-5.3.0-19-generic N/A
 linux-backports-modules-5.3.0-19-generic N/A
 linux-firmware 1.183.1
RfKill:

SourcePackage: linux
UpgradeStatus: Upgraded to eoan on 2019-10-23 (8 days ago)
dmi.bios.date: 07/31/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P2.60
dmi.board.name: B450M Steel Legend
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.:bvrP2.60:bd07/31/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450MSteelLegend: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.

Revision history for this message
Kai Groner (kai-gronr) wrote :
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Kai Groner (kai-gronr) wrote :
Revision history for this message
Kai Groner (kai-gronr) wrote :

I haven't experienced this hang since 2020-01-12 (as far back as my logs go), so I think the upstream fix probably made it into the 19.10 and 20.04 kernels.

Changed in linux (Ubuntu):
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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