From owner-freebsd-current Thu Nov 26 11:42:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA27717 for freebsd-current-outgoing; Thu, 26 Nov 1998 11:42:22 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from lionking.org (blacker-99.caltech.edu [131.215.86.99]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA27710 for ; Thu, 26 Nov 1998 11:42:20 -0800 (PST) (envelope-from btman@ugcs.caltech.edu) Received: from localhost (btman@localhost) by lionking.org (8.9.1a/8.9.1) with ESMTP id LAA07390; Thu, 26 Nov 1998 11:42:08 -0800 (PST) X-Authentication-Warning: lionking.org: btman owned process doing -bs Date: Thu, 26 Nov 1998 11:42:08 -0800 (PST) From: Brian Tiemann X-Sender: btman@lionking.org To: Mike cc: Forrest Aldrich , freebsd-current@FreeBSD.ORG Subject: Re: Page fault response from OSS 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 Thu, 26 Nov 1998, Mike wrote: > How current are you? With a kernel cvsup'd on 25 Nov, I can use the oss > drivers just fine. For what it's worth, I've been able to use OSS successfully ever since kern/8632 was closed (with the patch by Bruce Evans). Another bug, i386/8673, relates to the remaining crashes, though I haven't run across them yet. But as people have been saying, this has only been addressed with patches so far; this all seems to mask a more serious general problem with the vm architecture, according to the OSS developers. Brian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message