On Fri, 2002-05-24 at 20:36, Tim Smith wrote: > > I've introduced a tiny usleep into the loop in radeon_accel.c to give syslog > a chance and my loghost now produces a couple of thousand lines of the form > > moomintroll kernel: [drm:radeon_freelist_get] skipping buf=23 age=48355 > done=48319 > moomintroll kernel: [drm:radeon_freelist_get] skipping buf=24 age=48356 > done=48319 > > Covering about 30 seconds prior to me hitting reset, so the card certainly > seems to be getting rather stuck, because 'done=N' doesn't increment over > that 30 seconds. The lines immediately prior to this storm read: > > May 24 18:16:36 moomintroll kernel: [drm:radeon_freelist_get] ret buf=14 > last=14 age=47687 done=47733 > May 24 18:16:36 moomintroll kernel: [drm:radeon_cp_dispatch_texture] tex: > ofs=0xe240 p=32 f=7 x=0 y=310 w=512 h=202 > May 24 18:16:36 moomintroll kernel: [drm:radeon_cp_dispatch_texture] > tex=2048x512 blit=2048 > May 24 18:16:36 moomintroll kernel: [drm:radeon_cp_dispatch_indirect] > indirect: buf=14 s=0x0 e=0xf820 > > This isn't consistent though. Later I get a similar lockup and the logs are > entirely different. Logs from a couple of tries are at > http://www.electronghost.co.uk/radlock1.txt.gz > > Any ideas about where I should look?
Logging the buffer age in radeon_cp_discard_buffer() and looking at what happened after the buffer with the age shown in 'done=xxxxx' was discarded might be interesting. -- Earthling Michel D�nzer (MrCooper)/ Debian GNU/Linux (powerpc) developer XFree86 and DRI project member / CS student, Free Software enthusiast _______________________________________________________________ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
