On Thu, Dec 11, 2008 at 08:13:12PM +1000, Dave Airlie wrote: > On Thu, Dec 11, 2008 at 4:56 PM, garrone <[EMAIL PROTECTED]> wrote: > > > > Hi, > > I am getting freezes in direct rendering. Sometimes glxgears works, > > but eventually the freeze occurs at program exit, or upon xrandr operation. > > > > The freeze occurs > > because the kernel function drm_lock continually returns -EINTR > > because the hardware lock variable master->lock.hw_lock is NULL, > > and the function drmIoctl (in user space drm) continually invokes the ioctl > > while it returns -EINTR. > > I need to look at this some more, but I can't figure out how the shm > can find a matching map > if there was a map created already, it should have gotten a lock > allocated in it. > > I'll try and take a look asap. > > Dave. >
Thanks. The condition happens after the drm devices are closed and reopened. The map that is still there corresponds to the one generating the mtrr message. Now that I know that the maps are supposed to be cleared in that situation, I can find out why this one isn't. Peter. _______________________________________________ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg