Roland, On Tue, Jun 17, 2003 at 11:15:02PM +0200, Roland Scheidegger wrote: > >FWIW, I get that now always when I start the X server, then shut down > >the X server and start it again. DRI will never work again, unless I > >rmmod the radeon module manually before I restart the X server. Sounds > >like some initialization thing. > >lsmod will show (before starting X, but after manually inserting agpgart > >& radeon): > >Module Size Used by Not tainted > >radeon 102152 0 (unused) > >agpgart 13904 1 > > > >after X is started: > >radeon 102152 12 > >agpgart 13904 3 > > > >and after X shutdown (and restart with dri not working): > >radeon 102152 0 > >agpgart 13904 3 > > > >after rmmod radeon the agpgart used count will be back to 0. > It looks like the driver doesn't release the agp device when the X > Server is shut down. At next startup (with startx) thus the driver can't > acquire the agp device. More precisely, calling > DRM(agp_acquire_ioctl)(struct inode *inode, struct file *filp, > unsigned int cmd, unsigned long arg) (in > drm_agp_tmp.h) returns an error, since dev->agp->acquired is still 1 > (verified with some additional debug output). > I remember there was a bug which resulted in non-freeing the resources > if the X Server was terminated, but I thought this was fixed some month ago?
This may be regression caused by my patch, and could go some way in explaning what Martin is experiencing. I'm going to see if I can reproduce the problem and solve it. Thanks for the feedback, Jos� Fonseca ------------------------------------------------------- This SF.Net email is sponsored by: INetU Attention Web Developers & Consultants: Become An INetU Hosting Partner. Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission! INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
