From owner-freebsd-hackers@FreeBSD.ORG Fri Apr 11 00:21:04 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6980F37B401 for ; Fri, 11 Apr 2003 00:21:04 -0700 (PDT) Received: from cirb503493.alcatel.com.au (c18609.belrs1.nsw.optusnet.com.au [210.49.80.204]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4075943FA3 for ; Fri, 11 Apr 2003 00:21:03 -0700 (PDT) (envelope-from peterjeremy@optushome.com.au) Received: from cirb503493.alcatel.com.au (localhost.alcatel.com.au [127.0.0.1])h3B7KZM2047368; Fri, 11 Apr 2003 17:20:36 +1000 (EST) (envelope-from jeremyp@cirb503493.alcatel.com.au) Received: (from jeremyp@localhost) by cirb503493.alcatel.com.au (8.12.8/8.12.8/Submit) id h3B7KOjb047367; Fri, 11 Apr 2003 17:20:24 +1000 (EST) Date: Fri, 11 Apr 2003 17:20:24 +1000 From: Peter Jeremy To: Terry Lambert Message-ID: <20030411072023.GA47320@cirb503493.alcatel.com.au> References: <200304101843.h3AIh4C65481@flip.jhs.private> <3E95EC17.7746B6D9@mindspring.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3E95EC17.7746B6D9@mindspring.com> User-Agent: Mutt/1.4.1i cc: freebsd-hackers@freebsd.org cc: jhs@berklix.com cc: Michael Elbel Subject: Re: Anyone seen 4.8-RELEASE running on a real 386 (not 486 586 etc) ? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Apr 2003 07:21:04 -0000 On Thu, Apr 10, 2003 at 03:11:35PM -0700, Terry Lambert wrote: >Julian Stacey wrote: >> freebsd-hackers@, >> Anyone seen 4.8-RELEASE running on a real 386 processor (not a 486, 586 etc) ? > >You must config your kernel with a CPU type of 386, so that it >will not atttempt to use 486-specific instructions, and so it >will emulate kernel write faulting, since the 386 does not do >this correctly. The kernel must have had I386_CPU because otherwise it would it would panic via panicifcpuunsupported() from cpu_startup(). Peter