From owner-freebsd-hackers@FreeBSD.ORG Thu Apr 10 12:46:39 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 9201337B404 for ; Thu, 10 Apr 2003 12:46:39 -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 B12C443FA3 for ; Thu, 10 Apr 2003 12:46:37 -0700 (PDT) (envelope-from peterjeremy@optushome.com.au) Received: from cirb503493.alcatel.com.au (localhost.alcatel.com.au [127.0.0.1])h3AJk8M2046826; Fri, 11 Apr 2003 05:46:08 +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 h3AJk3eA046825; Fri, 11 Apr 2003 05:46:03 +1000 (EST) Date: Fri, 11 Apr 2003 05:46:03 +1000 From: Peter Jeremy To: Julian Stacey Message-ID: <20030410194603.GB31752@cirb503493.alcatel.com.au> References: <200304101843.h3AIh4C65481@flip.jhs.private> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200304101843.h3AIh4C65481@flip.jhs.private> User-Agent: Mutt/1.4.1i cc: freebsd-hackers@freebsd.org 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: Thu, 10 Apr 2003 19:46:39 -0000 On Thu, Apr 10, 2003 at 08:43:04PM +0200, Julian Stacey wrote: >"SX 33" is written on chip, though dmesg reports "DX". AFAIK, the only difference is external bus width (SX is 16 bit, DX is 32 bit). It's only 486 where the SX means half the CPU doesn't work. >I recall 386 support was dropped in 5.0, but presume not dropped in 4.8, It's only dropped in 5.0 GENERIC - you should still be able to compile your own kernel with I386_CPU specified (and all other CPU options removed). >I compiled a kernel with ddb, Results copied by hand as no serial for >remote gdb.t present More useful would be a debug kernel and a crash dump. You can then use gdb on it and find the offending line of source code. > Fatal trap 1: priveleged instruction fault while in kernel mode > instruction pointer = 0x8:0xc02695a0 If you can't get a crash dump, do an 'nm -n' on the kernel and find the function containing this address. > stopped at 0xc02695a0: invlpg 0(%ecx) invlpg doesn't exist on i386 - you have to invalidate the entire TLB. It looks like someone forgot to protect an invlpg instruction. Peter