From owner-freebsd-amd64@FreeBSD.ORG  Thu Jan 29 06:04:18 2004
Return-Path: <owner-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 35E1E16A4CE
	for <freebsd-amd64@freebsd.org>; Thu, 29 Jan 2004 06:04:18 -0800 (PST)
Received: from bigtex.jrv.org (rrcs-sw-24-73-246-106.biz.rr.com
	[24.73.246.106])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 3D14A43D3F
	for <freebsd-amd64@freebsd.org>;
	Thu, 29 Jan 2004 06:04:13 -0800 (PST)
	(envelope-from james@bigtex.jrv.org)
Received: from bigtex.jrv.org (localhost [127.0.0.1])
	by bigtex.jrv.org (8.12.1/8.12.1) with ESMTP id i0TE4Co8010297
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Thu, 29 Jan 2004 08:04:12 -0600 (CST)
Received: (from james@localhost)
	by bigtex.jrv.org (8.12.1/8.12.1/Submit) id i0TE4Co1010294;
	Thu, 29 Jan 2004 08:04:12 -0600 (CST)
Date: Thu, 29 Jan 2004 08:04:12 -0600 (CST)
Message-Id: <200401291404.i0TE4Co1010294@bigtex.jrv.org>
From: James Van Artsdalen <james-freebsd-amd64@jrv.org>
To: tomh@waterloo.equitrac.com
In-reply-to: <B1D77424948FD611A3B80000C0109EEF0225A07A@SYNCRO>
	(tomh@waterloo.equitrac.com)
References: <B1D77424948FD611A3B80000C0109EEF0225A07A@SYNCRO>
cc: freebsd-amd64@freebsd.org
Subject: Re: New AMD64 owner
X-BeenThere: freebsd-amd64@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Porting FreeBSD to the AMD64 platform <freebsd-amd64.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-amd64>,
	<mailto:freebsd-amd64-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-amd64>
List-Post: <mailto:freebsd-amd64@freebsd.org>
List-Help: <mailto:freebsd-amd64-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-amd64>,
	<mailto:freebsd-amd64-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Jan 2004 14:04:18 -0000

> From: "Haapanen, Tom" <tomh@waterloo.equitrac.com>
> Date: Thu, 29 Jan 2004 08:45:11 -0500
> 
> Is there any real downside in turning off ACPI?  Especially for a server
> that will be running 24x7?

If it seems to work then turning off ACPI has no important downside.

"Seems to work" means that you can access a disk drive or talk over a
network: I don't expect any subtle failure modes.

My familiarity with this is from the BIOS side, and about five years
old, but I think FreeBSD can get all of the data it needs to configure
the IRQ/IOAPIC from the MP tables.  ACPI probably isn't required.

The bigger question is whether the MP table data is reliable.  I
believe Windows uses ACPI exclusively if available, so once BIOS
vendor X has ACPI everything else becomes untested and unreliable.

(vendors generally don't test anything the current version of Windows
doesn't use, so ACPI in FreeBSD is preferred even if theoretically
unnecessary).

I see no reason not to deploy a FreeBSD/AMD64 server right now, after
the hardware is burned in, and if all of the apps run 64-bit.