From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 108854] [polaris11] - GPU Hang - ring gfx timeout
Date: Sun, 10 Feb 2019 01:01:52 +0000 [thread overview]
Message-ID: <bug-108854-502-4XKgeQdjja@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-108854-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 935 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=108854
--- Comment #12 from Tom Seewald <tseewald@gmail.com> ---
(In reply to Alex Deucher from comment #11)
> The reset was actually successful. The problem is, userspace components
> need to be aware of the reset and recreate their contexts. As a workaround,
> you can kill the problematic app or restart X.
Hmm, but then why will the machine not restart unless I use sysrq keys? I would
think a userspace issue wouldn't cause hung kernel tasks like that.
I'm also curious regarding why this program is causing the GPU to reset to
begin with, I have not seen others reporting issues on other platforms with
this program.
Is this ring gfx timeout purely a problem with userspace?
e.g.
[drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled
seq=32203, emitted seq=32205
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1779 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
next prev parent reply other threads:[~2019-02-10 1:01 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-24 20:41 [Bug 108854] [polaris11] - Failed GPU reset after hang bugzilla-daemon
2018-12-01 18:17 ` 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 [this message]
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-4XKgeQdjja@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