From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 107204] GPU hang (ring gfx timeout) in OpenGL game
Date: Thu, 12 Jul 2018 12:45:24 +0000 [thread overview]
Message-ID: <bug-107204-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1176 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=107204
Bug ID: 107204
Summary: GPU hang (ring gfx timeout) in OpenGL game
Product: Mesa
Version: git
Hardware: All
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/radeonsi
Assignee: dri-devel@lists.freedesktop.org
Reporter: fbz-me@milek7.pl
QA Contact: dri-devel@lists.freedesktop.org
Created attachment 140587
--> https://bugs.freedesktop.org/attachment.cgi?id=140587&action=edit
Dumps from GALLIUM_DDEBUG
It hangs in OpenGL game immediately after startup almost always (but sometimes
it goes through and works) with dmesg message:
>[drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, last signaled seq=3324, last emitted seq=3327
I tested it on Radeon RX580, mainline kernel 4.18, Mesa 18.1.3 and Mesa git
c0874947f1.
I could provide game code for testing but I would have to package minimal
assets as full game weights pretty much.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2716 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 reply other threads:[~2018-07-12 12:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-12 12:45 bugzilla-daemon [this message]
2018-07-13 16:25 ` [Bug 107204] GPU hang (ring gfx timeout) with out of bounds UBO read in shader bugzilla-daemon
2018-07-13 16:28 ` bugzilla-daemon
2019-09-25 18:09 ` 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-107204-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.