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 36088] New: [r300g, bisected] Oilrush: menu and UI are corrupted and flickering
Date: Fri,  8 Apr 2011 13:20:54 -0700 (PDT)	[thread overview]
Message-ID: <bug-36088-502@http.bugs.freedesktop.org/> (raw)

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

           Summary: [r300g, bisected] Oilrush: menu and UI are corrupted
                    and flickering
           Product: Mesa
           Version: git
          Platform: Other
        OS/Version: All
            Status: NEW
          Keywords: regression
          Severity: normal
          Priority: medium
         Component: Drivers/Gallium/r300
        AssignedTo: dri-devel@lists.freedesktop.org
        ReportedBy: pavel.ondracka@email.cz


Created an attachment (id=45432)
 --> (https://bugs.freedesktop.org/attachment.cgi?id=45432)
screenshot

437c748bf5072d2bded77a00c74c51cdb8b510e5 is the first bad commit
commit 437c748bf5072d2bded77a00c74c51cdb8b510e5
Author: Marek Olšák <maraeo@gmail.com>
Date:   Sun Apr 3 18:14:49 2011 +0200

    r300g: handle DISCARD_WHOLE_RESOURCE for buffers

Reverting this commit from current mesa git fixes it.

RADEON_NO_TCL=1 also works around this.

GPU:RV530
Kernel: 2.6.38.2
Mesa: c6e33ca285f9eba26cae2fdd74fb5cc694f1e74b

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

             reply	other threads:[~2011-04-08 20:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-08 20:20 bugzilla-daemon [this message]
2011-04-08 21:27 ` [Bug 36088] [r300g, bisected] Oilrush: menu and UI are corrupted and flickering 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-36088-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