From owner-freebsd-current Wed Oct 2 0:54:54 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 985AA37B401 for ; Wed, 2 Oct 2002 00:54:53 -0700 (PDT) Received: from mail2.itxmarket.com (fw.itxmarket.com [213.11.40.109]) by mx1.FreeBSD.org (Postfix) with ESMTP id A410043E3B for ; Wed, 2 Oct 2002 00:54:47 -0700 (PDT) (envelope-from mich@freebsdcluster.net) Received: from freebsdcluster.net (mich2.itxmarket.com [192.168.2.26]) by mail2.itxmarket.com (Postfix) with ESMTP id 2095137C85; Wed, 2 Oct 2002 09:53:51 +0200 (CEST) Received: by freebsdcluster.net (Postfix, from userid 1000) id 799A93B9644; Wed, 2 Oct 2002 09:53:45 +0200 (CEST) Date: Wed, 2 Oct 2002 09:53:45 +0200 From: Michael Hostbaek To: Rasmus Skaarup Cc: freebsd-current@freebsd.org Subject: Re: could sleep with messages Message-ID: <20021002075345.GC17620@mich2.itxmarket.com> References: <20021002003038.J62700-100000@alfred.skaarup.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20021002003038.J62700-100000@alfred.skaarup.org> X-Operating-System: FreeBSD 4.6-STABLE i386 X-PGP-Key: http://www.freebsdcluster.org/~mich/ User-Agent: Mutt/1.5.1i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Rasmus Skaarup (mfbsd) writes: > > > I've been getting the following messages for quite some time, during > boot and when using the pcm device: > > ... > /usr/src/sys/vm/uma_core.c:1307: could sleep with "pcm0:play:0" locked [...] > ... > > Is anyone interesting in getting more details? > This is a well known problem. It is basically a diagnostic message telling you that there's a deficiency in the pcm driver. If you want to fix it permanently I suggest that you go and have a look at dev/sound/pcm/sound.c:134 and look for a way of invoking UMA without holding the lock. A possible workaround, is to try and disable INVARIANTS and WITNESS in the your kernel conf. and hope it won't turn into a real problem (fx. panic.) -- Best Regards, Michael Landin Hostbaek FreeBSDCluster.org - an International Community */ PGP-key available upon request /* To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message