this should happen on all radeons since radeon-rewrite. The issue here is that if texture images are specified from level 0 to some level, but if because of gl state (baselevel, maxlod etc.) the actually needed textures for rendering go from level x (!=0) to some level, miptree comparison will fail. The driver then will try to create another tree, but since it does try this only with level 0 as base it will always fail (with the error message "radeon_validate_texture failed to alloc miptree") if the calculated required firstlevel is not 0.
Note that actually there's another bug here since the fallback then always segfaults, but I didn't look at this.
I'm not actually sure what the intention of the code how to handle this is, but note that on r300 and up this should probably be fixed by not messing with the miptree at all when the required base level changes, since these chips can easily clamp both min and max levels. However, miptree changes are required for r100/r200 (which can only clamp the smallest mipmap used).
Can you check if current mesa_7_7_branch fixes the problem?
Please check if commit 960464e42dce138fde11c379ce7744bc4be14aa2 on mesa_7_7_branch fixes the problem.
I can't see any error with mipmap_comp_tests on rv280 and mesa up to
Author: Kristian HÃ¸gsberg <email@example.com>
Date: Tue May 18 14:45:10 2010 -0400
dri2_glx: Put the invalidate b/c code back in
BUT I see somewhat strange image in this test .. let me open new bug .....
-- 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/272.