From owner-freebsd-questions@FreeBSD.ORG Fri Jul 4 15:31:28 2008 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7E9E21065721 for ; Fri, 4 Jul 2008 15:31:28 +0000 (UTC) (envelope-from rdmurray@bitdance.com) Received: from kimball.webabinitio.net (kimball.webabinitio.com [199.125.120.189]) by mx1.freebsd.org (Postfix) with ESMTP id 4E0408FC22 for ; Fri, 4 Jul 2008 15:31:28 +0000 (UTC) (envelope-from rdmurray@bitdance.com) Received: from localhost (kimball.webabinitio.net [127.0.0.1]) by kimball.webabinitio.net (Postfix) with ESMTP id E6A171B58F9 for ; Fri, 4 Jul 2008 11:06:06 -0400 (EDT) X-Virus-Scanned: amavisd-new at webabinitio.net Received: from kimball.webabinitio.net ([127.0.0.1]) by localhost (kimball.webabinitio.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 3uKTzZjSiRbW for ; Fri, 4 Jul 2008 11:06:06 -0400 (EDT) Received: from matthew.jpcalvin.com (matthew.jpcalvin.com [199.125.120.33]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by kimball.webabinitio.net (Postfix) with ESMTP id 09C6F1ABC52 for ; Fri, 4 Jul 2008 11:06:06 -0400 (EDT) Date: Fri, 4 Jul 2008 11:06:05 -0400 (EDT) From: rdmurray@bitdance.com To: freebsd-questions@freebsd.org In-Reply-To: <20080618073800.D290F10656BF@hub.freebsd.org> Message-ID: References: <20080618073800.D290F10656BF@hub.freebsd.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Subject: Re: 6.3 SMP but only one CPU detected X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Jul 2008 15:31:28 -0000 I wrote: > We have some systems we are upgrading from FreeBSD 6.1 to FreeBSD 6.3. > These are Dell PowerEdge servers. The one I'm working on now is a 1950. > Under 6.1 it booted into SMP mode no problem. Under 6.3, with no changes > made in the BIOS settings, it does not. Here is the start of the dmesg: Turns out the problem was a third party installer that added a line that disabled ACPI to /boot/loader.conf. Sigh. --David