All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 31046] New: [r600g, tiling] visual errors and GPU resets
Date: Fri, 22 Oct 2010 03:29:30 -0700 (PDT)	[thread overview]
Message-ID: <bug-31046-502@http.bugs.freedesktop.org/> (raw)

https://bugs.freedesktop.org/show_bug.cgi?id=31046

           Summary: [r600g, tiling] visual errors and GPU resets
           Product: DRI
           Version: DRI CVS
          Platform: x86-64 (AMD64)
        OS/Version: Linux (All)
            Status: NEW
          Severity: major
          Priority: medium
         Component: DRM/Radeon
        AssignedTo: dri-devel@lists.freedesktop.org
        ReportedBy: liquid.acid@gmx.net


Hello!

Yesterday I saw with much delight that the was some new tiling code in r600g,
which could be enabled with a simple envvar. So I pulled drm-radeon-testing and
applied Dave's patch for the CS checker to it (this one:
http://article.gmane.org/gmane.comp.video.dri.devel/51060).

However I encountered several problems with the new code (exporting
R600_FORCE_TILING=1 makes a difference, so it is working to some extent:

1) ioquake3 shows lots of gfx errors. Mipmaps are affected the most (when
setting r_textureMode to GL_LINEAR these problems disappear), but also small
textures seem to be affected (staircases, which use small textures, are either
rendered totally black or black with white stripes).

2) doom3 (demo) shows similar mipmap-related errors.

3) ut2004 is completly unplayable, I get GPU resets nearly every frame and most
of the geometry is missing.

4) ut2003 kinda works, but the HUD is messed up and sprite rendering is totally
broken

Going to post some snips from the kernel log later.

My hardware:
01:00.0 VGA compatible controller: ATI Technologies Inc Radeon HD 4770 [RV740]

libdrm, mesa and xf86-video-ati are all git master tip.
ColorTiling is enabled in the xorg.conf, verified this by checking the Xorg
logfile.

Greets,
Tobias

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

             reply	other threads:[~2010-10-22 10:29 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-22 10:29 bugzilla-daemon [this message]
2010-10-22 10:31 ` [Bug 31046] [r600g, tiling] visual errors and GPU resets bugzilla-daemon
2010-10-22 11:22 ` bugzilla-daemon
2010-10-22 12:57 ` bugzilla-daemon
2010-10-28 23:49 ` bugzilla-daemon
2010-11-05  0:12 ` bugzilla-daemon
2010-12-07 20:22 ` bugzilla-daemon
2010-12-11 20:42 ` bugzilla-daemon
2011-01-15 22:45 ` bugzilla-daemon
2011-01-19 22:12 ` bugzilla-daemon
2011-01-26 21:01 ` bugzilla-daemon
2011-01-26 21:01 ` bugzilla-daemon
2011-01-26 21:01 ` bugzilla-daemon
2011-01-26 21:02 ` bugzilla-daemon
2011-02-01 21:17 ` 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-31046-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.