From owner-freebsd-stable@FreeBSD.ORG  Mon Jun  5 17:12:29 2006
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
X-Original-To: freebsd-stable@freebsd.org
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 47A4316B01A
	for <freebsd-stable@freebsd.org>; Mon,  5 Jun 2006 17:12:29 +0000 (UTC)
	(envelope-from jfvogel@gmail.com)
Received: from wx-out-0102.google.com (wx-out-0102.google.com [66.249.82.192])
	by mx1.FreeBSD.org (Postfix) with ESMTP id C45B443D46
	for <freebsd-stable@freebsd.org>; Mon,  5 Jun 2006 17:12:28 +0000 (GMT)
	(envelope-from jfvogel@gmail.com)
Received: by wx-out-0102.google.com with SMTP id i31so771778wxd
	for <freebsd-stable@freebsd.org>; Mon, 05 Jun 2006 10:12:28 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
	h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=Rg5GjR+xVITwNuzvgWqtEtcwf8oz8aks6aZsovJnfiuFhE48VcXY6aJk2cW6OMJUj4lppgKYCCYFCX3SGx44u3r2DS+sovmjjSHM5D1WQ5gZ11Dr/w4bv2J/jhxUbuMW9opjA7m0DI6hc3LMEi157nn7r3ssy9KRgsp/RfLkGz8=
Received: by 10.70.32.15 with SMTP id f15mr6288961wxf;
	Mon, 05 Jun 2006 10:12:28 -0700 (PDT)
Received: by 10.70.90.17 with HTTP; Mon, 5 Jun 2006 10:12:28 -0700 (PDT)
Message-ID: <2a41acea0606051012r5831971qb3d2fb88e701225@mail.gmail.com>
Date: Mon, 5 Jun 2006 10:12:28 -0700
From: "Jack Vogel" <jfvogel@gmail.com>
To: "Pete French" <petefrench@ticketswitch.com>
In-Reply-To: <E1FnI6R-0003aM-3o@dilbert.firstcallgroup.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <2a41acea0606050919p17efd6cfva55113b19d105815@mail.gmail.com>
	<E1FnI6R-0003aM-3o@dilbert.firstcallgroup.co.uk>
Cc: freebsd-stable@freebsd.org
Subject: Re: Dual Opteron system will not run SMP
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, 
	<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Jun 2006 17:12:35 -0000

On 6/5/06, Pete French <petefrench@ticketswitch.com> wrote:
> > You say you can boot 'safe', can you boot with just ACPI disabled?
>
> Not using an SMP kernel, no. I did another experiment though, I
> installed amd64 onto an IDe drive, and that will boot SMP with
> APCI disabled, but still only recognises a single processor.
>
> > One suggestion, boot in SAFE or non-ACPI, then do a pciconf -l and
> > look for pci devices that are unknown. At least that will give more
> > evidence.
>
> O.K, will give that a shot later this evening.
>
> > Hard to say if its ACPI or PCI related. Uh, you did make sure you
> > have the latest BIOS for your motherboard right?
>
> Yup - first thing I did. I also asked if other people are using this, and
> Soren apparently uses it (for amd64), so it preseumably does work!

We (Intel networking group) have seen issues with SMP and amd64
as well, although I dont know that its fully characterized (what works
and what doesnt) yet.

If just non-ACPI isnt sufficient, the other thing SAFE does is turn
off disk DMA. I have an as-yet unreleased system that has this
same type of issue, and the problem is that two PCI device ID's
are not recognized, so maybe that will be your problem.

Jack