From owner-freebsd-ia64@FreeBSD.ORG Tue Jun 24 10:21:45 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 DFDDD37B401 for ; Tue, 24 Jun 2003 10:21:45 -0700 (PDT) Received: from ns1.xcllnt.net (209-128-86-226.bayarea.net [209.128.86.226]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0582843FA3 for ; Tue, 24 Jun 2003 10:21:43 -0700 (PDT) (envelope-from marcel@xcllnt.net) Received: from dhcp01.pn.xcllnt.net (dhcp01.pn.xcllnt.net [192.168.4.201]) by ns1.xcllnt.net (8.12.9/8.12.9) with ESMTP id h5OHLdDZ004492; Tue, 24 Jun 2003 10:21:40 -0700 (PDT) (envelope-from marcel@piii.pn.xcllnt.net) Received: from dhcp01.pn.xcllnt.net (localhost [127.0.0.1]) by dhcp01.pn.xcllnt.net (8.12.9/8.12.9) with ESMTP id h5OHLdhn023328; Tue, 24 Jun 2003 10:21:39 -0700 (PDT) (envelope-from marcel@dhcp01.pn.xcllnt.net) Received: (from marcel@localhost) by dhcp01.pn.xcllnt.net (8.12.9/8.12.9/Submit) id h5OHLbOx023327; Tue, 24 Jun 2003 10:21:37 -0700 (PDT) (envelope-from marcel) Date: Tue, 24 Jun 2003 10:21:37 -0700 From: Marcel Moolenaar To: qian Zhao Message-ID: <20030624172137.GA23224@dhcp01.pn.xcllnt.net> References: <20030624123710.81928.qmail@web15001.mail.bjs.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030624123710.81928.qmail@web15001.mail.bjs.yahoo.com> User-Agent: Mutt/1.5.4i 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 17:21:46 -0000 On Tue, Jun 24, 2003 at 08:37:10PM +0800, qian Zhao wrote: > Hi, > Who can tell me why the FreeBSD 5.1 for IA64can't run on Intel's Tiger4. Because we don't have one. > I complied the kernel of 5.1 on 5.0 of IA64. I found the machine reboot at the line between >>>>>>>>> and <<<<<<<<<< when type is 3. > void > mtx_lock_spin(&mca_info_block_lock); > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > result = ia64_sal_entry(SAL_GET_STATE_INFO, type, 0, > mca_info_block, 0, 0, 0, 0); > <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< > if (result.sal_status < 0) { It may be a SAL bug. Dunno, -- Marcel Moolenaar USPA: A-39004 marcel@xcllnt.net