From owner-freebsd-smp Mon Sep 2 12:21:37 1996 Return-Path: owner-smp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA08095 for smp-outgoing; Mon, 2 Sep 1996 12:21:37 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id MAA08090 for ; Mon, 2 Sep 1996 12:21:33 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id MAA02683; Mon, 2 Sep 1996 12:20:42 -0700 From: Terry Lambert Message-Id: <199609021920.MAA02683@phaeton.artisoft.com> Subject: Re: SMP on Intel MG15 To: smp@csn.net (Steve Passe) Date: Mon, 2 Sep 1996 12:20:41 -0700 (MST) Cc: freebsd-smp@FreeBSD.ORG, rv@groa.uct.ac.za, erich@uruk.org In-Reply-To: <199608312143.PAA28776@clem.systemsix.com> from "Steve Passe" at Aug 31, 96 03:43:40 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-smp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Russel and I are trying to get FreeBSD SMP working on the Intel XXPRESS > board. We are past hte 2nd CPU ID = 2 problem. It appears that > the apic_startup routine never (correctly) launches the 2nd CPU. looking > at the MP spec and Intel pent. manuals it appears that the INIT/Reset > IPI expects that a "warm start vector" will exist for starting the > 2nd CPU, but the current code seems to ignore this. See MP spec B.4.1 > for details. > > Is the purpose of this INIT/Reset IPI just to get the 2nd CPU to a known > state, ie NOT to actually start it processing the bootMP code? > > Should not the code setup the BIOS warmstart vector to point @ > a "HLT" instruction b4 using the INIT IPI? B.4.1 specifically applies only to the 82489DX APIC. Is this a 486 MP box you are trying to get running? I think it's more likely that the problem is the system default state doesn't match one of the allowable configurations, and is maybe using a defaul configuration that we aren't handling properly. See chapter 5 of the spec, "Default Configurations". I think it's unlikely that the B.4.1 startup is your problem. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.