Michel Dänzer wrote:
It's really just the lock. The locking process is two stage, with a cmpxcg in userspace which can handle the trivial case (if the same context wants to get a lock and it was the last context to hold it) without kernel intervention. If that fails, the process has to do an ioctl to get the lock. This is where this message comes from -- maybe saying that '6' already has the lock it is asking for.On Son, 2002-11-24 at 18:39, Andreas Stenglein wrote:Nov 23 20:18:13 buche kernel: [drm:radeon_irq_emit] *ERROR* radeon_irq_emit called without lock held
Nov 23 20:18:13 buche kernel: [drm:radeon_lock_take] *ERROR* 6 holds heavyweight lock
A friend of mine reported something like this (haven't seen it myself). For him, killing the DRI client(s) resumes normal operation. Can you confirm that? If so, that's not an actual lockup. I still can't really imagine what a 'heavyweight lock' is, can one of the traditional developers explain?
Keith
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel
