From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 90997] [apitrace] GPU lockup with Dishonored and Gallium Nine
Date: Tue, 16 Jun 2015 19:41:36 +0000 [thread overview]
Message-ID: <bug-90997-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1184 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=90997
Bug ID: 90997
Summary: [apitrace] GPU lockup with Dishonored and Gallium Nine
Product: Mesa
Version: git
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/radeonsi
Assignee: dri-devel@lists.freedesktop.org
Reporter: commendsarnex@gmail.com
QA Contact: dri-devel@lists.freedesktop.org
Hi guys,
If I try to play Dishonored with Gallium Nine, I get a gpu lockup. If I play
the game with normal wine, there is no issue.
This apitrace consistently causes the lockup with Nine, but plays normally with
wine.
Apitrace: https://idontevenlift.no-ip.org/Dishonored.trace.xz
I've attached a run of the apitrace with R600_DEBUG=ps,vs,trace_cs.
There is no rlockup file created from the trace_cs, I've searched the whole
computer and tried multiple times.
I am using LLVM git, Mesa git, and kernel 4.0.5. My GPU is a Radeon HD
7950[Tahiti].
Thanks,
sarnex
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2556 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2015-06-16 19:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-16 19:41 bugzilla-daemon [this message]
2015-06-16 19:43 ` [Bug 90997] [apitrace] GPU lockup with Dishonored and Gallium Nine bugzilla-daemon
2015-06-16 19:44 ` bugzilla-daemon
2015-06-17 17:12 ` bugzilla-daemon
2016-09-29 22:49 ` 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-90997-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