From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 75794] New: Accumulation of black squares with OpenGL applications at high resolutions
Date: Wed, 05 Mar 2014 11:47:24 +0000 [thread overview]
Message-ID: <bug-75794-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 2066 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=75794
Priority: medium
Bug ID: 75794
Assignee: dri-devel@lists.freedesktop.org
Summary: Accumulation of black squares with OpenGL applications
at high resolutions
Severity: normal
Classification: Unclassified
OS: Linux (All)
Reporter: l.mollari@gmx.net
Hardware: x86-64 (AMD64)
Status: NEW
Version: 9.1
Component: Drivers/Gallium/r300
Product: Mesa
Created attachment 95154
--> https://bugs.freedesktop.org/attachment.cgi?id=95154&action=edit
glxgears with artifacts
I am having trouble with black areas made up by 8 × 8 pixel squares that occur
in 3D enabled applications when using the build-in TFTs native resolution of
1920 × 1200. Lower resolutions are not affected (see attached screenshots [1]
and [2]). The shape of these areas is sensitive to the actual content drawn in
such a way that it acts like a shadow or an impression of the actual 3D
geometry and even of 2D HUDs in 3D enabled games. These artifacts are
persistent across different applications i. e. the current application inherits
the artifacts from the previous one and vice versa [4]. I have uploaded a video
showing the artifacts described in 0 A. D.:
https://www.youtube.com/watch?v=Rpu-s8DowFw
I narrowed the glitches down to Mesa 3D version 9.1 that seemingly introduced
the bug. The bug seems to be still present in the most recent Mesa 3D and Linux
kernel versions [6].
Damaged hardware is unlikely to be the cause for these glitches since I was
able to reproduce the same artifacts on three different laptops of the same
product line, all equipped with the same GPU.
All tests were performed with unaltered default settings of the respective
distributions. No manually touched or customized xorg.conf files or kernel mode
settings were in place.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 3646 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 reply other threads:[~2014-03-05 11:47 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-05 11:47 bugzilla-daemon [this message]
2014-03-05 11:48 ` [Bug 75794] Accumulation of black squares with OpenGL applications at high resolutions bugzilla-daemon
2014-03-05 11:49 ` bugzilla-daemon
2014-03-05 11:50 ` bugzilla-daemon
2014-03-05 11:51 ` bugzilla-daemon
2014-03-05 11:52 ` bugzilla-daemon
2014-03-05 11:53 ` bugzilla-daemon
2014-03-05 11:55 ` bugzilla-daemon
2014-03-05 11:55 ` bugzilla-daemon
2014-03-05 14:13 ` bugzilla-daemon
2014-03-05 20:34 ` bugzilla-daemon
2014-03-11 7:45 ` bugzilla-daemon
2014-03-11 8:29 ` bugzilla-daemon
2014-03-11 13:00 ` bugzilla-daemon
2018-10-28 16:26 ` bugzilla-daemon
2019-09-18 18:52 ` 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-75794-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;
as well as URLs for NNTP newsgroup(s).