From owner-freebsd-current@FreeBSD.ORG Thu Apr 3 18:25:24 2014 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id A9D0E1EF for ; Thu, 3 Apr 2014 18:25:24 +0000 (UTC) Received: from mail.lifanov.com (mail.lifanov.com [206.125.175.12]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 8C134E19 for ; Thu, 3 Apr 2014 18:25:24 +0000 (UTC) Received: by mail.lifanov.com (Postfix, from userid 58) id CBA261AF7F1; Thu, 3 Apr 2014 14:25:23 -0400 (EDT) X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on mail.lifanov.com X-Spam-Level: X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED,SHORTCIRCUIT shortcircuit=ham autolearn=disabled version=3.4.0 Received: from [10.1.3.5] (cnet520-windstream.mcclatchyinteractive.com [166.108.16.2]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by mail.lifanov.com (Postfix) with ESMTPSA id 3EED61A0071; Thu, 3 Apr 2014 14:25:22 -0400 (EDT) Message-ID: <533DA790.5050802@mail.lifanov.com> Date: Thu, 03 Apr 2014 14:25:20 -0400 From: Nikolai Lifanov User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0 MIME-Version: 1.0 To: Ryan Stone , Benjamin Kaduk Subject: Re: Boot fails @r264070 References: <20140403160031.GD30431@albert.catwhisker.org> <20140403162127.GE30431@albert.catwhisker.org> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: FreeBSD Current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.17 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: Thu, 03 Apr 2014 18:25:24 -0000 On 04/03/14 14:05, Ryan Stone wrote: > Can somebody please confirm whether setting hw.pci.enable_ari=0 in the > loader fixes the issue or not. That will help me to figure out if the > issue is with ARI or if I have somehow broken PCI enumeration in > general (I suspect the later). > __________________ I already tried it. I can confirm that it does not help. - Nikolai Lifanov