From owner-freebsd-current@FreeBSD.ORG Thu Apr 3 18:05:42 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 66467BCB for ; Thu, 3 Apr 2014 18:05:42 +0000 (UTC) Received: from mail-oa0-x236.google.com (mail-oa0-x236.google.com [IPv6:2607:f8b0:4003:c02::236]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 30D33C45 for ; Thu, 3 Apr 2014 18:05:42 +0000 (UTC) Received: by mail-oa0-f54.google.com with SMTP id n16so2383885oag.13 for ; Thu, 03 Apr 2014 11:05:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=q/K/9pIYCI95ohjSQZIhjmVcA03llHUyYcq3ZwKd8/g=; b=Fd4ZPTP9+leGFeg23j5z7FYouLHJvHM+DO7+do8EG4cqpso26taZWqgMSlhFL5VFVN HYHK8Hloh1OGxGDaHuoPmY9gGpdtMhM6h+Ft4bEnoRAX7DcLJIR4uhrC7S8r3CCwJKAg 3IaMhvKBD7Xf9uHmWTLaJJGunWagBRnaI1HOkrtFf+Xbcwotq474+pCyCOtwnCMqG28W eLwvUIvr5YfbW4KcRXK9lVYIenUJNFsbnKZz0pKLb8lcLz//oOmXUTXsVPsV7fZKIQIk kZPqGXsKCPbe+SDHADORAFfUhukPmaRJTlYWbRGoeV0TiI8uNgPb9O6EsMt6SEVZpqPQ GL0w== MIME-Version: 1.0 X-Received: by 10.60.140.201 with SMTP id ri9mr2361455oeb.74.1396548341558; Thu, 03 Apr 2014 11:05:41 -0700 (PDT) Received: by 10.76.7.199 with HTTP; Thu, 3 Apr 2014 11:05:41 -0700 (PDT) In-Reply-To: References: <20140403160031.GD30431@albert.catwhisker.org> <20140403162127.GE30431@albert.catwhisker.org> Date: Thu, 3 Apr 2014 14:05:41 -0400 Message-ID: Subject: Re: Boot fails @r264070 From: Ryan Stone To: Benjamin Kaduk Content-Type: text/plain; charset=ISO-8859-1 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:05:42 -0000 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).