On Sun, 28 Apr 2002, Leif Delgass wrote: > On Mon, 29 Apr 2002, José Fonseca wrote: > > > On 2002.04.29 00:33 Peter Andersson wrote: > > >> > > >> > > >> hmmm.. OK, here are some questions for you: Did you actually see the > > >> gears being drawn, or just the window with a black background? > > > I saw the gears. Previously when it crashed to xmon i only saw the > > > window with the black background. So this is the first time for me when > > > the gears actually get drawn. > > > > > >> If you saw them being drawn, did you see them moving before the lockup? > > > No motion the system hung as soon as it drew the first frame. > > > > This is strange. It seams that it drawed a full frame and copied the back > > to the front buffer. It's not clear where the fault happened, as it should > > be able to repeat this cicle over and over. > > > > > > > >> When the lockup happened, did the screen blank or did it just freeze? > > >> > > > It just froze. > > > > I said that u had to make ctrl-alt-del. This in PowerPC means what? Can u > > still ssh? If yes a backtrace from glxgears would be great. If not running > > > > DRI_MACH64_DEBUG=all glxgears > dump.txt 2>&1 > > > > would have to do. > > > > Actually turning on all the debugging options when you're not stepping > through in a debugger will probably __cause__ a lockup. Setting a > breakpoint at the SwapBuffers would let you get a frame of output at a > time, but you'd need to compile gears from the Mesa source with debugging > symbols.
OK, scratch that. I forgot that all implies sync, which will wait for idle after each frame, so you should be OK. You probably don't need all the output for primitives though, so I'd use: DRI_MACH64_DEBUG=sync,api,msg,ioctl glxgears > dump.txt 2>&1 -- Leif Delgass http://www.retinalburn.net _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
