From owner-freebsd-current@FreeBSD.ORG Sat May 10 00:26:32 2003 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 8EB0F37B401 for ; Sat, 10 May 2003 00:26:32 -0700 (PDT) Received: from gw.catspoiler.org (217-ip-163.nccn.net [209.79.217.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id E90BD43F93 for ; Sat, 10 May 2003 00:26:31 -0700 (PDT) (envelope-from truckman@FreeBSD.org) Received: from FreeBSD.org (mousie.catspoiler.org [192.168.101.2]) by gw.catspoiler.org (8.12.9/8.12.9) with ESMTP id h4A7QMM7039660; Sat, 10 May 2003 00:26:27 -0700 (PDT) (envelope-from truckman@FreeBSD.org) Message-Id: <200305100726.h4A7QMM7039660@gw.catspoiler.org> Date: Sat, 10 May 2003 00:26:22 -0700 (PDT) From: Don Lewis To: tlambert2@mindspring.com In-Reply-To: <3EBC8E40.69A472BC@mindspring.com> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii cc: current@FreeBSD.org Subject: Re: data corruption with current (maybe sis chipset related?) 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: Sat, 10 May 2003 07:26:32 -0000 On 9 May, Terry Lambert wrote: > Chris BeHanna wrote: >> And, why aren't Bosko's patches in the tree? > > I don't know. I do know that they increased the minimum memory > requirements by 4M (part of Bosko's approach to a fix requires > linking the kernel with a base address aligned on a 4M boundary). How hard would it be to make this a compile time option? Small memory machines are unlikely to want to use 4 MB pages anyway. In other words a configuration option that would disable 4 MB pages and put the kernel at its current location when set one way, and would enable 4MB pages and relocate the kernel on a 4 MB boundary when set the other way. I really dislike our default configuration of a little bit more speed at the expense of data integrity. If that's what I really wanted, I could probably get even more speed by overclocking.