From owner-freebsd-current@FreeBSD.ORG Sun Sep 26 23:12:01 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 3795116A4CE for ; Sun, 26 Sep 2004 23:12:01 +0000 (GMT) Received: from slipgate.org (S0106000acd019ad0.du.shawcable.net [24.109.1.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0783943D2F for ; Sun, 26 Sep 2004 23:11:59 +0000 (GMT) (envelope-from ryan@slipgate.org) Received: from ryan.lan (gate.lan [192.168.1.1]) by slipgate.org (8.12.11/8.12.11) with ESMTP id i8QNBY8N005860 for ; Sun, 26 Sep 2004 16:11:34 -0700 (PDT) Received: from ryan.lan (localhost [127.0.0.1]) by ryan.lan (8.13.1/8.13.1) with ESMTP id i8QNC7ZV001551 for ; Sun, 26 Sep 2004 16:12:07 -0700 (PDT) (envelope-from ryan@slipgate.org) Received: (from ryan@localhost) by ryan.lan (8.13.1/8.13.1/Submit) id i8QNC6Lq001550 for freebsd-current@freebsd.org; Sun, 26 Sep 2004 16:12:06 -0700 (PDT) (envelope-from ryan@slipgate.org) X-Authentication-Warning: ryan.lan: ryan set sender to ryan@slipgate.org using -f Date: Sun, 26 Sep 2004 16:12:06 -0700 From: Ryan Freeman To: FreeBSD Mailing List Message-ID: <20040926231206.GA1508@slipgate.org> References: <20040924071520.GA44388@slipgate.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i Subject: Re: Sound performance problems in FreeBSD 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: Sun, 26 Sep 2004 23:12:01 -0000 > On Fri, 24 Sep 2004 00:15:20 -0700, Ryan Freeman wrote: > > >hello, sorry to drag up a slightly outdated topic, but i just installed > >5.3beta5 > >and i'm having the same issue. the last time i used freebsd was back in > >march at... --snip-- > >>An easy way to reproduce these > >>skips is to run `while true; do sysctl vm.vmtotal; done`, while > >>playing an mp3. > > i'm wondering if the reason that the problem doesn't occur for the first few hours is that when you first boot up not much memory has been used and then set inactive and such. like right now, i just upgraded to 5.3beta6, and since i booted up i have 484mb free. when the problem was last occuring i had almost no memory free, most of it was set to cached or inactive. ideas? comments? - ryan