All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 112297] AMDGPU recovery does recover desktop to an unstable state
Date: Fri, 15 Nov 2019 12:09:32 +0000	[thread overview]
Message-ID: <bug-112297-502@http.bugs.freedesktop.org/> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1580 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=112297

            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=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.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 2918 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

             reply	other threads:[~2019-11-15 12:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-15 12:09 bugzilla-daemon [this message]
2019-11-15 12:10 ` [Bug 112297] AMDGPU.gpu_recovery does recover desktop to an unusable state bugzilla-daemon
2019-11-15 15:08 ` bugzilla-daemon
2019-11-15 15:11 ` bugzilla-daemon
2019-11-19 10:01 ` bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-112297-502@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.org \
    --cc=dri-devel@lists.freedesktop.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.