From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 39902] R600g Evergreen: GPU lockup after launch of StarCraft II
Date: Tue, 9 Aug 2011 21:12:11 -0700 (PDT) [thread overview]
Message-ID: <20110810041211.ACEF413006A@annarchy.freedesktop.org> (raw)
In-Reply-To: <bug-39902-502@http.bugs.freedesktop.org/>
https://bugs.freedesktop.org/show_bug.cgi?id=39902
--- Comment #2 from runetmember@gmail.com 2011-08-09 21:12:11 PDT ---
You was right, there are probably problem with packaging of x86_64 of the
driver.
https://bugs.freedesktop.org/show_bug.cgi?id=39897#c12
I can not reproduce StarCraft II GPU lockup on pure x86 setup. Works fine on
low settings by the way.
But now I have another lockup-problem when I try to launch Bioshock or Metro
2033.
How to reproduce:
1. Install Bioshock demo: http://www.gamefront.com/files/8363410
2. Launch Bioshock. Wait few seconds.
3. Switch to any other text console, and after that switch back to graphics
console.
So now you should able to get GPU lockup. Log attached.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next prev parent reply other threads:[~2011-08-10 4:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-39902-502@http.bugs.freedesktop.org/>
2011-08-08 11:17 ` [Bug 39902] R600g Evergreen: GPU lockup after launch of StarCraft II bugzilla-daemon
2011-08-10 4:12 ` bugzilla-daemon [this message]
2011-08-10 4:12 ` [Bug 39902] R600g Evergreen: GPU lockup after launch of Bioshock bugzilla-daemon
2011-08-10 4:13 ` bugzilla-daemon
2011-08-10 7:50 ` bugzilla-daemon
2011-08-10 10:27 ` bugzilla-daemon
2012-04-29 15:46 ` bugzilla-daemon
2014-10-31 12:06 ` bugzilla-daemon
2014-10-31 12:48 ` 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=20110810041211.ACEF413006A@annarchy.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