dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 88561] [radeonsi][regression, bisected] Depth test/buffer issues in Portal
Date: Sun, 18 Jan 2015 17:34:27 +0000	[thread overview]
Message-ID: <bug-88561-502@http.bugs.freedesktop.org/> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1841 bytes --]

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

            Bug ID: 88561
           Summary: [radeonsi][regression,bisected] Depth test/buffer
                    issues in Portal
           Product: Mesa
           Version: git
          Hardware: Other
                OS: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Drivers/Gallium/radeonsi
          Assignee: dri-devel@lists.freedesktop.org
          Reporter: daniel@constexpr.org

Created attachment 112428
  --> https://bugs.freedesktop.org/attachment.cgi?id=112428&action=edit
Bad frame

With current Mesa master (commit 461103ef64858e9d81073fad1bd8222b70b2754b),
(some) background geometry will be randomly drawn above foreground for some
frames in Portal (also observed in the Portal mod Rexaura). It does not happen
often and the same scene may be fine depending on what was loaded before or
just randomness.

Bisecting blames commit 02ba7334d35cf8182048c17a149b16f18104c6bf
Author: Marek Olšák <marek.olsak@amd.com>
Date:   Sun Jan 4 22:16:53 2015 +0100

    radeonsi: don't use TC L2 for updating descriptors on SI

    It's causing problems, because we mix uncached CP DMA with cached
WRITE_DATA
    when updating the same memory.

    The solution for SI is to use uncached access here, because CP DMA doesn't
    support cached access.

    CIK will be handled in the next patch.

    Reviewed-by: Michel Dänzer <michel.daenzer@amd.com>

Simply reverting this commit on master causes other rendering issues.

GPU: Radeon HD 7950 (OpenGL renderer string: Gallium 0.4 on AMD TAHITI)
LLVM compiled from svn last week (r225584)
GCC: 4.8.4
Kernel: Linux 3.18.2-gentoo
Distro: Gentoo

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 3361 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

             reply	other threads:[~2015-01-18 17:34 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-18 17:34 bugzilla-daemon [this message]
2015-01-18 17:35 ` [Bug 88561] [radeonsi][regression, bisected] Depth test/buffer issues in Portal bugzilla-daemon
2015-01-18 17:36 ` bugzilla-daemon
2015-02-04 11:56 ` bugzilla-daemon
2015-02-05  7:26 ` bugzilla-daemon
2015-02-05 15:33 ` bugzilla-daemon
2015-02-06  2:58 ` bugzilla-daemon
2015-02-18 20:37 ` bugzilla-daemon
2015-02-19 12:12 ` bugzilla-daemon
2015-02-19 14:37 ` bugzilla-daemon
2015-02-19 19:25 ` bugzilla-daemon
2015-02-20  3:25 ` bugzilla-daemon
2015-02-20  3:26 ` bugzilla-daemon
2015-05-08 23:09 ` bugzilla-daemon
2015-05-23 20:47 ` 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-88561-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