From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 42683] New: [r300g] GPU lockup while playing WoW
Date: Mon, 07 Nov 2011 21:31:56 +0000 [thread overview]
Message-ID: <bug-42683-502@http.bugs.freedesktop.org/> (raw)
https://bugs.freedesktop.org/show_bug.cgi?id=42683
Bug #: 42683
Summary: [r300g] GPU lockup while playing WoW
Classification: Unclassified
Product: Mesa
Version: git
Platform: x86 (IA32)
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/r300
AssignedTo: dri-devel@lists.freedesktop.org
ReportedBy: rankincj@googlemail.com
Created attachment 53271
--> https://bugs.freedesktop.org/attachment.cgi?id=53271
dmesg log from GPU lockup
I'm not sure whether this is a new problem or just a particularly bad side
effect of bug #41698, but WoW has now begun locking up after just a few moments
of gameplay. I'm sure it wasn't as bad as this yesterday though.
The latest commit in git is:
commit dceb202297b39220fbbcb41267077fb3ff8d137a
Author: Kenneth Graunke <kenneth@whitecape.org>
Date: Mon Nov 7 12:07:44 2011 -0800
i965: Fix Sandybridge regression introduced by workaround-free math.
And I'm fairly sure it was working yesterday with:
commit 2318443ebd6bf9727676b530a3b057dcf13a3ca6
Author: Dave Airlie <airlied@redhat.com>
Date: Sun Nov 6 19:38:50 2011 +0000
gl3.txt: update for ARB_texture_storage.
There is something seriously wrong with r300g.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next reply other threads:[~2011-11-07 21:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-07 21:31 bugzilla-daemon [this message]
2011-11-07 16:44 ` [Bug 42683] [r300g] GPU lockup while playing WoW bugzilla-daemon
2011-11-07 22:50 ` bugzilla-daemon
2011-11-07 23:13 ` bugzilla-daemon
2011-11-22 20:57 ` bugzilla-daemon
2012-06-08 13:44 ` 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-42683-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.