From owner-freebsd-current@FreeBSD.ORG Mon May 16 13:40:20 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 4D8D4106564A for ; Mon, 16 May 2011 13:40:20 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id 246398FC0A for ; Mon, 16 May 2011 13:40:20 +0000 (UTC) Received: from bigwig.baldwin.cx (66.111.2.69.static.nyinternet.net [66.111.2.69]) by cyrus.watson.org (Postfix) with ESMTPSA id CBA9646B09; Mon, 16 May 2011 09:40:19 -0400 (EDT) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 6CA4B8A04F; Mon, 16 May 2011 09:40:19 -0400 (EDT) From: John Baldwin To: freebsd-current@freebsd.org Date: Mon, 16 May 2011 09:37:53 -0400 User-Agent: KMail/1.13.5 (FreeBSD/8.2-CBSD-20110325; KDE/4.5.5; amd64; ; ) References: In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201105160937.53197.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.6 (bigwig.baldwin.cx); Mon, 16 May 2011 09:40:19 -0400 (EDT) Cc: "deeptech71@gmail.com" 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 13:40:20 -0000 On Sunday, May 15, 2011 8:50:04 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. A more helpful approach would be to provide a verbose dmesg, devinfo -ur, and devinfo -rv output. -- John Baldwin