All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 70411] 7970M PRIME: lockup with Distance game, recovery doesn't work
Date: Wed, 12 Feb 2014 08:20:05 +0000	[thread overview]
Message-ID: <bug-70411-2300-iY0KAJyPbV@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-70411-2300@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=70411

--- Comment #3 from Christoph Haag <haagch.christoph@googlemail.com> ---
Maybe it would have been good to mention, mesa is a relatively current git
version a21552a.



(In reply to Michel Dänzer from comment #2)
> Does setting the environment variable R600_DEBUG=nohyperz for running the
> game work around the problem?

Yes, with R600_DEBUG=nohyperz the game works and there is no lockup.

I guess it's possible that it stopped working when HyperZ was enabled by
default.

Still, this lockup is not nice since currently only a reboot makes the radeon
gpu usable again.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2014-02-12  8:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-11 21:38 [Bug 70411] New: 7970M PRIME: lockup with Distance game, recovery doesn't work bugzilla-daemon
2014-02-12  3:49 ` [Bug 70411] " bugzilla-daemon
2014-02-12  7:58 ` bugzilla-daemon
2014-02-12  8:20 ` bugzilla-daemon [this message]
2014-02-12 14:59 ` bugzilla-daemon
2014-05-26 23:24 ` 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-70411-2300-iY0KAJyPbV@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.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.