On Sat, 16 Mar 2002 10:22:22 +0100,
  Poul-Henning Kamp <[EMAIL PROTECTED]> said:

Poul-Henning> acquiring duplicate lock of same type: "thrd_sleep"
Poul-Henning>  1st @ ../../../vm/vm_map.c:2288
Poul-Henning>  2nd @ ../../../vm/vm_kern.c:172
Poul-Henning> _vm_map_lock(c038afb4,c02f8440,ac,c034a840,1) at _vm_map_lock+0x16
Poul-Henning> kmem_alloc(c038afb4,3000,c0e41a00,0,c02fa434) at kmem_alloc+0x41
Poul-Henning> _zget(c0e41a00,bfc00000,0,c0435cd0,c0281769) at _zget+0xfa
Poul-Henning> zalloc(c0e41a00,c034a840,1,c02f8630,a7) at zalloc+0x3b
Poul-Henning> vmspace_alloc(0,bfc00000,c035c940,c02f8630,8f0) at vmspace_alloc+0x2d
Poul-Henning> vmspace_fork(c035c940,cbb9ad24,c0331f84,cbb9ab00,c0331d60) at 
Poul-Henning> vm_forkproc(c0332080,cbb9ab00,cbb9ac00,20014) at vm_forkproc+0xc6

This seems due to naming all of the vm map locks as "thrd_sleep." The
locks of vm maps should have their own hierarachy. For instance, lock
the map of a process vm space first, then lock the kernel_map.


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Reply via email to