From owner-freebsd-current Sun Jan 14 13:32:25 2001 Delivered-To: freebsd-current@freebsd.org Received: from thelab.hub.org (SHW2-220.accesscable.net [24.71.145.220]) by hub.freebsd.org (Postfix) with ESMTP id 27C0A37B402 for ; Sun, 14 Jan 2001 13:32:04 -0800 (PST) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.11.1/8.11.1) with ESMTP id f0ELUJN20585; Sun, 14 Jan 2001 17:30:19 -0400 (AST) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Sun, 14 Jan 2001 17:30:19 -0400 (AST) From: The Hermit Hacker To: Cameron Grant Cc: Michael Wells , Subject: Re: Soundblaster 64 PCI In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG yup, just confirmed ... it does it with splay as well ... On Sun, 14 Jan 2001, The Hermit Hacker wrote: > On Sun, 14 Jan 2001, Cameron Grant wrote: > > > > > If this is a known problem, I'll stop for now and watch out for fixes. > > > > If it's not the expected behaviour from the PCM driver though, can > > > > anyone advise? > > > > > > Okay, just checked and it appears tha htis is the same error that I'm > > > seeing on mine, as reported yesterday ... not sure if its known or not, > > > but its not "just you" ... > > > > are either of you using esound or xmms? if so, i know the cause of this and > > it will be fixed shortly, once my primary development box recovers from > > killing its cpu. > > > > if not, i'll try to reproduce this. > > for me, I tried using splay ... but, not sure how old my compile was, so > am just installing a new copy and will report back ... > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy Systems Administrator @ hub.org primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message