Bug 112297

Summary: AMDGPU.gpu_recovery does recover desktop to an unusable state
Product: DRI Reporter: David Biró <dbiro97>
Component: DRM/AMDgpuAssignee: Default DRI bug account <dri-devel>
Status: RESOLVED MOVED QA Contact:
Severity: critical    
Priority: highest    
Version: unspecified   
Hardware: x86-64 (AMD64)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:

Description David Biró 2019-11-15 12:09:32 UTC 
I have got Radeon RX 5700 XT which has unstable driver. So that amdgpu.gpu_recovery=1 flag would be helpful if even that could work well.
Unfortunately it doesn't.

My kernel's latest commit ID: 53dbc27ad5a93932ff1892a8e4ef266827d74a0f ( fix AVFS handling with custom powerplay table) On branch drm-next-5.5
Display server: X11
WM: BSPWM
DM: Slim

Journalctl output:
https://pastebin.com/if4PYda7

The error is the "average" ring sdma0 timeout. After reset, the actual application that caused the crash, stays on the screen, The screen is flickering, vibrating, I'm frequently able to see some green rectangle at the top of the screen with full width. But I can able to move mouse. Also I cannot do anything else, because then BSPWM can switch workspaces (I can see it by the type of the mouse cursor), but the crashed application stays on the screen anyway, so I have to restart.

At least, I can save my work if I remember which workspace contained my work.
Comment 1 Daniel Suarez 2019-11-15 15:11:14 UTC 
Don't expect this to work anytime soon unfortunately. AMD really slacked off with the drivers for this and similar bug reports have been open for months. 

As for your work, save early, save often while writing. Don't rely on auto-save doing it for you.  Get in the habit of Ctrl+S'ing often.

Ideally you shouldn't be using a 5700 if you're dealing with sensitive work.
Comment 2 Martin Peres 2019-11-19 10:01:52 UTC 
-- 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/957.

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.