From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 42913] New: r600g: glx-swap-pixmap causes screen corruption
Date: Mon, 14 Nov 2011 11:59:37 +0000 [thread overview]
Message-ID: <bug-42913-502@http.bugs.freedesktop.org/> (raw)
https://bugs.freedesktop.org/show_bug.cgi?id=42913
Bug #: 42913
Summary: r600g: glx-swap-pixmap causes screen corruption
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: debian@carbon-project.org
First: I don't think this is bug 40610 because I don't see a crash but screen
corruption and (sometimes) the following lines in dmesg:
> radeon 0000:01:00.0: r600_check_texture_resource:1346 texture invalid format 0
> [drm:radeon_cs_ioctl] *ERROR* Invalid command stream !
But I'm no Mesa/Piglit expert, so my assumption might be wrong.
The Piglit test itself fails, the output is:
> Probe at (0,0)
> Expected: 0.000000 1.000000 0.000000 0.000000
> Observed: 0.000000 0.000000 1.000000 1.000000
Used stack:
Mesa: Git/9ae10e9c
libdrm: 2.4.27-1
Kernel: 3.1.1
X.org: 1.11.1.902-1
Let me know, if you need more information.
--
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-14 11:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-14 11:59 bugzilla-daemon [this message]
2011-11-15 16:38 ` [Bug 42913] r600g: glx-swap-pixmap causes screen corruption bugzilla-daemon
2011-11-15 17:34 ` bugzilla-daemon
2011-11-15 19:47 ` bugzilla-daemon
2011-11-22 13:31 ` bugzilla-daemon
2011-12-23 15:29 ` bugzilla-daemon
2011-12-28 12:26 ` 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-42913-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