On Mit, 2003-03-12 at 10:55, Keith Whitwell wrote: > > In fact the lockup comes down to this one line: > > > --- radeon_driver.c 28 Oct 2002 02:21:14 -0000 1.44 > +++ radeon_driver.c 29 Oct 2002 13:49:25 -0000 1.45 > @@ -4639,6 +4639,7 @@ > save->cap0_trig_cntl = 0; > save->cap1_trig_cntl = 0; > save->bus_cntl = info->BusCntl; > + save->gen_int_cntl = info->gen_int_cntl; > /* > * If bursts are enabled, turn on discards > * Radeon doesn't have write bursts > > > Michel, what are the consequences of removing this?
Well, the idea of this line is to preserve the interrupts the chip generates over mode changes. What does this get set to before the lockup? Something else than during the first server generation? Thanks for tracking this down Keith, I'd love to dive into this, but I'm supposed to be learning for the exam tomorrow. :( I'll hopefully find the time during the weekend at the latest. -- Earthling Michel Dänzer (MrCooper)/ Debian GNU/Linux (powerpc) developer XFree86 and DRI project member / CS student, Free Software enthusiast ------------------------------------------------------- This SF.net email is sponsored by:Crypto Challenge is now open! Get cracking and register here for some mind boggling fun and the chance of winning an Apple iPod: http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
