Hit while trying out the r300g driver by playing Oolite (svn HEAD, no OXPs needed, but shaders turned up to full). Setup: Debian testing/unstable, with bits from experimental. xserver-xorg-core 1.7.5 xserver-xorg-video-radeon 6.12.192-1 libdrm 2.4.19 (local build, with packaging adapted from 2.4.18-4) mesa git 2ad8692a (local build, with packaging adapted from 7.7-4) Oolite: svn://svn.berlios.de/oolite-linux/trunk
Reverting cba6430524198a1bdcdeada03cbe946a454f3935 stops the hardlock, but now there's a failing vertex shader. Looking into it now.
Tired, commented on wrong bug. Investigating yours now.
Can't figure out how to build your program. :T You hit the generic "error in shader compiler" assert. Could you run again with RADEON_DEBUG=fp set, and attach that log here?
Created attachment 34486 [details] Shader log from Oolite One log file, as requested. (This is with shader-effects-level set to 3.)
About compiling Oolite: "make -f Makefile pkg-deb" works here. ("debuild binary" would be fine, but debian/changelog is generated.) http://www.oolite.org/download has links to binaries.
I won't be able to reproduce exactly, without finding one of my older cards. Also oolite appears to refuse to enable fancy shaders. :T Basically, the shader is too big for the hardware. There's no obvious optimizations to be done, but I bet I could find some, if the shader is known to work on fglrx. I've pushed a patch to make it so that you get an error message instead of just an empty assertion.
Closing because the game loads longer shaders than hardware can handle.
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.