From owner-freebsd-current@FreeBSD.ORG Wed Aug 11 11:26:13 2004 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 A6C8916A4CE; Wed, 11 Aug 2004 11:26:13 +0000 (GMT) Received: from lakermmtao02.cox.net (lakermmtao02.cox.net [68.230.240.37]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1650843D1D; Wed, 11 Aug 2004 11:26:13 +0000 (GMT) (envelope-from conrads@cox.net) Received: from dolphin.local.net ([68.11.71.51]) by lakermmtao02.cox.net (InterMail vM.6.01.03.02.01 201-2131-111-104-103-20040709) with ESMTP id <20040811112612.WSOK1467.lakermmtao02.cox.net@dolphin.local.net>; Wed, 11 Aug 2004 07:26:12 -0400 Received: from dolphin.local.net (localhost.local.net [127.0.0.1]) by dolphin.local.net (8.13.1/8.13.1) with ESMTP id i7BBQBee005108; Wed, 11 Aug 2004 06:26:11 -0500 (CDT) (envelope-from conrads@dolphin.local.net) Received: (from conrads@localhost) by dolphin.local.net (8.13.1/8.13.1/Submit) id i7BBQ6Od005107; Wed, 11 Aug 2004 06:26:06 -0500 (CDT) (envelope-from conrads) Message-ID: X-Mailer: XFMail 1.5.5 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <49521.66.13.175.242.1092194974.squirrel@[66.13.175.242]> Date: Wed, 11 Aug 2004 06:26:06 -0500 (CDT) Organization: A Rag-Tag Band of Drug-Crazed Hippies From: "Conrad J. Sabatier" To: Rusty Nejdl cc: Don Lewis cc: freebsd-current@FreeBSD.org cc: dnelson@allantgroup.com Subject: Re: Is anything being done re: the pcm timeout issue? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: conrads@cox.net List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Aug 2004 11:26:13 -0000 On 11-Aug-2004 Rusty Nejdl wrote: > >>> >>> And I have seen that these will eventually stop working one by one >>> until I have none left. lsof and fstat don't show any programs >>> using >>> them, but nonetheless, programms like xmms and gaim can't use them >>> anymore. > > Well, try as much as I could, I haven't been able to duplicate this > tonight. I've got 4 vchans setup and I was running madplay > continuously on 4 channels for 4 hours and it worked the whole time. > >> >> The vchan code is fairly broken. I was hoping to have to some time >> to >> work on this (and other problems in the top half of the sound code) >> before >> 5.3, but it looks like the clock has just about run out. > > I'm not seeing the locked channels yet, but that doesn't mean that > they aren't there. I do appreciate your looking into this matter. So far, with my latest kernel, I haven't experienced the problem yet, either. Which doesn't necessarily mean, of course, that I still won't. :-) There's definitely the possibility that it's not really a sound issue at all, but just the drivers' sensitivity to something else going on in the kernel. Unfortunately, my knowledge/understanding of the low-level operations of the kernel is practically nil, so I really can't comment on that in any sort of intelligent or useful fashion. :-) I'll keep my fingers crossed here; maybe the problem will just "go away" (or already has). :-) I'll keep you posted if I still see any problems. Thanks again. -- Conrad J. Sabatier -- "In Unix veritas"