Am Montag, 25. November 2002 10:39 schrieb Keith Whitwell: > Michel Dänzer wrote: > > 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 had such messages (trunk and r200 branch) but they are gone for some weeks, now. > > I still can't really imagine what a 'heavyweight lock' is, can one of > > the traditional developers explain? > > 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. Below are lastet error messages before lockup with r200 on mesa-4-1. Kernel is 2.5.47-mm1 radeon.o show 1.6.0 (backup path, not latest DRI stuff). Nov 23 21:59:21 SunWave1 kernel: [drm:radeon_cp_cmdbuf] *ERROR* bad cmd_type 0 at 080516ec Nov 23 22:06:24 SunWave1 kernel: [drm:radeon_cp_cmdbuf] *ERROR* bad cmd_type 0 at 081025ac Nov 24 02:57:46 SunWave1 kernel: [drm:radeon_cp_cmdbuf] *ERROR* bad cmd_type 0 at 08055880 -Dieter ------------------------------------------------------- This SF.net email is sponsored by: Get the new Palm Tungsten T handheld. Power & Color in a compact size! http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0002en _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
