dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 37490] New: texture corruption in r600/r600g when using DRI2, no texture corruption in r600 with dri1
Date: Mon, 23 May 2011 01:58:30 -0700 (PDT)	[thread overview]
Message-ID: <bug-37490-502@http.bugs.freedesktop.org/> (raw)

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

           Summary: texture corruption in r600/r600g when using DRI2, no
                    texture corruption in r600 with dri1
           Product: Mesa
           Version: 7.10
          Platform: x86-64 (AMD64)
        OS/Version: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Drivers/DRI/R600
        AssignedTo: dri-devel@lists.freedesktop.org
        ReportedBy: nenolod@systeminplace.net


hi,

i get texture corruption as seen in the attached screenshot when using dri2. 
when running more 3D intensive applications (like say, etracer), the texture
corruption increases resulting in some graphics primitives not being rendered.

this does not happen with DRI1, with DRI1, there is no corruption and all
primitives are rendered as expected.

this is on linux 2.6.38.6 with alpine patches, mesa 7.10.2 and xorg 1.10 with
xf86-video-ati 6.14.1, libdrm 2.4.25 and uclibc 0.9.32-rc3 (also with alpine
patches).

there are some bugs that look similar to what i am seeing, but they are all
marked RESOLVED, and none of them mention DRI2.

-- 
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:[~2011-05-23  8:58 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-23  8:58 bugzilla-daemon [this message]
2011-05-23  9:00 ` [Bug 37490] texture corruption in r600/r600g when using DRI2, no texture corruption in r600 with dri1 bugzilla-daemon
2011-05-23  9:36 ` bugzilla-daemon
2011-05-23 12:49 ` bugzilla-daemon
2011-05-23 17:22 ` bugzilla-daemon
2011-05-23 17:31 ` bugzilla-daemon
2011-05-23 19:45 ` bugzilla-daemon
2011-05-24  4:29 ` bugzilla-daemon
2011-05-24  4:31 ` bugzilla-daemon
2011-05-24  4:40 ` bugzilla-daemon
2011-05-24  4:41 ` bugzilla-daemon
2011-05-24  4:44 ` bugzilla-daemon
2011-05-24 15:41 ` bugzilla-daemon
2011-05-24 15:43 ` bugzilla-daemon
2011-05-24 20:34 ` bugzilla-daemon
2011-05-24 21:19 ` bugzilla-daemon
2011-05-24 21:32 ` bugzilla-daemon
2012-08-09 15:03 ` bugzilla-daemon
2012-11-02 16:18 ` bugzilla-daemon
2014-07-07 16:05 ` 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-37490-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).