From owner-freebsd-amd64@FreeBSD.ORG Tue Aug 22 18:15:14 2006 Return-Path: X-Original-To: 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 E758B16A4E2 for ; Tue, 22 Aug 2006 18:15:14 +0000 (UTC) (envelope-from mjacob@freebsd.org) Received: from ns1.feral.com (ns1.feral.com [192.67.166.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9900943D49 for ; Tue, 22 Aug 2006 18:15:14 +0000 (GMT) (envelope-from mjacob@freebsd.org) Received: from ns1.feral.com (localhost [127.0.0.1]) by ns1.feral.com (8.13.6/8.13.6) with ESMTP id k7MIFEBF005006; Tue, 22 Aug 2006 11:15:14 -0700 (PDT) (envelope-from mjacob@freebsd.org) Received: from localhost (mjacob@localhost) by ns1.feral.com (8.13.6/8.13.6/Submit) with ESMTP id k7MIFErO005003; Tue, 22 Aug 2006 11:15:14 -0700 (PDT) (envelope-from mjacob@freebsd.org) X-Authentication-Warning: ns1.feral.com: mjacob owned process doing -bs Date: Tue, 22 Aug 2006 11:15:14 -0700 (PDT) From: mjacob@freebsd.org X-X-Sender: mjacob@ns1.feral.com To: Kris Kennaway In-Reply-To: <20060822180902.GA80432@xor.obsecurity.org> Message-ID: <20060822111226.J4912@ns1.feral.com> References: <20060822091057.GA47193@xor.obsecurity.org> <20060822155812.GA76180@xor.obsecurity.org> <20060822110321.C4912@ns1.feral.com> <20060822180902.GA80432@xor.obsecurity.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: amd64@freebsd.org Subject: Re: mpt broken on amd64? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: mjacob@freebsd.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Aug 2006 18:15:15 -0000 > On Tue, Aug 22, 2006 at 11:05:41AM -0700, mjacob@freebsd.org wrote: >> >> Interesting. Worked fine on my EM64Ts for U320, SAS/SATA && FC- two >> different kinds. >> >> This is -current? > > Yes. Okay. My lab is disconnected mostly at the moment and I'm at a client's site today, but if it's okay with you I'll get it put back together tonite to reconfirm that -current is working for me so we can isolate it to what's going on for you. Can you do the following: a) try booting with ACPI disabled (does that work for a real AMD?) b) Give me an lspci output of your system thx