From owner-freebsd-current@FreeBSD.ORG Mon Apr 28 23:01:53 2003 Return-Path: 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 6C69137B401 for ; Mon, 28 Apr 2003 23:01:53 -0700 (PDT) Received: from MAILSERVER.ofw.fi (ns.ofw.fi [194.111.144.200]) by mx1.FreeBSD.org (Postfix) with ESMTP id 972BD43FBD for ; Mon, 28 Apr 2003 23:01:51 -0700 (PDT) (envelope-from dan.naumov@ofw.fi) Received: from [172.16.161.81] by MAILSERVER.ofw.fi (NTMail 7.00.0022/NT1439.00.90501b21) with ESMTP id ksikjaaa for freebsd-current@freebsd.org; Tue, 29 Apr 2003 09:01:31 +0300 Date: Tue, 29 Apr 2003 09:05:37 +0300 From: Dan Naumov To: freebsd-current@freebsd.org Message-Id: <20030429090537.6bf751d1.dan.naumov@ofw.fi> In-Reply-To: <200304271730.53960.cbiffle@safety.net> References: <200304271730.53960.cbiffle@safety.net> X-Mailer: Sylpheed version 0.8.11 (GTK+ 1.2.10; i386-portbld-freebsd5.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: vchans seem to affect /dev/dsp* availability X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Apr 2003 06:01:53 -0000 On Sun, 27 Apr 2003 17:30:53 -0700 "Cliff L. Biffle" wrote: > When I have vchans enabled, every few attempts at opening /dev/dsp* > result in 'Operation not supported by device.' Also, while they're > enabled, some programs (most reproduceably artsd) peg my CPU after > outputting sound data in certain situations. > > Disabling vchans fixes the problem. The problem's a little ephemeral, > so I'm still collecting hard data, but it seems I have to go all the > way to properly disable them, e.g. > kldload snd_pcm > sysctl hw.snd.maxautovchans=0 > kldload snd_ Here is a related PR initially submitted on July 17, 2002: http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/40711 I am experiencing this problem on a 5.0 box (as I've described in the follow-up to this PR). Disabling and then re-enabling vchans seems to work as a workaround, although sometimes I have to do it several times. Sincerely, -- Dan Naumov