From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 92184] Many piglit assertion failures in radeon_unmap_renderbuffer
Date: Fri, 05 Feb 2016 05:39:56 +0000 [thread overview]
Message-ID: <bug-92184-502-Rt06iygHbj@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-92184-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 722 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=92184
--- Comment #3 from Timothy Arceri <t_arceri@yahoo.com.au> ---
The problem starts happening with this commit:
commit 085a86154553d86f8e4296b4c732901f781bdfd8
Author: Marek Olšák <marek.olsak@amd.com>
Date: Fri Aug 1 19:36:37 2014 +0200
radeon,r200: fix buffer validation after CS flush
This validates all bound buffers (CB, ZB, textures, DMA) at the beginning
of CS. This fixes "bo->space_accouned" assertion failures.
Tested by: Jochen Rollwagen <joro-2013@t-online.de>
Cc: mesa-stable@lists.freedesktop.org
Reviewed-by: Alex Deucher <alexander.deucher@amd.com>
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1760 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
next prev parent reply other threads:[~2016-02-05 5:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-29 21:24 [Bug 92184] Many piglit assertion failures in radeon_unmap_renderbuffer bugzilla-daemon
2015-11-30 23:27 ` bugzilla-daemon
2015-12-01 0:26 ` bugzilla-daemon
2016-02-05 5:39 ` bugzilla-daemon [this message]
2019-09-18 18:40 ` 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-92184-502-Rt06iygHbj@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).