On Sun, 12 Sep 2004 22:00:45 +0200, Roland Scheidegger <[EMAIL PROTECTED]> wrote: > > > Marcello Maggioni wrote: > > On Sun, 12 Sep 2004 00:34:01 +0200, Roland Scheidegger > > <[EMAIL PROTECTED]> wrote: > > > >> > >>Marcello Maggioni wrote: > >> > >>>>My card is a 3D prophet Radeon 8500LE with R200 ,My drivers are the > >>>>lastest taken yesterday from CVS. > >>>> > >>>>I've downloaded the demo , and the game seemed to run fine .... at > >>>>least until I tried to shoot with a "Shock Rifle" . > >>>> > >>>>Just after the laser beam started to run from my rifle to the target > >>>>the system simply freezed . > >>> > >>>No one has ideas or info about this? > >> > >>I think some time ago it was suggested to create a small, empty room and > >>fire the shock rifle in that (and log the commands submitted to the gpu) > >>to see what's going on. I'll might just do that if I find some time, > >>though the fact that the lockup doesn't happen on anything else than > >>"real" R200 and not the derivative chips doesn't really help (and it > >>does not only not lockup on rv250, but actually looks correct too). > >> > >>Roland > >> > > > > > > Hi . I've heard of this . I can do those test if you can tell me how > > to catch the commands submitted to the GPU into a file or in some > > other ways . > Basically, you can simply use R200_DEBUG environment variable set to > "sanity" (there are other deubg values possible - see dri_debug_control > in r200_context.c), so start with something like "R200_DEBUG=san ut2k4 > >&ut2k4debugsan.log". > However, there are some problems with that approach: > 1) the log file will be HUGE (basically 3d rendering speed will be > limited by how fast your hd can write the log file...). > 2) you don't know what exactly to look for in the output - the commands > which caused the GPU lockup are typically not exactly at the end, but > somewhat before that. > > Roland >
I've finally done it :) It was quite difficult , the rendering speed was too slow and I couldn't reproduce the freeze with that speed (the game took hours to load into a stage ) . So I had to enable NMI_WATCHDOG then redirect the output of R200_DEBUG=san into /dev/shm (the memory is much faster than the HD! ) and then access by SSH into the system and copy the log file into a real filesystem before rebooting . Anyway now I have the log file , but the problem is that are 210 MB (6MB compressed) :O What should I do? posting it to the ML or not?? Bye Marcello ------------------------------------------------------- This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 Project Admins to receive an Apple iPod Mini FREE for your judgement on who ports your project to Linux PPC the best. Sponsored by IBM. Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php -- _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
