From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 63124] New: [r600g] HyperZ lockup on REDWOOD in Half Life 2 Deathmatch
Date: Thu, 04 Apr 2013 14:59:46 +0000 [thread overview]
Message-ID: <bug-63124-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1205 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=63124
Priority: medium
Bug ID: 63124
Assignee: dri-devel@lists.freedesktop.org
Summary: [r600g] HyperZ lockup on REDWOOD in Half Life 2
Deathmatch
Severity: major
Classification: Unclassified
OS: Linux (All)
Reporter: abortretryfail@gmail.com
Hardware: x86-64 (AMD64)
Status: NEW
Version: git
Component: Drivers/DRI/R600
Product: Mesa
Created attachment 77426
--> https://bugs.freedesktop.org/attachment.cgi?id=77426&action=edit
dmesg output from when the GPU resets. This keeps happening until the game is
killed or you look away from whatever is causing the lockup.
This might be related to bug #61721, as it also occurs on my machine.
When playing Half Life 2 Deathmatch, the game runs great until certain scenes
cause a GPU lockup.
When run with R600_DEBUG=nohyperz there's no lockup, but performance is much
slower. (from ~85fps vsync 1400x1050 down to ~45fps w/o HyperZ)
I'll see if I can get an apitrace tonight.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 3038 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:[~2013-04-04 14:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-04 14:59 bugzilla-daemon [this message]
2013-04-04 15:09 ` [Bug 63124] [r600g] HyperZ lockup on REDWOOD in Half Life 2 Deathmatch bugzilla-daemon
2013-04-04 15:12 ` bugzilla-daemon
2013-04-16 10:20 ` bugzilla-daemon
2013-04-24 19:23 ` bugzilla-daemon
2013-05-02 14:12 ` 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-63124-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.