From owner-freebsd-current@FreeBSD.ORG Mon Nov 21 18:16:57 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 398CF16A420; Mon, 21 Nov 2005 18:16:57 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from speedfactory.net (mail6.speedfactory.net [66.23.216.219]) by mx1.FreeBSD.org (Postfix) with ESMTP id 01EFD43D45; Mon, 21 Nov 2005 18:16:55 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (unverified [66.23.211.162]) by speedfactory.net (SurgeMail 3.5b3) with ESMTP id 2371905 for multiple; Mon, 21 Nov 2005 13:17:06 -0500 Received: from localhost (john@localhost [127.0.0.1]) by server.baldwin.cx (8.13.1/8.13.1) with ESMTP id jALIGkcl070379; Mon, 21 Nov 2005 13:16:51 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-current@freebsd.org Date: Mon, 21 Nov 2005 13:07:02 -0500 User-Agent: KMail/1.8.2 References: <20051120013530.GA55161@nowhere> <20051120042536.E72D816A421@hub.freebsd.org> <20051120.210457.109704843.imp@bsdimp.com> In-Reply-To: <20051120.210457.109704843.imp@bsdimp.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200511211307.05043.jhb@freebsd.org> X-Spam-Status: No, score=-2.8 required=4.2 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on server.baldwin.cx X-Server: High Performance Mail Server - http://surgemail.com r=1653887525 Cc: wpaul@freebsd.org, tillman@seekingfire.com, current@freebsd.org, "M. Warner Losh" , craig@xfoil.gank.org Subject: Re: Compaq ProLiant 1600 server freezes when detecting keyboard controller 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, 21 Nov 2005 18:16:57 -0000 On Sunday 20 November 2005 11:04 pm, M. Warner Losh wrote: > In message: <20051120042536.E72D816A421@hub.freebsd.org> > > wpaul@freebsd.org (Bill Paul) writes: > : Our PCI code > : then comes along and enables all of the devices but doesn't necessarily > : update the base address registers on some of them, which has the effect > : of mapping one of the PCI devices at physical address 0. > > Actually, that bug has been fixed in recent versions of > FreeBSD-current, and should be fixed in 6.0. I recall merging changes > to 6.0 just before the release. The problem was that the host bridge > wasn't properly setting a range. If that's not the case, then I'd > like to know about it... No, the bug was fixed, but that wasn't the fix. The fix was to bail out earlier if a BAR's base was 0 and not enable IO or MEM decoding unless a BAR had a valid base (where 0 and 0xfffffff are both invalid bases). -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org