From owner-freebsd-current@FreeBSD.ORG Tue Sep 1 14:31:18 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 37E3B1065672 for ; Tue, 1 Sep 2009 14:31:18 +0000 (UTC) (envelope-from nick-lists@netability.ie) Received: from mail.acquirer.com (mail.acquirer.com [87.198.142.193]) by mx1.freebsd.org (Postfix) with ESMTP id B3E518FC08 for ; Tue, 1 Sep 2009 14:31:16 +0000 (UTC) X-Envelope-To: freebsd-current@freebsd.org Received: from cupcake.internal.acquirer.com (cupcake.internal.acquirer.com [10.228.100.105]) (authenticated bits=0) by mail.acquirer.com (8.14.3/8.14.3) with ESMTP id n81EVCDw021018 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Tue, 1 Sep 2009 15:31:12 +0100 (IST) (envelope-from nick-lists@netability.ie) Message-ID: <4A9D3030.9040500@netability.ie> Date: Tue, 01 Sep 2009 15:31:12 +0100 From: Nick Hilliard User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.1.1) Gecko/20090715 Thunderbird/3.0b3 MIME-Version: 1.0 To: John Baldwin References: <4A9BF23F.6070801@netability.ie> <4A9BF438.1000006@smeets.im> <200909011002.59592.jhb@freebsd.org> In-Reply-To: <200909011002.59592.jhb@freebsd.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-4.2 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on muffin.acquirer.com Cc: freebsd-current@freebsd.org Subject: Re: 8.0-beta3 does not detect several ata channels X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Sep 2009 14:31:18 -0000 On 01/09/2009 15:02, John Baldwin wrote: > Hmm, so an idea I had just now.. can you grab a dump of the PCI config space > for the disk controller in the MCFG vs non-MCFG cases? That is, find the > device's address using pciconf -lv (e.g. pci0:0:30:0 or some such) and then > run this command under both configurations and save the output: > > pciconf -r pci0:0:30:0 0:0xfc 7.1, 8.0-beta3, or does it matter? Nick