From owner-freebsd-current Fri Nov 24 18:35:20 2000 Delivered-To: freebsd-current@freebsd.org Received: from mta6.snfc21.pbi.net (mta6.snfc21.pbi.net [206.13.28.240]) by hub.freebsd.org (Postfix) with ESMTP id CA18937B479 for ; Fri, 24 Nov 2000 18:35:17 -0800 (PST) Received: from zippy.pacbell.net ([207.214.149.167]) by mta6.snfc21.pbi.net (Sun Internet Mail Server sims.3.5.2000.01.05.12.18.p9) with ESMTP id <0G4K00M5B73WA5@mta6.snfc21.pbi.net> for current@freebsd.org; Fri, 24 Nov 2000 18:33:33 -0800 (PST) Received: by zippy.pacbell.net (Postfix, from userid 1000) id 9C54717F9; Fri, 24 Nov 2000 18:33:54 -0800 (PST) Date: Fri, 24 Nov 2000 18:33:54 -0800 From: Alex Zepeda Subject: Re: -current scheduler strangeness In-reply-to: <20001120154327.C16019@petra.hos.u-szeged.hu>; from sziszi@petra.hos.u-szeged.hu on Mon, Nov 20, 2000 at 03:43:27PM +0100 To: current@freebsd.org Message-id: <20001124183354.B6896@zippy.pacbell.net> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-disposition: inline User-Agent: Mutt/1.2.5i References: <20001120142326.A97732@thing.orbitel.bg> <20001120142543.B97732@thing.orbitel.bg> <3A191B13.60A7C199@FreeBSD.org> <20001120152154.A644@thing.orbitel.bg> <3A1928AC.E627E639@elischer.org> <20001120154327.C16019@petra.hos.u-szeged.hu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Nov 20, 2000 at 03:43:27PM +0100, Szilveszter Adam wrote: > The messages did not start with SMPNG but got a *lot* more frequent in the > last couple of weeks, making listening to mp3-s a real annoyance during any > more serious system activity. (Earlier, ie in the early fall and in the > summer) these messages were almost never seen while in console mode, but > only with X and RealPlayer messing things up. I'm getting this too, in fact even pcmplay (about as minimalistic as you can get) skips a lot and often throws hwptr went backwards. Oh yeah, I'm using an AWE64 PnP as well. - alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message