Bug 24734

Made this upgrade today:

libgl1-mesa-dri (7.7.0~git20091023.68372274-0ubuntu0tormod~jaunty2) to 7.7.0~git20091026.50e113e3-0ubuntu0tormod~jaunty
libgl1-mesa-glx (7.7.0~git20091023.68372274-0ubuntu0tormod~jaunty2) to 7.7.0~git20091026.50e113e3-0ubuntu0tormod~jaunty
libglu1-mesa (7.7.0~git20091023.68372274-0ubuntu0tormod~jaunty2) to 7.7.0~git20091026.50e113e3-0ubuntu0tormod~jaunty
mesa-common-dev (7.7.0~git20091023.68372274-0ubuntu0tormod~jaunty2) to 7.7.0~git20091026.50e113e3-0ubuntu0tormod~jaunty
mesa-utils (7.7.0~git20091023.68372274-0ubuntu0tormod~jaunty2) to 7.7.0~git20091026.50e113e3-0ubuntu0tormod~jaunty

The problem is still present.

More info:

I'ts not compiz specific. 3d apps yield this:

libGL: OpenDriver: trying /usr/lib/dri/tls/i915_dri.so
libGL: OpenDriver: trying /usr/lib/dri/i915_dri.so
libGL error: dlopen /usr/lib/dri/i915_dri.so failed (/usr/lib/dri/i915_dri.so: undefined symbol: intel_miptree_image_offset)
libGL error: unable to load driver: i915_dri.so

and then:

Driver "i915" is not installed or does not support configuration.

or:

libGL error: driver pointer missing
libGL: OpenDriver: trying /usr/lib/dri/tls/swrast_dri.so
libGL: OpenDriver: trying /usr/lib/dri/swrast_dri.so

So it falls back to software rendering, which apparently, isn't supported in this compiz installation.

Seems like some sort of version mismatch. I'll happily report the versions of my currently installed libs.

Indeed, looks like a compilation/distribution issue. If you are only using packaged components, please raise the issue with your packagers.

This was introduced by http://cgit.freedesktop.org/mesa/mesa/commit/?h=mesa_7_6_branch&id=2d17dbfb5346b6d75e87c839148cbe125bf5cd6d "intel: Keep track of x,y offsets in miptrees and use them for blitting." which added intel_miptree_get_image_offset() and removed intel_miptree_image_offset().

I don't know what is still calling intel_miptree_image_offset(). Maybe something in trunk that was not updated in the 7.6 merge (http://cgit.freedesktop.org/mesa/mesa/commit/?id=46a784b7fd2dcab97c26d5ca02fb8f74945ba157).

$ grep -r intel_miptree_image_offset src/mesa/drivers/dri
src/mesa/drivers/dri/i915/i830_texstate.c:         intel_miptree_image_offset(intelObj->mt, 0, intelObj->firstLevel, 0);
src/mesa/drivers/dri/i915/i915_texstate.c:         intel_miptree_image_offset(intelObj->mt, 0, intelObj->firstLevel, 0);

Created attachment 30741 [details] [review]
possible fix

Looks like this function was also used in the i830/i915 texstate, as they need to adjust offset based on lod. This quick patch might fix it, or introduce some errors if firstLevel isn't 0...

Reassigning to anholt since it was his commit. :)

commit 70b17db918a2784296434877a43b4c4036be792a
Author: Eric Anholt <eric@anholt.net>
Date:   Tue Oct 27 10:26:09 2009 -0700

    i915: Fix driver for the miptree x/y offset changes.
    
    Bug #24734.

*** Bug 24750 has been marked as a duplicate of this bug. ***

I installed latest build of mesa. The bug is fixed. It would be interesting to know how to test for any side effects from the patch that Roland Scheidegger send. 

