[965] render defects in google earth / atunnel screensaver (intrepid and jaunty-as-of-feb-3rd)

atunnel screensaver shows rendering glitches (some textures are momentarily rendered black, see attached screenshots). Repros consistently on intrepid and on jaunty live CD as of feb 3rd using a 965 machine with pci id 8086:2a02.

Eric Anholt et al are discussing this particular bug in this thread:
http://lists.freedesktop.org/archives/intel-gfx/2009-February/001351.html

Once Intel commits something upstream we should get this into jaunty (and possibly intrepid?).

---

Google Earth is know to also be affected, but probably a wide range of 3D apps see this from time to time.

These bugs might be the same issue but since Eric says it's probably chipset specific for 965 it might also be that at least the 945 issues/screenshots mentioned below are separate issues:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/262758
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/289106

Relevant upstream bugs include:
https://bugs.freedesktop.org/show_bug.cgi?id=19879
https://bugs.freedesktop.org/show_bug.cgi?id=19549

Everyone using RCs, ALPHAs & BETAs, please keep in mind that these are for TESTING ONLY!!! You need to remember that the testing continues after the release. However, by installing the FULL released STABLE version usually has these bugs fixed. Please reinstall stables & THEN report your issues. Thank You. Please do not contact me directly, instead please leave your questions, reports, problems, etc here so that everyone may benefit & help with your concerns. Thank You, Jay

Here is the upstream commit message:
http://cgit.freedesktop.org/mesa/mesa/commit/?id=68915fd6fac44dd000080298e3afb0669e8754aa

Here is the patch:
http://cgit.freedesktop.org/mesa/mesa/patch/?id=68915fd6fac44dd000080298e3afb0669e8754aa

I don't know yet if it's suitable for backporting to jaunty (or even to intrepid etc).
I've not tried to apply it to jaunty mesa because jaunty mesa does not compile at all when I do the usual "fakeroot debian/rules binary" (and this is _before_ I apply the patch so.... hmm)

I've fixed up this patch so that it applies cleanly to intrepid's mesa-7.2 and I've done some initial testing. On my 965 this patches fixes the rendering defects.

how to try this patch:
1. mkdir my_mesa_bits ; cd my_mesa_bits
2. sudo apt-get build-dep mesa
2. apt-get source mesa
3. cd mesa-7.2
4. patch -p0 < ~/path/to/atunnel_intrepid_final.patch
5. debuild -us -uc -b
6. cd ..
7. sudo dpkg -i libgl1-mesa-dri_7.2-1ubuntu2_i386.deb

