From owner-freebsd-ia64@FreeBSD.ORG Tue Jun 24 13:43:12 2003 Return-Path: Delivered-To: freebsd-ia64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5B43037B401 for ; Tue, 24 Jun 2003 13:43:12 -0700 (PDT) Received: from caduceus.sc.intel.com (fmr04.intel.com [143.183.121.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id BBCAC43FA3 for ; Tue, 24 Jun 2003 13:43:11 -0700 (PDT) (envelope-from arun.sharma@intel.com) Received: from talaria.sc.intel.com (talaria.sc.intel.com [10.3.253.5]) 2003/05/22 21:17:36 rfjohns1 Exp $) with ESMTP id h5OKfuL10759; Tue, 24 Jun 2003 20:41:56 GMT Received: from unix-os.sc.intel.com (unix-os.sc.intel.com [143.183.96.244]) 2003/05/22 21:18:01 rfjohns1 Exp $) with ESMTP id h5OKbQl19440; Tue, 24 Jun 2003 20:37:26 GMT Received: from intel.com (arun-desktop.sc.intel.com [143.183.85.194]) by unix-os.sc.intel.com (8.11.6/8.11.2) with ESMTP id h5OKh9k18049; Tue, 24 Jun 2003 13:43:09 -0700 Message-ID: <3EF8B7CD.402@intel.com> Date: Tue, 24 Jun 2003 13:42:53 -0700 From: Arun Sharma User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20030225 X-Accept-Language: en-us, en MIME-Version: 1.0 To: qian Zhao References: <20030624123710.81928.qmail@web15001.mail.bjs.yahoo.com> In-Reply-To: <20030624123710.81928.qmail@web15001.mail.bjs.yahoo.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: freebsd-ia64@freebsd.org Subject: Re: FreeBSD 5.1 can't run on Intel's Tiger4 X-BeenThere: freebsd-ia64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the IA-64 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Jun 2003 20:43:12 -0000 qian Zhao wrote: > Hi, > Who can tell me why the FreeBSD 5.1 for IA64can't run on Intel's Tiger4. You can comment out the calls to ia64_mca_save_state() and make further progress, but you'll probably run into ACPI related issues. Perhaps we should have a boot environment variable to disable ia64_mca_save_state() until we resolve this. -Arun