From owner-freebsd-current Mon May 1 10:50:24 2000 Delivered-To: freebsd-current@freebsd.org Received: from ucsu.Colorado.EDU (ucsu.Colorado.EDU [128.138.129.83]) by hub.freebsd.org (Postfix) with ESMTP id BC0CE37BCD1 for ; Mon, 1 May 2000 10:50:20 -0700 (PDT) (envelope-from vinson@ucsu.Colorado.EDU) Received: from localhost (vinson@localhost) by ucsu.Colorado.EDU (8.9.3/8.9.3/ITS-5.0/standard) with SMTP id LAA11807 for ; Mon, 1 May 2000 11:50:18 -0600 (MDT) Date: Mon, 1 May 2000 11:50:18 -0600 (MDT) From: VINSON WAYNE HOWARD To: "current@FreeBSD.ORG" Subject: Re: high CPU usage by xmms In-Reply-To: <20000501183617.A91188@shadowmere.student.utwente.nl> 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 Ok, more in the sound department: A current src/sys/dev/sound with a src/sys/dev/sound/pcm/dsp.c from the 22nd does not exhibit the high load problem. Moving dsp.c to the 24th causes the problem to re-appear. Thus, I'm prety convinced tha the big commit on the 23rd to dsp.c is the cause of at least my woes. However, I had major problems is onther areas with running dsp.c out of sync with the rest of the sound dir, so I RERALLY DON'T RECOMEND IT(not that you may care what I think). The workaround that has worked for me on three machines is to revert ALL of sys/dev/sound back to the 20th. If I get really bored in a couple of weeks, I may try to hammer out a patch, but I've got no familiarity with the code, so someone who understands it, or can do it sooner, might want to take a look. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message