From owner-freebsd-hackers@FreeBSD.ORG Mon Feb 2 12:33:12 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5BD63106566C for ; Mon, 2 Feb 2009 12:33:12 +0000 (UTC) (envelope-from laladelausanne@gmail.com) Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.156]) by mx1.freebsd.org (Postfix) with ESMTP id D7A328FC17 for ; Mon, 2 Feb 2009 12:33:11 +0000 (UTC) (envelope-from laladelausanne@gmail.com) Received: by fg-out-1718.google.com with SMTP id l26so492582fgb.35 for ; Mon, 02 Feb 2009 04:33:10 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:from:to :in-reply-to:content-type:content-transfer-encoding:mime-version :subject:date:references:x-mailer; bh=7GQ/ebVCtpp/eOQXUqOGahYdn3yW1uHkMLjiv8jHvsM=; b=sacUEWJM9NB2RV53uWQQLrz9+dPigLXmbjQXSrF+0ZlNzeZYm/KhL9ABkRPc9zIWlS 3X4VidAGUX20was3APf5z1nIW/L/R/Rcg1+S/Tm4gkEbheetMVVUeXK6qaolc4vAWIYk uYXmTb8cTyW4A2g+SOf0WiyZL+jVJ10HR4UKE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:from:to:in-reply-to:content-type :content-transfer-encoding:mime-version:subject:date:references :x-mailer; b=XTdDeJUVn6Y3ePY8G3FKUyLH6yvSbWcprwwAQePV0CDIGaEwTgYz/NoL/KRaVYguVk gLAs5JR6Qk2gdpxMtur+RLYBnOkA6zwYIea6EDCdkyDUN9VtdQeDdYwHj1u0vhr7soox yGcTCcOeLE6sIsp5SiEkBVl45VDNwq95nATaQ= Received: by 10.86.95.8 with SMTP id s8mr1825496fgb.16.1233577990561; Mon, 02 Feb 2009 04:33:10 -0800 (PST) Received: from nslpc5.epfl.ch (nslpc5.epfl.ch [128.178.149.20]) by mx.google.com with ESMTPS id l19sm439987fgb.27.2009.02.02.04.33.09 (version=TLSv1/SSLv3 cipher=RC4-MD5); Mon, 02 Feb 2009 04:33:09 -0800 (PST) Message-Id: <32679C0A-28C1-4D7A-950C-580787F3971D@gmail.com> From: =?UTF-8?Q?Nikola_Kne=C5=BEevi=C4=87?= To: freebsd-hackers@freebsd.org In-Reply-To: <02026848-7F83-405C-B4F3-EDD8B47DA294@gmail.com> Content-Type: text/plain; charset=UTF-8; format=flowed; delsp=yes Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Apple Message framework v930.3) Date: Mon, 2 Feb 2009 13:33:08 +0100 References: <02026848-7F83-405C-B4F3-EDD8B47DA294@gmail.com> X-Mailer: Apple Mail (2.930.3) Subject: Re: blockable sleep lock (sleep mutex) 16 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Feb 2009 12:33:12 -0000 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=