dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 108854] [polaris11] - Failed GPU reset after hang
Date: Sat, 24 Nov 2018 20:41:30 +0000	[thread overview]
Message-ID: <bug-108854-502@http.bugs.freedesktop.org/> (raw)


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

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

            Bug ID: 108854
           Summary: [polaris11] - Failed GPU reset after hang
           Product: DRI
           Version: DRI git
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: DRM/AMDgpu
          Assignee: dri-devel@lists.freedesktop.org
          Reporter: tseewald@gmail.com

Created attachment 142604
  --> https://bugs.freedesktop.org/attachment.cgi?id=142604&action=edit
dmesg showing the hang and failed gpu reset

Problem:

While running RuneLite [1] with GPU acceleration enabled, the system hangs
after  several minutes of seemingly normal operation. Once the GPU hangs, it
attempts to reset itself but fails with the following message:

[drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!

This hang causes the system to lock up and ssh is the only access possible.
There is no graphical corruption, the displays are simply frozen.

System Information:

GPU: POLARIS11 - RX 560 4GB (1002:67ff)
Mesa: 18.0.5
X11: 1.19.6
Firmware files should be the latest as I've pulled them from adg5f's repo [2].

Kernel parameters: "quiet splash scsi_mod.use_blk_mq=1 apparmor=2
security=apparmor amdgpu.gpu_recovery=1 spectre_v2=off"

I have reproduced this issue on:

4.20-rc3
amd-staging-drm-next (as of commit 1179994039abc10aab0d2f0ecfc4c65dfbd77438)

[1] https://github.com/runelite/runelite
[2] https://people.freedesktop.org/~agd5f/radeon_ucode/

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

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

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

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

             reply	other threads:[~2018-11-24 20:41 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-24 20:41 bugzilla-daemon [this message]
2018-12-01 18:17 ` [Bug 108854] [polaris11] - Failed GPU reset after hang bugzilla-daemon
2018-12-08 18:20 ` bugzilla-daemon
2018-12-08 18:27 ` bugzilla-daemon
2019-01-14 16:54 ` bugzilla-daemon
2019-01-14 16:55 ` bugzilla-daemon
2019-01-14 16:55 ` bugzilla-daemon
2019-01-14 16:57 ` bugzilla-daemon
2019-01-14 17:05 ` bugzilla-daemon
2019-01-14 17:42 ` bugzilla-daemon
2019-01-14 17:43 ` bugzilla-daemon
2019-01-23  0:20 ` [Bug 108854] [polaris11] - GPU Hang - ring gfx timeout bugzilla-daemon
2019-01-25 17:24 ` bugzilla-daemon
2019-01-25 17:26 ` bugzilla-daemon
2019-02-10  1:01 ` bugzilla-daemon
2019-02-21 17:56 ` bugzilla-daemon
2019-02-21 19:21 ` bugzilla-daemon
2019-02-22 17:03 ` bugzilla-daemon
2019-02-22 18:15 ` bugzilla-daemon
2019-02-22 18:31 ` bugzilla-daemon
2019-02-22 18:46 ` 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-108854-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox