Bug 35446

Summary:	Problem with Blender and big textures
Product:	Mesa	Reporter:	Václav Čermák <disnel>
Component:	Drivers/Gallium/r300	Assignee:	Default DRI bug account <dri-devel>
Status:	RESOLVED NOTABUG	QA Contact:
Severity:	normal
Priority:	medium
Version:	git
Hardware:	x86-64 (AMD64)
OS:	Linux (All)
Whiteboard:
i915 platform:		i915 features:
Attachments:	dmesg output

Description Václav Čermák 2011-03-19 03:57:37 UTC

When I try to use a big texture (4096x4096) in blender 2.56beta, I get following error:

r300: CS space validation failed. (not enough memory?) Skipping rendering.

and no texture is displayed. Smaller textures (tested 2048x2048) works fine. Also with LIBGL_ALWAYS_SOFTWARE=1 it works fine. When I try bigger texture (8000x6048), I get no error, but also no texture and I can see screen corruption with Compiz (bad window shadows, applets on panel, background on 2nd display etc).

Blender files with textures and image with corrupted display are here

http://devel.disnel.com/tmp/

(I dont'know, how big files can I attach here). I'am using mesa 7.11.0-git2011016+gallium from xorg-edgers with Ubuntu 10.10 x86_64. My graphics card is Radeon X1400.

Comment 1 Marek Olšák 2011-03-19 05:41:01 UTC

When the CS space validation fails, it means there is not enough space either in the video memory or in the GPU-accessible system memory.

How many bits per pixel does the texture have? 4096x4096 is the maximum hardware limit. Any larger texture is not loaded and OpenGL will return an error to the application (but Blender seems to ignore it), and can draw either a black or white color instead.

Please post the output of:

RADEON_DEBUG=info glxgears

I am interested in the lines beginning with "r300:"

Comment 2 Marek Olšák 2011-03-19 05:52:03 UTC

Also please attach your dmesg.

Comment 3 Václav Čermák 2011-03-19 06:39:11 UTC

Created attachment 44615 [details] [review]
dmesg output

Comment 4 Václav Čermák 2011-03-19 06:40:41 UTC

glxgears does not write anything interesting:


disnel@infimi:~$ RADEON_DEBUG=info glxgears
Running synchronized to the vertical refresh.  The framerate should be
approximately the same as the monitor refresh rate.
304 frames in 5.0 seconds = 60.708 FPS
303 frames in 5.0 seconds = 60.565 FPS
^C
disnel@infimi:~$ 

dmesg attached. Texture has 24bit per pixel.

Comment 5 Marek Olšák 2011-03-19 12:42:19 UTC

(In reply to comment #4)
> glxgears does not write anything interesting:
> 
> 
> disnel@infimi:~$ RADEON_DEBUG=info glxgears
> Running synchronized to the vertical refresh.  The framerate should be
> approximately the same as the monitor refresh rate.
> 304 frames in 5.0 seconds = 60.708 FPS
> 303 frames in 5.0 seconds = 60.565 FPS
> ^C
> disnel@infimi:~$ 
> 
> dmesg attached. Texture has 24bit per pixel.

You seem to be using indirect rendering. Please post the output of:

LIBGL_DEBUG=verbose glxgears

Comment 6 Václav Čermák 2011-03-19 12:50:15 UTC

disnel@infimi:~$ LIBGL_DEBUG=verbose glxgears
libGL: OpenDriver: trying /usr/lib/dri/tls/r300_dri.so
libGL: OpenDriver: trying /usr/lib/dri/r300_dri.so
libGL: Can't open configuration file /etc/drirc: No such file or directory.
libGL: Can't open configuration file /etc/drirc: No such file or directory.
Running synchronized to the vertical refresh.  The framerate should be
approximately the same as the monitor refresh rate.
304 frames in 5.0 seconds = 60.672 FPS
303 frames in 5.0 seconds = 60.560 FPS
302 frames in 5.0 seconds = 60.368 FPS
^C
disnel@infimi:~$

Comment 7 Tomasz P. 2012-12-05 17:09:02 UTC

Is there still a problem with that?

Comment 8 Václav Čermák 2012-12-05 18:34:37 UTC

That old machine with Radeon X1400 is gone now (machine works, I can log in through ssh, but display shows nothing, it is hardware failure, because is does not show even setup), so I cannot test it. In new laptop I have Nvidia card....

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.