Here is a debdiff that integrates the patch above into the mesa quilt (not sure if this is worth a SRU, but I don't use google earth myself so I don't know how how big the impact of this bug really is, if it was atunnel along I'd say no SRU for it?)

Now I've also prepared a debdiff for jaunty mesa that applies this patch. When I boot the jaunty alpha5 live CD on 965 I do see the rendering glitch (see screenshots attached above). However, I've not been able to test this debdiff at all because I don't have jaunty installed on my 965 machine (and I don't want to install it yet because it's my "stable" machine that I used for e-mail, skype etc). So while I think this jaunty debdiff fixes the problem for jaunty (like I know it did for intrepid), I have not tested it at all.

Thanks for the debdiff.

The patch looks okay (what I understand of it anyway). More importantly, I see the patch is happily upstream and there's been no changes to either of the two files it fixes since it went in 3 weeks ago.

I've committed it to git and will upload once I've verified it builds.

hello,

these patchs seem to be for jaunty. Can they be applied to intrepid too, or is ther another way to fix this issue ?

thanks

The debdiff I posted on 2009-03-01 is for intrepid and the debdiff I posted on 2009-03-02 is for Jaunty.

This bug was fixed in the package mesa - 7.4-0ubuntu1

---------------
mesa (7.4-0ubuntu1) jaunty; urgency=low

  * New upstream release, merge from debian-experimental
    (LP: #330476, #347171, #349127)
  * Drop 103_rs600_support.patch, included in this version.
  * Drop 104_swrast_fbconfigs.patch, included in this version.
  * Add 103_bump_965_texture_limit.diff. (LP: #146298)
  * Add 104_fix_dri2_ext_tfp.diff. (LP: #324854)

 -- Timo Aaltonen <email address hidden> Fri, 03 Apr 2009 12:42:06 +0300

Yesterday, I booted the jaunty live CD on the machine that was previously affected. With the new mesa upload the problem is indeed gone. Thanks a lot Timo!

Just updated Jaunty to the latest and I can confirm that the rendering glitch in atunnel is gone.

Thank you!

(Thinkpad T61 with GM965/GL960 Integrated Graphics Controller rev 0c).

I have latests updates but there are still issues in video rendering when compiz is enable, see attachment.

I tried to start a live cd of Fedora 11 Beta, in this version it does not happens.... (Maybe it helps to some developer)..

glxinfo
name of display: :0.0
display: :0 screen: 0
direct rendering: Yes
server glx vendor string: SGI
server glx version string: 1.2
server glx extensions:
    GLX_ARB_multisample, GLX_EXT_import_context, GLX_EXT_texture_from_pixmap,
    GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_MESA_copy_sub_buffer,
    GLX_OML_swap_method, GLX_SGI_make_current_read, GLX_SGI_swap_control,
    GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_visual_select_group
client glx vendor string: SGI
client glx version string: 1.4
client glx extensions:
    GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_import_context,
    GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_MESA_allocate_memory,
    GLX_MESA_copy_sub_buffer, GLX_MESA_swap_control,
    GLX_MESA_swap_frame_usage, GLX_OML_swap_method, GLX_OML_sync_control,
    GLX_SGI_make_current_read, GLX_SGI_swap_control, GLX_SGI_video_sync,
    GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer,
    GLX_SGIX_visual_select_group, GLX_EXT_texture_from_pixmap
GLX version: 1.2
GLX extensions:
    GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_import_context,
    GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_MESA_copy_sub_buffer,
    GLX_MESA_swap_control, GLX_MESA_swap_frame_usage, GLX_OML_swap_method,
    GLX_SGI_make_current_read, GLX_SGI_swap_control, GLX_SGI_video_sync,
    GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_visual_select_group
OpenGL vendor string: Tungsten Graphics, Inc
OpenGL renderer string: Mesa DRI Intel(R) 965GM GEM 20090326 2009Q1 RC2 x86/MMX/SSE2
OpenGL version string: 2.0 Mesa 7.4
OpenGL shading language version string: 1.10

00:02.0 VGA compatible controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (rev 03)
 Subsystem: Micro-Star International Co., Ltd. Device 2fb3
 Flags: bus master, fast devsel, latency 0, IRQ 2297
 Memory at fda00000 (64-bit, non-prefetchable) [size=1M]
 Memory at d0000000 (64-bit, prefetchable) [size=256M]
 I/O ports at b480 [size=8]
 Capabilities: <access denied>
 Kernel modules: intelfb

dpkg -s xserver-xorg-video-intel
Package: xserver-xorg-video-intel
Status: install ok installed
Priority: optional
Section: x11
Installed-Size: 1292
Maintainer: Ubuntu X-SWAT <email address hidden>
Architecture: i386
Version: 2:2.6.3-0ubuntu9
Replaces: xserver-xorg (<< 6.8.2-35), xserver-xorg-driver-i810, xserver-xorg-video-i810 (<< 2:1.9.91-1), xserver-xorg-video-i810-modesetting, xserver-xorg-video-intel-modesetting
Provides: xserver-xorg-video-5
Depends: libc6 (>= 2.4), libdrm-intel1 (>= 2.4.5), libdrm2 (>= 2.3.1), libpciaccess0 (>= 0.8.0+git20071002), libxext6, libxv1, libxvmc1, xserver-xorg-core (>= 2:1.5.99.901)
Conflicts: 915resolution, xserver-xorg-driver-i810, xserver-xorg-video-i810 (<< 2:1.9.91-1), xserver-xorg-video-i810-modesetting, xserver-xorg-video-intel-modesetting
Description: X.Org X server -- Intel i8xx, i9xx display driver
 This package provides the driver fo...

Sorry, this is not an issue with atunnel for my, Atunnel screensaver works fine but google earth and glxgears are having errors when them works with compiz activated.

Do I have to open a new bug report for this? Or this bug isn't be really fixed?

Same Problem here with a X61t 965...
This bug is a real pain in the ass and present since 2 Years or something like that. Will it ever be fixed?

Sebastian, this bug was fixed in jaunty. If you are seeing some issue using jaunty that's a separate bug report and you should use the command "ubuntu-bug xorg" to open a new bug report for it (remember to include screenshots or a photo of the corruption) and describe the bug as carefully as you can. In particular how to trigger the bug itself (this is the most useful piece of information for the developers).