| Priority | medium |
|---|---|
| Bug ID | 75794 |
| Assignee | dri-devel@lists.freedesktop.org |
| Summary | Accumulation of black squares with OpenGL applications at hig= h 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 [details] glxgears with artifacts I am having trouble with black areas made up by 8 =C3=97 8 pixel squares th= at occur in 3D enabled applications when using the build-in TFTs native resolution of 1920 =C3=97 1200. Lower resolutions are not affected (see attached screensh= ots [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 inhe= rits the artifacts from the previous one and vice versa [4]. I have uploaded a v= ideo showing the artifacts described in 0 A. D.: https://www.y= outube.com/watch?v=3DRpu-s8DowFw I narrowed the glitches down to Mesa 3D version 9.1 that seemingly introduc= ed the bug. The bug seems to be still present in the most recent Mesa 3D and L= inux 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.
| What | Removed | Added |
|---|---|---|
| Attachment #95154 description | glxgears with artifacts | 1. glxgears with artifacts |
| Attachment #95154 mime type | text/plain | image/png |
Created attachment 95155 [details]
2. glxgears without artifacts at lower resolution
Created attachment 95156 [details]
3. 0 A. D. with artifacts
Created attachment 95157 [details]
4. 0 A. D. with silhouette artifacts
Created attachment 95158 [details]
5. Latest Xorg.0.log from the affected system
Created attachment 95159 [details]
6. List of tested versions
Created attachment 95160 [details]
7. Output from lspci (excerpt)
Created attachment 95161 [details]
8. Output from xrandr
Can you use git to bisect between the 9.0 and 9.1 releases to see what commit caused the regression?
My attempt to track down the commit that introduced the glitches ended with the following error from the configure script, using revisions "mesa-9.1" and "mesa-9.0.3": configure: error: DRI driver directory 'r300' does not exist I followed the instructions given at the Ubuntu wiki site, using the configure command with the parameters as listed below: https://wiki.ubuntu.com/X/BisectingMesa git clone git://anongit.freedesktop.org/git/mesa/mesa ... ./configure --prefix=/usr --mandir=\${prefix}/share/man \ --infodir=\${prefix}/share/info --sysconfdir=/etc \ --localstatedir=/var --build=i486-linux-gnu --disable-gallium --with-driver=dri \ --with-dri-drivers="r300" --with-demos=xdemos --libdir=/usr/lib/glx \ --enable-glx-tls --enable-driglx-direct --disable-egl \ --disable-glu --disable-glut --disable-glw CFLAGS="-Wall -g -O2" To my understanding the particular driver "r300" is not (any longer?) part of what I have cloned so far from the git repository, hence the configure script wants to include a precompiled version. Could you please give me a hint how I can get past this missing driver obstacle? However opting out the parameter --with-dri-drivers="r300" enables the configure script and subsequently the make command to succeed even though glxgears, now running without artifacts at decent fps, is stuttering noticeably. This applies to 9.0.3 and 9.1 likewise.
First of all, have you confirmed that the problem is still pre= sent in Mesa 10.x? Mesa 9.0 already didn't have the classic r300 driver anymore. You need to u= se --with-gallium-drivers=3Dr300 instead of --with-dri-drivers=3D"r300&qu= ot; (and maybe also drop --disable-gallium just in case, although AFAICT that shouldn't ha= ve any effect).
Opening Google Chrome seems to "fix" the bug. Thats = weird, my computer is a HP Compaq nw8440 with a FireGL V5200 GPU, only resolutions over 1920x1080 trig= ger the bug. It's fine at 1920x1080 but not at 1920x1081 (In Window mode).
| What | Removed | Added |
|---|---|---|
| Status | NEW | RESOLVED |
| Resolution | --- | MOVED |
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this = link to our GitLab instance: https://gitlab.freedesktop.org/mesa/mesa/issues/360.