From owner-freebsd-current Wed Feb 12 23:56: 0 2003 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 A41C337B401 for ; Wed, 12 Feb 2003 23:55:58 -0800 (PST) Received: from zibbi.icomtek.csir.co.za (zibbi.icomtek.csir.co.za [146.64.24.58]) by mx1.FreeBSD.org (Postfix) with ESMTP id E595B43FD7 for ; Wed, 12 Feb 2003 23:55:56 -0800 (PST) (envelope-from jhay@zibbi.icomtek.csir.co.za) Received: from zibbi.icomtek.csir.co.za (localhost [IPv6:::1]) by zibbi.icomtek.csir.co.za (8.12.6/8.12.6) with ESMTP id h1D7tsbw027272 for ; Thu, 13 Feb 2003 09:55:55 +0200 (SAST) (envelope-from jhay@zibbi.icomtek.csir.co.za) Received: (from jhay@localhost) by zibbi.icomtek.csir.co.za (8.12.6/8.12.6/Submit) id h1D7tsZR027271 for current@FreeBSD.ORG; Thu, 13 Feb 2003 09:55:54 +0200 (SAST) Date: Thu, 13 Feb 2003 09:55:54 +0200 From: John Hay To: current@FreeBSD.ORG Subject: Re: dsp "device busy" (me too) vchans weirdness Message-ID: <20030213075554.GA26761@zibbi.icomtek.csir.co.za> References: <1045061169.91280.17.camel@owen1492.uf.corelab.com> <20030212183111.GA2342@zibbi.icomtek.csir.co.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030212183111.GA2342@zibbi.icomtek.csir.co.za> User-Agent: Mutt/1.4i 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 On Wed, Feb 12, 2003 at 08:31:11PM +0200, John Hay wrote: > On Wed, Feb 12, 2003 at 08:46:09AM -0600, Craig Boston wrote: > > I remember a couple of posts about this problem; but don't recall (and > > am unable to find in the archives) if there was ever any resolution. > > I have experienced the same thing. I have tried vchan sound on three > -current boxes and it works on all but the Dell. The Dell also have > the ICH2 sound while the other two have different sound chips. Maybe > it has something to do with the ICH driver or else I was just lucky > with the other machines. On the Dell have tried setting vchans > directly and maxautovchans, but neither did work for me. I did see > this on the console though: > > ###### > lock order reversal > 1st 0xc87d5b00 pcm0:virtual:0 (pcm channel) @ /usr/src/sys/dev/sound/pcm/sound.c:191 > 2nd 0xc5d99a80 pcm0 (sound cdev) @ /usr/src/sys/dev/sound/pcm/sound.c:163 > ###### > > Just switching vchans off on the Dell made the sound work again. > Looks like I have to take that back. I just tried a brand new -CURRENT kernel and vchans are now working. I have only tried it by setting hw.snd.maxautovchans. It does produce a lot of "could sleep with" messages though: ################## ../../../vm/uma_core.c:1330: could sleep with "pcm0" locked from /usr/src/sys/dev/sound/pcm/sound.c:163 ../../../vm/uma_core.c:1330: could sleep with "pcm0" locked from /usr/src/sys/dev/sound/pcm/sound.c:163 ../../../vm/uma_core.c:1330: could sleep with "pcm0" locked from /usr/src/sys/dev/sound/pcm/sound.c:163 ../../../vm/uma_core.c:1330: could sleep with "pcm0" locked from /usr/src/sys/dev/sound/pcm/sound.c:378 ../../../vm/uma_core.c:1330: could sleep with "pcm0" locked from /usr/src/sys/dev/sound/pcm/sound.c:378 ../../../vm/uma_core.c:1330: could sleep with "pcm0" locked from /usr/src/sys/dev/sound/pcm/sound.c:378 ../../../vm/uma_core.c:1330: could sleep with "pcm0" locked from /usr/src/sys/dev/sound/pcm/sound.c:378 ../../../vm/uma_core.c:1330: could sleep with "pcm0" locked from /usr/src/sys/dev/sound/pcm/sound.c:378 ../../../vm/uma_core.c:1330: could sleep with "pcm0" locked from /usr/src/sys/dev/sound/pcm/sound.c:434 ../../../vm/uma_core.c:1330: could sleep with "pcm0" locked from /usr/src/sys/dev/sound/pcm/sound.c:434 ../../../vm/uma_core.c:1330: could sleep with "pcm0" locked from /usr/src/sys/dev/sound/pcm/sound.c:434 ################### John -- John Hay -- John.Hay@icomtek.csir.co.za / jhay@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message