From owner-freebsd-current@FreeBSD.ORG Mon May 16 17:38:33 2011 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 22B931065670 for ; Mon, 16 May 2011 17:38:33 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from vps1.elischer.org (vps1.elischer.org [204.109.63.16]) by mx1.freebsd.org (Postfix) with ESMTP id E9E658FC13 for ; Mon, 16 May 2011 17:38:32 +0000 (UTC) Received: from julian-mac.elischer.org (home-nat.elischer.org [67.100.89.137]) (authenticated bits=0) by vps1.elischer.org (8.14.4/8.14.4) with ESMTP id p4GHcSRM090288 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Mon, 16 May 2011 10:38:31 -0700 (PDT) (envelope-from julian@freebsd.org) Message-ID: <4DD16111.6090904@freebsd.org> Date: Mon, 16 May 2011 13:38:25 -0400 From: Julian Elischer User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X 10.4; en-US; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10 MIME-Version: 1.0 To: "deeptech71@gmail.com" References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: pcib allocation failure 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: Mon, 16 May 2011 17:38:33 -0000 On 5/15/11 8:50 PM, deeptech71@gmail.com wrote: > On Sat, May 14, 2011 at 6:27 PM, deeptech71@gmail.com > wrote: >> pcib1: at device 1.0 on pci0 >> pcib1: failed to allocate initial prefetch window: 0xd0000000-0xfaffffff >> >> this happens with a the r221862 kernel, but not with the r221309 kernel. >> a quick search reveals something: >> http://www.freebsd.org/cgi/query-pr.cgi?pr=143874 (i have no idea what >> that is). > indeed, r221394 introduced the said behaviour by using a new PCI bus > driver or something. with "nooptions NEW_PCIB", even the latest > sources (r221970) do not exhibit the said behaviour. i conclude that > the new PCI bus driver basically sux. Since "sux" was not one of the design criteria for the new driver it would seem that your best course of action is to contact the author with large amounts of useful information and offer to help him fix it by providing a test platform.