Bug 27729

I suspect this is a problem with compressed textures.

Can you go up the stack trace into fallback_generate_mipmap() and print the value of texObj->Image[face][baseLevel]->TexFormat ?

(In reply to comment #1)
> I suspect this is a problem with compressed textures.
> 
> Can you go up the stack trace into fallback_generate_mipmap() and print the
> value of texObj->Image[face][baseLevel]->TexFormat ?

(gdb) print texObj->Image[face][baseLevel]->TexFormat
$1 = 45

Created attachment 35287 [details]
updated r300g backtrace

It now crashes with a different assertion (backtrace attached for both r300g and swrastg).

Created attachment 35288 [details]
swrastg backtrace

Note that I have libtxc_dxtn.so installed, but it crashes with different bt even without it.

I think I have this fixed now.  Can you re-test with mesa commit db14a8022a2a957c83b1fe33a84af3cdb1952d68 or later?

(In reply to comment #6)
> I think I have this fixed now.  Can you re-test with mesa commit
> db14a8022a2a957c83b1fe33a84af3cdb1952d68 or later?

With 7567f05199f1ca114cc57e3a11ac101d3707f819 it's still crashing with the same backtraces of comment #3 and comment #4.

Created attachment 35312 [details] [review]
patch for r300g is_format_supported()

Here's a patch for r300g (totally untested) that might help.  If it doesn't, maybe you could debug further and fix the patch.

I think the softpipe bug is something else.  Could you provide the values of the vars at the failure point?

(In reply to comment #8)
> Created an attachment (id=35312) [details]
> patch for r300g is_format_supported()
> 
> Here's a patch for r300g (totally untested) that might help.  If it doesn't,
> maybe you could debug further and fix the patch.

OK, with that patch r300g now crashes similar to swrastg.

> I think the softpipe bug is something else.  Could you provide the values of
> the vars at the failure point?

(gdb) p index
$2 = 1
(gdb) p t->psizoutindex
$3 = -1
(gdb) p t->prevInstWrotePsiz
$4 = 0 '\000'
(gdb) p t->outputMapping[index]
$5 = 19828484

Other vars?

> (gdb) p index
> $2 = 1
> (gdb) p t->psizoutindex
> $3 = -1
> (gdb) p t->prevInstWrotePsiz
> $4 = 0 '\000'
> (gdb) p t->outputMapping[index]
> $5 = 19828484
> 
> Other vars?

That was with r300g. With swrastg:
(gdb) p t->outputMapping[index]
$1 = 19617796

Can you do "export ST_DEBUG=mesa,tgsi" and re-run?  That should print the GPU instructions to stderr.  Please attach that output to the bug report.  Thanks.

Created attachment 35316 [details]
swrastg debug output with "ST_DEBUG=mesa,tgsi"

(In reply to comment #11)
> Can you do "export ST_DEBUG=mesa,tgsi" and re-run?  That should print the GPU
> instructions to stderr.  Please attach that output to the bug report.  Thanks.

Output with swrastg and mesa up to 37e98e5cd217075d58456753ed8450dc116fe32c is attached.

I've moved some of the debug code to get more useful info from "ST_DEBUG=mesa,tgsi".

Can you repeat the test with the latest Mesa code (commit ce0844b44cb3924323ed1fd2b75cda4dbd0013c7) or later?  Thanks.

Created attachment 35327 [details]
swrastg debug output with "ST_DEBUG=mesa,tgsi"

Anyway you may also want to try the game yourself from http://trac.wildfiregames.com/wiki/LatestRelease since it appears it will be a common open source game when finished.

In the meantime 95bfc8f32571751c5c9ec6d8e84f5e3c28d1b20e has been committed from Marek Olšák which is a subset of attached "patch for r300g is_format_supported()", but which appears to also fix the r300g problem.

(In reply to comment #15)
> In the meantime 95bfc8f32571751c5c9ec6d8e84f5e3c28d1b20e has been committed
> from Marek Olšák which is a subset of attached "patch for r300g
> is_format_supported()", but which appears to also fix the r300g problem.

Yes but the S3TC code appears to be bloody slow, e.g. the TA3D game seems to load a new texture everytime a new GUI element shows up and during that the game basically locks up for 5 seconds with 100% CPU load. This is unbearable.

Is this still an issue with current Mesa git?

Created attachment 35535 [details]
updated r300g backtrace with ST_DEBUG=mesa,tgsi with mesa 7c5e2672

(In reply to comment #17)
> Is this still an issue with current Mesa git?

With mesa up to 7c5e2672f050644bcab6902b11d0ff4036603bb3 both r300g and swrast are still crashing, but now in a different way. Game log + backtrace are attached.

Created attachment 35536 [details]
updated swrastg backtrace with ST_DEBUG=mesa,tgsi with mesa 7c5e2672

This appears to be fixed, the game is however still crashing later, see bug #28169.