From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 83205] New: GPU lockup when entering settings in Verdun game with HyperZ enabled
Date: Thu, 28 Aug 2014 18:21:31 +0000 [thread overview]
Message-ID: <bug-83205-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1023 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=83205
Priority: medium
Bug ID: 83205
Assignee: dri-devel@lists.freedesktop.org
Summary: GPU lockup when entering settings in Verdun game with
HyperZ enabled
Severity: normal
Classification: Unclassified
OS: Linux (All)
Reporter: geecko.dev@free.fr
Hardware: Other
Status: NEW
Version: git
Component: Drivers/Gallium/radeonsi
Product: Mesa
When playing Verdun (http://store.steampowered.com/app/242860/), every time I
go to the settings I get a GPU lockup. Without R600_DEBUG=hyperz everything is
fine.
I'm using mesa 4ca203f, llvm 216658, xorg-server 1.16, xf86-video-ati 7.4.0 on
Arch Linux. I tried on Linux 3.14, 3.16 and 3.17rc2 with the same results. My
graphics card is a HD 7950.
Here's my journalctl log: http://pastebin.com/s80VLPtr
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2426 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:[~2014-08-28 18:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-28 18:21 bugzilla-daemon [this message]
2014-08-29 0:28 ` [Bug 83205] GPU lockup when entering settings in Verdun game with HyperZ enabled bugzilla-daemon
2014-08-29 10:58 ` bugzilla-daemon
2014-08-29 11:06 ` bugzilla-daemon
2014-08-29 11:20 ` bugzilla-daemon
2014-08-29 11:35 ` bugzilla-daemon
2014-08-30 9:43 ` bugzilla-daemon
2014-08-30 10:38 ` bugzilla-daemon
2014-09-01 19:58 ` 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-83205-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.