| Bug ID | 112297 |
|---|---|
| Summary | AMDGPU recovery does recover desktop to an unstable state |
| Product | DRI |
| Version | unspecified |
| Hardware | x86-64 (AMD64) |
| OS | Linux (All) |
| Status | NEW |
| Severity | critical |
| Priority | not set |
| Component | DRM/AMDgpu |
| Assignee | dri-devel@lists.freedesktop.org |
| Reporter | dbiro97@gmail.com |
I have got Radeon RX 5700 XT which has unstable driver. So that amdgpu.gpu_recovery=3D1 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 a= ctual application that caused the crash, stays on the screen, The screen is flickering, vibrating, I'm frequently able to see some green rectangle at t= he top of the screen with full width. But I can able to move mouse. Also I can= not 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 wor= k.
| What | Removed | Added |
|---|---|---|
| Summary | AMDGPU recovery does recover desktop to an unstable state | AMDGPU.gpu_recovery does recover desktop to an unusable state |
| What | Removed | Added |
|---|---|---|
| Priority | not set | highest |
Don't expect this to work anytime soon unfortunately. AMD real= ly slacked off with the drivers for this and similar bug reports have been open for months= .=20 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= .
| What | Removed | Added |
|---|---|---|
| Status | NEW | RESOLVED |
| Resolution | --- | MOVED |
-- 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.