----- Original Message ----- From: "Michel D�nzer" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Saturday, February 01, 2003 6:39 PM Subject: Re: [XFree86] 4.2.99.4 no display, locked keyboard (Radeon7500Mobility)
> On Mon, 2003-01-27 at 10:14, Nathaniel Gray wrote: > > """ > > I guess this doesn't happen with DRI disabled? Looks like pure luck to > > me that RADEONWaitForVerticalSync() ever returns when the DRM handles > > vertical blank interrupts. I'll look into fixing that if noone beats me > > to it. > > """ > > > > True, the problem doesn't occur unless DRI is enabled. > > This patch works for me with DRI enabled, can you (or anyone seeing the > problem, for that matter) try it? > > There could still be an even worse problem if the vertical blank > interrupt stops working for some reason (I've seen that happen after > some weird 3D client crashes). Another possibility would be polling the > CRTC_VBLANK_SAVE bit in the CRTC_STATUS register. Kevin, Hui, anyone > interested, what do you think? It appears RADEONWaitForVerticalSync can cause some race conditon with DRM WaitVBlank routine. If this is the case, Michel's patch should work. Since the display driver can also use CRTC2 (different from CRTC1's vblank condition) when DRI is enabled, this makes things more complicated. Judging from current situation, we probably should take RADEONWaitForVerticalSync and RADEONWaitForVerticalSync2 all out of the cursor routines. The WaitForVerticalSync functions were added for avoiding flickering problem when switching between ARGB and BW cursors. This problem is much less severe than having WaitForVerticalSync to time out, particularly if ARGB cursor is not used as default (has this been decided?). We can work this thing out after 4.3 release. Hui > > > """ > > > 2. I was using KDM and after exiting X my machine would lock up as it > > > tried to restart the login screen. I think that even without KDM I > > > couldn't restart X after I started it once. I'm not positive about > > > this though. > > > > Can you verify that? Would be interesting to know. > > """ > > > > Nope, I can't verify it. I guess my system just got into a bad state > > somehow. I'm using 4.2.99.4 right now and have successfully restarted > > X many times. > > So you have verified that it only happens with a display manager. :) > > > I haven't tried using KDM again though. > > Probably still happens with that? One possibility is one or more > processes keeping the DRM open (Qt comes to mind) long enough to prevent > the next server generation from enabling the DRI. That causing a lockup > would still be a bug, but this might give opportunities for workarounds. > > > -- > Earthling Michel D�nzer (MrCooper)/ Debian GNU/Linux (powerpc) developer > XFree86 and DRI project member / CS student, Free Software enthusiast > _______________________________________________ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
