Date: Mon, 2 Feb 2009 13:33:08 +0100 From: =?UTF-8?Q?Nikola_Kne=C5=BEevi=C4=87?= <laladelausanne@gmail.com> To: freebsd-hackers@freebsd.org Subject: Re: blockable sleep lock (sleep mutex) 16 Message-ID: <32679C0A-28C1-4D7A-950C-580787F3971D@gmail.com> In-Reply-To: <02026848-7F83-405C-B4F3-EDD8B47DA294@gmail.com> References: <02026848-7F83-405C-B4F3-EDD8B47DA294@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 30 Jan 2009, at 18:11 , Nikola Kne=C5=BEevi=C4=87 wrote: > This is the message buffer: > Unread portion of the kernel message buffer: > panic: blockable sleep lock (sleep mutex) 16 @ /usr/src/sys/vm/=20 > uma_core.c:1834 > Any hints where I should search for the cause? Ok, I solved this problem. I had a critical_enter/exit surrounding =20 code which was calling a lot of mallocs. Now, I'm getting another =20 message, which doesn't make any sense: ---8<--- --- trap 0, rip =3D 0, rsp =3D 0xffffffff87834d30, rbp =3D 0 --- uma_zalloc_arg: zone "256" with the following non-sleepable locks held: exclusive sleep mutex click_instance r =3D 0 (0xffffff00051b4540) locked = =20 @ sched.cc:441 --->8--- It says "non-sleepable locks", yet it classifies click_instance as =20 sleep mutex. I think witness code should emit messages which are more =20= clear. Cheers, Nikola=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?32679C0A-28C1-4D7A-950C-580787F3971D>