The following reply was made to PR kern/36003; it has been noted by GNATS.

From: "Andrew Doran" <ad@netbsd.org>
To: gnats-bugs@NetBSD.org
Cc: 
Subject: Re: kern/36003: "Mutex error: mutex_vector_enter: locking against 
     myself" on evbarm/IQ80321
Date: Wed, 14 Mar 2007 14:37:54 -0000 (GMT)

 > 	Mutex error: mutex_vector_enter: locking against myself
 >
 > 	lock address : 0x00000000c0533e8c
 > 	current cpu  :                  0
 > 	current lwp  : 0x00000000c26559c0
 > 	owner field  : 0x0000000000010c00 wait/spin:                0/1
 
 [...]
 
 > 	netbsd:turnstile_lookup+0xc
 > 		scp=0xc0353e4c rlv=0xc033f838 (netbsd:mutex_vector_exit+0x110)
 > 		rsp=0xc2ed0e00 rfp=0xc2ed0e14
 > 		r5=0x00000000 r4=0xc2ee6f00
 
 I guess this is a DIAGNOSTIC kernel? The sched_mutex has been locked and
 something has failed to release it. There's no MI reason for that to occur
 that I know of. It looks like there is a gxemul target for this machine,
 so I'll give it a go when I get a chance.
 
 Andrew