All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 64471] Radeon HD6570 lockup in Brütal Legend with HyperZ
Date: Tue, 12 Nov 2013 11:19:49 +0000	[thread overview]
Message-ID: <bug-64471-502-CT8mXCdXxt@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-64471-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 1093 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=64471

--- Comment #12 from Andre Heider <a.heider@gmail.com> ---
I tried this game again and the issue is still present.
Tested with 3.12 and recent mesa (head:
f0f202e6b764be803470e27cba9102f14361ae22).

However, with a current apitrace it's now possible to trace and replay it on
r600g to provoke the GPU reset. Using past apitraces makes the game work
without traces/glitches.
I'm using apitrace head 0227203a229e85f98a491c6b9480c0bc210f1dbb, I didn't test
if a replay with older versions yields the hang.

I've uploaded a trace here (~260MiB):
http://static.hackmii.com/dhewg/brutalz.trace.xz

Replaying that without R600_HYPERZ reliably reproduces GPU hangs on my BARTS
card. Replaying it with R600_HYPERZ=0 makes the hangs go away, but you'll see
glitches on the hero's face (effects like described above).

Note: Trace is 1920x1200 fullscreen. Windowed mode or different resolutions
didn't always lockup. I tried to trim the trace down, but apitrace choked on
it.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 1978 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

  parent reply	other threads:[~2013-11-12 11:19 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-11 13:02 [Bug 64471] New: Radeon HD6570 lockup in Brütal Legend bugzilla-daemon
2013-05-11 13:02 ` [Bug 64471] " bugzilla-daemon
2013-05-11 19:36 ` bugzilla-daemon
2013-05-12  6:27 ` bugzilla-daemon
2013-05-12  6:47 ` bugzilla-daemon
2013-05-24 17:08 ` bugzilla-daemon
2013-05-29  3:29 ` [Bug 64471] Radeon HD6570 lockup in Brütal Legend with HyperZ bugzilla-daemon
2013-05-29  3:30 ` bugzilla-daemon
2013-06-10 22:43 ` bugzilla-daemon
2013-08-05  9:01 ` bugzilla-daemon
2013-10-30 14:14 ` bugzilla-daemon
2013-10-31  2:51 ` bugzilla-daemon
2013-10-31  2:53 ` bugzilla-daemon
2013-11-12 11:19 ` bugzilla-daemon [this message]
2013-12-25 16:10 ` bugzilla-daemon
2014-01-23 20:39 ` bugzilla-daemon
2014-02-06 16:50 ` bugzilla-daemon
2014-02-07 17:58 ` bugzilla-daemon
2014-02-10 21:19 ` bugzilla-daemon
2014-02-17 18:58 ` bugzilla-daemon
2014-02-17 21:09 ` bugzilla-daemon
2014-02-18  6:42 ` bugzilla-daemon
2014-02-18  6:48 ` bugzilla-daemon
2014-02-18  7:32 ` bugzilla-daemon
2014-02-18 15:36 ` bugzilla-daemon
2014-02-18 16:05 ` bugzilla-daemon
2014-08-24 13:40 ` bugzilla-daemon
2014-08-25 19:07 ` bugzilla-daemon
2014-09-01 19:35 ` bugzilla-daemon
2014-12-29 21:34 ` bugzilla-daemon
2014-12-29 23:00 ` bugzilla-daemon
2014-12-30 10:00 ` bugzilla-daemon
2014-12-31  1:30 ` bugzilla-daemon
2015-02-07 13:43 ` 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-64471-502-CT8mXCdXxt@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.