From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 43332] New: corrupted output in mesa-demo/fp-tri using r600g on evergreen
Date: Tue, 29 Nov 2011 11:09:58 +0000 [thread overview]
Message-ID: <bug-43332-502@http.bugs.freedesktop.org/> (raw)
https://bugs.freedesktop.org/show_bug.cgi?id=43332
Bug #: 43332
Summary: corrupted output in mesa-demo/fp-tri using r600g on
evergreen
Classification: Unclassified
Product: Mesa
Version: git
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: stefano.teso@gmail.com
Hi,
using mesa from git master (commit 76ba431b97087e2d5ca0351e0d613f0812fd1425),
the mesa demo fp-tri, when running the scs.txt shader, displays the correct
output overlayed by random blue-ish blocks (perhaps alpha channel corruption?).
The bug doesn't affect llvmpipe. Only scs.txt seems to trigger the issue.
This is on evergreen hw:
01:00.0 VGA compatible controller: ATI Technologies Inc Robson CE [AMD Radeon
HD 6300 Series]
on an i7 machine with i386 debian unstable.
The bug is also present in the libGL 7.11.2 shipped by debian, so I don't think
it's a regression or a bug in my config.
Please let me know if you need more info.
Thanks,
--
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:[~2011-11-29 11:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-29 11:09 bugzilla-daemon [this message]
2011-11-29 3:10 ` [Bug 43332] corrupted output in mesa-demo/fp-tri using r600g on evergreen bugzilla-daemon
2011-12-15 17:37 ` bugzilla-daemon
2011-12-15 17:53 ` bugzilla-daemon
2011-12-16 10:15 ` [Bug 43332] corrupted output in mesa-demo/fp-tri using r600g bugzilla-daemon
2011-12-16 16:46 ` bugzilla-daemon
2011-12-29 17:13 ` 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-43332-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.