On Sat, 2004-07-03 at 00:51 +0200, Dieter NÃtzel wrote: > Am Freitag, 2. Juli 2004 18:55 schrieb Michel DÃnzer: > > On Fri, 2004-07-02 at 18:46 +0200, Dieter NÃtzel wrote: > > > > > > Run "gltestperf" on r200. > > > > > > http://marc.theaimsgroup.com/?l=dri-devel&m=108213539614605&w=2 > > > > > > Benchmark: 2 > > > ZSmooth Triangles > > > Current size: 480 > > > Elapsed time for the calibration test (341): 2.003000 > > > Selected number of benchmark iterations: 851 > > > Elapsed time for run 0: 15.413000 > > > Elapsed time for run 1: 15.377000 > > > Elapsed time for run 2: 15.303000 > > > r200WaitIrq: drmRadeonIrqWait: -16 > > > > > > >>>ZSmooth Triangles<<< > > > > > > Maybe a starting point? > > > > The same symptom doesn't necessarily mean it's the same problem. This is > > a common symptom after the chip has locked up, but IIRC that's not the > > case for you? > > True. > > But maybe a starting point?
Or maybe gltestperf simply queues commands which take longer than the drmRadeonIrqWait() timeout (3 seconds IIRC)? -- Earthling Michel DÃnzer | Debian (powerpc), X and DRI developer Libre software enthusiast | http://svcs.affero.net/rm.php?r=daenzer ------------------------------------------------------- This SF.Net email sponsored by Black Hat Briefings & Training. Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com -- _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
