From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 110130] ring gfx timeout when playing warcraft 3
Date: Fri, 15 Mar 2019 11:55:09 +0000 [thread overview]
Message-ID: <bug-110130-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1401 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=110130
Bug ID: 110130
Summary: ring gfx timeout when playing warcraft 3
Product: Mesa
Version: git
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/radeonsi
Assignee: dri-devel@lists.freedesktop.org
Reporter: haagch@frickel.club
QA Contact: dri-devel@lists.freedesktop.org
Created attachment 143678
--> https://bugs.freedesktop.org/attachment.cgi?id=143678&action=edit
kernel log
Vega 64, Linux 5.0, mesa git 1ea42894c70, llvm git
https://github.com/llvm-mirror/llvm/commit/d8706fcd747
Unfortunately hard to reproduce:
Play custom maps in warcraft 3 (started with -opengl) in wine (4.1) for a few
hours and maybe it'll happen.
Interestingly amdgpu thinks kwin is the culprit:
Mär 14 23:58:30 c-pc kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring
gfx timeout, signaled seq=5170371, emitted seq=5170373
Mär 14 23:58:30 c-pc kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process
information: process kwin_x11 pid 999 thread kwin_x11:cs0 pid 1396
I've also seen it say steam instead of kwin.
Other games do not seem to trigger this.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2947 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
next reply other threads:[~2019-03-15 11:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-15 11:55 bugzilla-daemon [this message]
2019-09-25 18:49 ` [Bug 110130] ring gfx timeout when playing warcraft 3 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-110130-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