From owner-freebsd-amd64@FreeBSD.ORG Fri Jun 23 17:05:30 2006 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AF68316A492 for ; Fri, 23 Jun 2006 17:05:30 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by mx1.FreeBSD.org (Postfix) with ESMTP id 976FD43D5E for ; Fri, 23 Jun 2006 17:05:29 +0000 (GMT) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost.apl.washington.edu [127.0.0.1]) by troutmask.apl.washington.edu (8.13.7/8.13.7) with ESMTP id k5NH4N5W016491; Fri, 23 Jun 2006 10:04:24 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.13.7/8.13.7/Submit) id k5NH4NUa016490; Fri, 23 Jun 2006 10:04:23 -0700 (PDT) (envelope-from sgk) Date: Fri, 23 Jun 2006 10:04:23 -0700 From: Steve Kargl To: "Matthew D. Fuller" Message-ID: <20060623170423.GA92531@troutmask.apl.washington.edu> References: <200606231107.k5NB7Ms1004172@guild.plethora.net> <20060623165833.GK83482@over-yonder.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060623165833.GK83482@over-yonder.net> User-Agent: Mutt/1.4.2.1i Cc: freebsd-amd64@freebsd.org Subject: Re: SMP system not running SMP X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Jun 2006 17:05:30 -0000 On Fri, Jun 23, 2006 at 11:58:33AM -0500, Matthew D. Fuller wrote: > On Fri, Jun 23, 2006 at 06:07:22AM -0500 I heard the voice of > Peter Seebach, and lo! it spake thus: > > > > There are two possible paths to fixing this: One is to make SMP > > work without ACPI. > > One thing to note is that in the dmesg you posted, there's no "ioapic" > probed. That suggests it's not really finding the APIC, which would > be why SMP is failing. It'd be getting that from ACPI normally, but > AIUI (I'm way out of my depth here) it could find them in other ways. > I vaguely recall somebody (John Baldwin, maybe?) doing something in > this area of ways of enumerating CPU's/APIC's in the last 6 > monthsish... > I think you may be recalling the atpic device. device atpic # Optional legacy pic support -- Steve