From owner-freebsd-current@FreeBSD.ORG Mon Aug 9 18:40:14 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 98E0E16A4CF for ; Mon, 9 Aug 2004 18:40:14 +0000 (GMT) Received: from lakermmtao08.cox.net (lakermmtao08.cox.net [68.230.240.31]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3080943D41 for ; Mon, 9 Aug 2004 18:40:14 +0000 (GMT) (envelope-from conrads@cox.net) Received: from dolphin.local.net ([68.11.71.51]) by lakermmtao08.cox.net (InterMail vM.6.01.03.02.01 201-2131-111-104-103-20040709) with ESMTP id <20040809184013.LIGQ2852.lakermmtao08.cox.net@dolphin.local.net>; Mon, 9 Aug 2004 14:40:13 -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 i79IeDR8096319; Mon, 9 Aug 2004 13:40:13 -0500 (CDT) (envelope-from conrads@dolphin.local.net) Received: (from conrads@localhost) by dolphin.local.net (8.13.1/8.13.1/Submit) id i79Ie7AD096310; Mon, 9 Aug 2004 13:40:07 -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: <20040809182126.GC4216@dan.emsphone.com> Date: Mon, 09 Aug 2004 13:40:07 -0500 (CDT) Organization: A Rag-Tag Band of Drug-Crazed Hippies From: "Conrad J. Sabatier" To: Dan Nelson cc: freebsd-current@freebsd.org 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: Mon, 09 Aug 2004 18:40:14 -0000 On 09-Aug-2004 Dan Nelson wrote: > In the last episode (Aug 09), Conrad J. Sabatier said: >> Sound has been broken now for I don't know how long. My machine's >> pcm device can be counted on to break, sometimes after only a very >> short period of usage after a reboot (which is the only way to get >> sound working again). > > Sound works fine for me on my Dell laptop (mss driver). I do get a > mutex-related panic on my desktop (sb16 driver), but haven't sent in > the stack trace to anyone yet. My problems are occurring on an amd64 box (Athlon 64) with the nVidia nForce3 chipset (snd_ich driver). Sounds works fine for a while, then suddenly I get a pcm play timeout, and game over. Have to reboot to get sound to work again. Others have reported similar problems, but I've seen no followups indicating anything is being done about it. >> This is getting extremely frustrating. Is anyone working on this at >> all? -- Conrad J. Sabatier -- "In Unix veritas"