From owner-freebsd-smp Sun Sep 22 14: 9:46 2002 Delivered-To: freebsd-smp@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5FEAC37B401 for ; Sun, 22 Sep 2002 14:09:45 -0700 (PDT) Received: from mailhub.cns.ksu.edu (grunt.ksu.ksu.edu [129.130.12.17]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0407143E65 for ; Sun, 22 Sep 2002 14:09:34 -0700 (PDT) (envelope-from beemern@ksu.edu) Received: from unix2.cc.ksu.edu (unix2.cc.ksu.edu [129.130.12.4]) by mailhub.cns.ksu.edu (8.9.1/8.9.1/mailhub+tar) with ESMTP id QAA19633; Sun, 22 Sep 2002 16:09:31 -0500 (CDT) Received: from localhost (beemern@localhost) by unix2.cc.ksu.edu (8.11.6+Sun/8.11.6) with ESMTP id g8ML9UF10266; Sun, 22 Sep 2002 16:09:31 -0500 (CDT) X-Authentication-Warning: unix2.cc.ksu.edu: beemern owned process doing -bs Date: Sun, 22 Sep 2002 16:09:30 -0500 (CDT) From: beemern X-X-Sender: To: Cc: Subject: Re: For those with P4 SMP problems.. Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Terry Lambert wrote: > The theory is that the BIOS has the corect information, but in the > wrong order, so the bios is fubar > So the two "solutions" boil down to correcting the physical/logical > mapping, or reloading the physical APIC ID register. yet the register DOES indeed have the correct,in-order info? tryin to do get some background in (smp) kernel booting/init, and ran across this at http://www.cheesecake.org/~sac/smp.html : "The base section consists of a set of entries that describe either processors, system busses, I/O APICs, I/O interrupt assignments, or local interrupt assignments." .. "In particular, you will want to note the APIC ID of each processor in the system, its version, and its type as well as the address of the system's I/O APIC." this matches (not surprisingly) exactly the array basetable_entry_types in mp_machdep.c so couldn't we simply re-init from the register? since apparantly things are getting confused in the intermediate data structures? (perhaps thru mptable_pass1 and/or mptable_pass2 ?) > them start the APs simultaneously, and a side effect of this is that > they don't care about order of start, they just care *that* they start but we've got only one AP, so simultaneous startup shouldnt be an issue? dont mean to be obtuse, just tryin to get a grip on whats happening and what is supposed to be right now i'm just doing a lot of rebooting with checkpoints in the code so i can get a handle on the boot process and what code is doing what etc etc thanks for all your help! nathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message