From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 99219] The Stanley Parable GPU hang when starting a new game
Date: Thu, 29 Dec 2016 10:29:32 +0000 [thread overview]
Message-ID: <bug-99219-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1072 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=99219
Bug ID: 99219
Summary: The Stanley Parable GPU hang when starting a new game
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
RX 480 with llvm 4.0.0svn_r290670, mesa git
Tested with linux 4.9 and 4.10-rc1, happens on both. Tested with ingame
settings medium and highest, happens with both.
This apitrace hangs my GPU:
https://haagch.frickel.club/files/stanley_linux.trace.xz
Dez 29 11:21:58 c-l kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx
timeout, last signaled seq=6391, last emitted seq=6394
Dez 29 11:21:58 c-l kernel: [drm] IP block:gfx_v8_0 is hung!
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2521 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:[~2016-12-29 10:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-29 10:29 bugzilla-daemon [this message]
2016-12-29 19:30 ` [Bug 99219] The Stanley Parable GPU hang when starting a new game bugzilla-daemon
2017-01-02 12:48 ` bugzilla-daemon
2017-01-02 22:03 ` bugzilla-daemon
2017-01-03 10:08 ` bugzilla-daemon
2017-01-03 11:17 ` bugzilla-daemon
2017-01-05 13:02 ` 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-99219-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.