> > I have an application that has been running for 2-3 days no worries > > with vblank_mode=0, but of course chews CPU and tears the screen, I > > recently started running it with vblank_mode=2 or 3 and it hangs > > in the glXSwapBuffers after a few hours, it looks like it is repeatedly > > calling the ioctl, > > Have you tried adding some debugging output to find out why that is?
Just on this I've setup a separate test box, 815 chipset, 7500 reference board from ATI (the big huge one :-), and running my application after about 2-3 hours it crashed out with.. radeonWaitIrq: drmRadeonIrqWait: -16 I'm going to start tracking this in earnest now that I have a machine dedicated to finding it :-), my first thought it to load up the map dumper from the r300 stuff so that when I hit this condition I dump all the current dri maps to disk.. this should give me the ring buffer contents... and I might be able to track down the packet that wrecked it all.... (anyone see any major issues with this I'm might be missing?) Dave. -- David Airlie, Software Engineer http://www.skynet.ie/~airlied / airlied at skynet.ie pam_smb / Linux DECstation / Linux VAX / ILUG person ------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt -- _______________________________________________ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
