From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 39902] R600g Evergreen: GPU lockup after launch of Bioshock
Date: Wed, 10 Aug 2011 03:27:07 -0700 (PDT) [thread overview]
Message-ID: <20110810102707.694151300A9@annarchy.freedesktop.org> (raw)
In-Reply-To: <bug-39902-502@http.bugs.freedesktop.org/>
https://bugs.freedesktop.org/show_bug.cgi?id=39902
--- Comment #4 from Sven Arvidsson <sa@whiz.se> 2011-08-10 03:27:07 PDT ---
Bioshock has been working for me in the past (on Evergreen), so this could be a
regression. Specifically I was using git
2fe39b46e73aea37152777fe11d489e0b1bc3f92 and Wine 1.3.22. I will try it again
when I have more time.
Keep in mind that to get the game running you need to revert commit
6a35cbb656e0f8a2479a63eadefb1ab85f42d490 to work around bug 38501.
Also, I think developers prefer if you file new and separate bug reports for
issues with different games. It could be that the GPU hangs you describe all
come from the same bug, but it could also be different problems all showing up
in the same way.
--
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 10:27 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
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 [this message]
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=20110810102707.694151300A9@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