From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 46161] New: [regression] Commit 356eb0aadb causes compiz redraw issues
Date: Thu, 16 Feb 2012 11:33:39 +0000 [thread overview]
Message-ID: <bug-46161-502@http.bugs.freedesktop.org/> (raw)
https://bugs.freedesktop.org/show_bug.cgi?id=46161
Bug #: 46161
Summary: [regression] Commit 356eb0aadb causes compiz redraw
issues
Classification: Unclassified
Product: Mesa
Version: unspecified
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: h.judt@gmx.at
"r600g: fix tiling with cayman and virtual memory" renders compiz unusable on AMD Radeon HD 6950. Parts of the screen do not get updated, show only the
background or other unpredictable redraw problems.
In dmesg there are a lot of these messages:
radeon 0000:01:00.0: bo ffff8803df3e8400 va 0x02600000 conflict with (bo ffff8803cc35cc00 0x025FE000 0x02606000)
radeon 0000:01:00.0: bo ffff8803e228c800 va 0x02600000 conflict with (bo ffff8803cc35cc00 0x025FE000 0x02606000)
radeon 0000:01:00.0: bo ffff880420fbac00 va 0x02600000 conflict with (bo ffff8803cc35cc00 0x025FE000 0x02606000)
radeon 0000:01:00.0: bo ffff8803bfa14c00 va 0x02600000 conflict with (bo ffff8803cc35cc00 0x025FE000 0x02606000)
radeon 0000:01:00.0: bo ffff8803bfa14c00 va 0x02600000 conflict with (bo ffff8803cc35cc00 0x025FE000 0x02606000)
radeon 0000:01:00.0: bo ffff8803bfa14c00 va 0x02600000 conflict with (bo ffff8803cc35cc00 0x025FE000 0x02606000)
--
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:[~2012-02-16 11:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-16 11:33 bugzilla-daemon [this message]
2012-02-21 22:09 ` [Bug 46161] [regression] Commit 356eb0aadb causes compiz redraw issues 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-46161-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.