From owner-freebsd-current Thu Aug 22 20:31:10 2002 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 1A76337B401 for ; Thu, 22 Aug 2002 20:31:08 -0700 (PDT) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id DF8D743E70 for ; Thu, 22 Aug 2002 20:31:07 -0700 (PDT) (envelope-from bright@elvis.mu.org) Received: by elvis.mu.org (Postfix, from userid 1192) id BB3FCAE25C; Thu, 22 Aug 2002 20:31:07 -0700 (PDT) Date: Thu, 22 Aug 2002 20:31:07 -0700 From: Alfred Perlstein To: current@freebsd.org Subject: Re: -current data corruption Message-ID: <20020823033107.GX75574@elvis.mu.org> References: <20020820043258.GI75574@elvis.mu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020820043258.GI75574@elvis.mu.org> User-Agent: Mutt/1.3.27i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG * Alfred Perlstein [020819 21:32] wrote: > If anyone is interested both David O'Brien and I are experiencing > what looks like data corruption under -current. FYI, a kernel compiled with Terry's suggestions (DISABLE_PSE, DISABLE_PG_G) makes the problem appear to go away. The "vim" port seems to compile without issues now. -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message