From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 42998] New: [r600g] Regression: EVE Online graphics borked again (bisected)
Date: Wed, 16 Nov 2011 18:27:19 +0000 [thread overview]
Message-ID: <bug-42998-502@http.bugs.freedesktop.org/> (raw)
https://bugs.freedesktop.org/show_bug.cgi?id=42998
Bug #: 42998
Summary: [r600g] Regression: EVE Online graphics borked again
(bisected)
Classification: Unclassified
Product: Mesa
Version: git
Platform: x86-64 (AMD64)
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/r600
AssignedTo: dri-devel@lists.freedesktop.org
ReportedBy: luziphermcleod@yahoo.ie
Created attachment 53609
--> https://bugs.freedesktop.org/attachment.cgi?id=53609
Screenshot of login screen (bad)
EVE Online (via wine, usually works well) has severe graphical glitches on
r600g (HD4870). It's unplayable now. I bisected this down to:
r600g: lazy load for AR register
commit: 8e366dc365d01213b71b87ace47d30938db74845
http://cgit.freedesktop.org/mesa/mesa/commit/?id=8e366dc365d01213b71b87ace47d30938db74845
It seems that all triangles (I guess) are malformed, jump around and aren't
textured as they should. Also the system gets quite slow as long as the game is
active.
System:
Gentoo on vanilla kernel linux-3.2.0-rc2
Mesa from git, r600g driver
GPU: Radeon HD4870 (x2, only one used), CPU: Intel Core i7-965, MB: ASUS P6T
Deluxe
libdrm from git, xf86-video-ati from git, wine-1.3.32, xorg-server-1.11.2
--
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-16 18:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-16 18:27 bugzilla-daemon [this message]
2011-11-16 16:47 ` [Bug 42998] [r600g] Regression: EVE Online graphics borked again (bisected) bugzilla-daemon
2011-11-17 17:20 ` 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-42998-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.