libgl1-mesa-dri (7.7.0~git20091028.24c61c8c-0ubuntu0tormod~jaunty) to 7.7.0~git20091029.f920d496-0ubuntu0tormod~jaunty
libgl1-mesa-glx (7.7.0~git20091028.24c61c8c-0ubuntu0tormod~jaunty) to 7.7.0~git20091029.f920d496-0ubuntu0tormod~jaunty
libglu1-mesa (7.7.0~git20091028.24c61c8c-0ubuntu0tormod~jaunty) to 7.7.0~git20091029.f920d496-0ubuntu0tormod~jaunty
mesa-common-dev (7.7.0~git20091028.24c61c8c-0ubuntu0tormod~jaunty) to 7.7.0~git20091029.f920d496-0ubuntu0tormod~jaunty
mesa-utils (7.7.0~git20091028.24c61c8c-0ubuntu0tormod~jaunty) to 7.7.0~git20091029.f920d496-0ubuntu0tormod~jaunty

And this bug (at least the same behavior) reappeared.

I downgraded the packages, disabled compiz, then upgraded the packages again. Gnome Desktop starts normally this way. Blender and glxgears work normally (as far as Blender can work with the current i915 driver). Can someone tell me how to obtain debug information?

> And this bug (at least the same behavior) reappeared.
> 
> I downgraded the packages, disabled compiz, then upgraded the packages again.
> Gnome Desktop starts normally this way. Blender and glxgears work normally (as
> far as Blender can work with the current i915 driver). Can someone tell me how
> to obtain debug information?
> 

Just to rule out that it's not the same kind of bug:

1) Replace your window manager with metacity
(fire up gconf-editor, change the key desktop/gnome/applications/window_manager -default and current- with metacity)
2) Upgrade again
3) In another VT (ctrl-alt-F1), type sudo /etc/init.d/gdm restart
4) login in gdm
5) In a gnome-terminal, type export LIBGL_DEBUG=verbose; glxinfo
6) Paste here the output

> 
> Just to rule out that it's not the same kind of bug:
> 
> 1) Replace your window manager with metacity
> (fire up gconf-editor, change the key desktop/gnome/applications/window_manager
> -default and current- with metacity)
> 2) Upgrade again
> 3) In another VT (ctrl-alt-F1), type sudo /etc/init.d/gdm restart
> 4) login in gdm
> 5) In a gnome-terminal, type export LIBGL_DEBUG=verbose; glxinfo
> 6) Paste here the output
> 

Sorry, I didn't see that you had upgraded again. Just do steps 5) and 6)

commit 2073006c9566b08888b4338748a843c645bd0db1
Author: Eric Anholt <eric@anholt.net>
Date:   Fri Oct 30 12:26:54 2009 -0700

    intel: Set the texture format in the TFP path.

Created attachment 30849 [details]
glxinfo debug

Made this upgrade

libgl1-mesa-dri (7.7.0~git20091028.24c61c8c-0ubuntu0tormod~jaunty) to 7.7.0~git20091029.f920d496-0ubuntu0tormod~jaunty
libgl1-mesa-glx (7.7.0~git20091028.24c61c8c-0ubuntu0tormod~jaunty) to 7.7.0~git20091029.f920d496-0ubuntu0tormod~jaunty
libglu1-mesa (7.7.0~git20091028.24c61c8c-0ubuntu0tormod~jaunty) to 7.7.0~git20091029.f920d496-0ubuntu0tormod~jaunty
mesa-common-dev (7.7.0~git20091028.24c61c8c-0ubuntu0tormod~jaunty) to 7.7.0~git20091029.f920d496-0ubuntu0tormod~jaunty
mesa-utils (7.7.0~git20091028.24c61c8c-0ubuntu0tormod~jaunty) to 7.7.0~git20091029.f920d496-0ubuntu0tormod~jaunty

The bug is still present.

Petar, if Eric posted a fix on the 30th, don't expect much improvement in the 20091029 package :) That fix (2073006c) is included in the 20091030 package.

Tormod I guess I upgrade my packages much faster than you can build them :)
I can confirm that the bug has been fixed in the 20091030 package.