From owner-freebsd-current Tue Jan 5 09:50:54 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA12305 for freebsd-current-outgoing; Tue, 5 Jan 1999 09:50:54 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bright.fx.genx.net (bright.fx.genx.net [206.64.4.154]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA12300 for ; Tue, 5 Jan 1999 09:50:51 -0800 (PST) (envelope-from bright@hotjobs.com) Received: from localhost (bright@localhost) by bright.fx.genx.net (8.9.1/8.9.1) with ESMTP id MAA49877; Tue, 5 Jan 1999 12:54:37 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: bright.fx.genx.net: bright owned process doing -bs Date: Tue, 5 Jan 1999 12:54:37 -0500 (EST) From: Alfred Perlstein X-Sender: bright@bright.fx.genx.net To: steven cc: current@FreeBSD.ORG Subject: Re: So we're stuck with using timidity now? 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 On Tue, 5 Jan 1999, steven wrote: > > Just curious.. what the status on the vm/oss "bug"? > > I see posts here saying its fixed (from early dec98) others > saying its still fubar'd. Posts on Usenet are contradictory > also. > > I got OSS's latest version ossfreebsd391i-30x > I'm using Current from Dec 27 1998 which has their patch > > running anything in X with OSS just kills the whole system, > Quake, Fxtv, X11Amp, mpg123.. you name it Not to knock such an inexpensive and interesting product ( i used it on 2.2.x a while back ) but how come my drivers don't panic my system? (i'm using Luigi's) the problem from what i understand is that OSS dynamically requests large regeons of contiguous memory, after X is running memory is most likely quite fragmented and the request hangs wedging the system. way back when (a year ago) it seemed to only try to alloc the a buffer when the module was loaded, however it may have changed, either that or you are trying to load it after memory is way too fragmented. also having contig_malloc() a bit more robust would be a nice feature... there were some fixes to help contig_malloc specifically with OSS. -Alfred > > > Steven S. > 403forbidden.net > > "My Sister opened a computer store in Hawaii. > She sells C shells down by the seashore." > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message