[Mesa-dev] [Mesa3d-dev] mesa commit e648d4a1d1c0c5f70916e38366b863f0bec79a62 st/mesa: ignore gl_texture_object::BaseLevel when allocating gallium textures

[Brian Paul]

Maxim Levitsky wrote:
> On Mon, 2010-05-03 at 13:11 -0600, Brian Paul wrote: 
>> Xavier Chantry wrote:
>>> On Sun, May 2, 2010 at 3:16 PM, Marek Olšák <maraeo at gmail.com> wrote:
>>>> On Sat, May 1, 2010 at 11:31 PM, Maxim Levitsky <maximlevitsky at gmail.com>
>>>> wrote:
>>>>> This commit breaks compiz completely here on nvidia G50 (Geforce 8400M)
>>>>> Compiz shows dark screen.
>>>>> (Using nouveau drivers)
>>>>>
>>>>> Without this commit compiz works almost perfectly.
>>>>>
>>>>> The error messages from compiz:
>>>>>
>>>>>
>>>>> debug_get_bool_option: NV50_ALWAYS_PUSH = FALSE
>>>>> debug_get_bool_option: DRAW_FSE = FALSE
>>>>> debug_get_bool_option: DRAW_NO_FSE = FALSE
>>>>> debug_get_bool_option: GALLIUM_DUMP_VS = FALSE
>>>>> Mesa: Mesa 7.9-devel DEBUG build May  1 2010 19:02:06
>>>>> Mesa warning: software DXTn compression/decompression available
>>>>> debug_get_bool_option: MESA_MVP_DP4 = FALSE
>>>>> debug_get_flags_option: ST_DEBUG = 0x0
>>>>> Mesa: User error: GL_OUT_OF_MEMORY in glTexImage
>>>>> compiz (cube) - Warn: Failed to load
>>>>> slide: /usr/share/gdm/themes/Human/ubuntu.png
>>>>> ^CMesa: User error: GL_OUT_OF_MEMORY in glTexImage
>>>> The commit also causes surface_copy to be called with S3TC textures,
>>>> breaking loading of such textures in r300g. I am working on a fix for r300g
>>>> but I haven't expected to get such weird formats in surface_copy.
>>>>
>>>> FYI Maxim, please use mesa-dev at lists.freedesktop.org instead.
>>>>
>>>> -Marek
>>>>
>>> This commit also causes piglit fbo-3d test to fail with both llvmpipe
>>> and nv50 gallium.
>>> http://img163.imageshack.us/img163/535/fbo3d.png
>> Can you retest now?
> Nope, still same error.

Both compiz and fbo-3d?

For compiz, could you set a breakpoint on _mesa_error() to find out 
where the OUT_OF_MEMORY error is coming from?

-Brian