CPU is AMD A9-9420 RADEON R5 GPU is: 00:01.0 0300: 1002:98e4 (rev da) 00:01.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Stoney [Radeon R2/R3/R4/R5 Graphics] (rev da) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device 8330 Flags: bus master, fast devsel, latency 0, IRQ 35 Memory at e0000000 (64-bit, prefetchable) [size=256M] Memory at f0800000 (64-bit, prefetchable) [size=8M] I/O ports at 4000 [size=256] Memory at f0400000 (32-bit, non-prefetchable) [size=256K] Expansion ROM at 000c0000 [disabled] [size=128K] Capabilities: [48] Vendor Specific Information: Len=08 <?> Capabilities: [50] Power Management version 3 Capabilities: [58] Express Root Complex Integrated Endpoint, MSI 00 Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 <?> Capabilities: [270] Secondary PCI Express <?> Capabilities: [2b0] Address Translation Service (ATS) Capabilities: [2c0] Page Request Interface (PRI) Capabilities: [2d0] Process Address Space ID (PASID) Kernel driver in use: amdgpu Kernel modules: amdgpu If I suspend the laptop then on resume the GPU does not work. I've tried with a 5.0 and a 5.2 kernel, same issue. dc=0 or dc=1 doesn't make any obvious difference. I have gpu recovery enabled, otherwise it really hangs. With Xorg, the screen looks the same as when suspended. With Wayland, there is bunch of garbage around. In both cases, the mouse moves around, but there are no screen updates. The following output shows up in dmesg with the last line repeating endlessly, probably correlated with screen update attempts: [ 48.337053] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled seq=73, emitted seq=75 [ 48.337202] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process gnome-shell pid 977 thread gnome-shel:cs0 pid 1005 [ 48.337206] [drm] IP block:gfx_v8_0 is hung! [ 48.337319] amdgpu 0000:00:01.0: GPU reset begin! [ 48.337761] amdgpu 0000:00:01.0: GRBM_SOFT_RESET=0x000F0001 [ 48.337817] amdgpu 0000:00:01.0: SRBM_SOFT_RESET=0x00000100 [ 48.468854] [drm] recover vram bo from shadow start [ 48.468855] [drm] recover vram bo from shadow done [ 48.468857] [drm] Skip scheduling IBs! [ 48.500792] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 48.502030] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 48.503933] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 49.144048] amdgpu 0000:00:01.0: GPU reset(2) succeeded! [ 49.147491] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 53.186659] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125! [ 56.651026] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!
Please attach your dmesg output and xorg log if using X.
Created attachment 145230 [details] dmesg
Created attachment 145231 [details] xorg log
Sorry, I should have thought of that. The dmesg is the same for both Wayland and xorg.
Created attachment 145236 [details] dmesg with drm.debug=4 I've seen mention elsewhere about setting the drm.debug value. If you need a different setting, let me know.
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/drm/amd/issues/898.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.