From owner-freebsd-current@FreeBSD.ORG Mon Nov 21 04:05:31 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 8CF5416A41F; Mon, 21 Nov 2005 04:05:31 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (vc4-2-0-87.dsl.netrack.net [199.45.160.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id E9C9B43D58; Mon, 21 Nov 2005 04:05:30 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (localhost.village.org [127.0.0.1] (may be forged)) by harmony.bsdimp.com (8.13.3/8.13.3) with ESMTP id jAL44kBU033428; Sun, 20 Nov 2005 21:04:46 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Sun, 20 Nov 2005 21:04:57 -0700 (MST) Message-Id: <20051120.210457.109704843.imp@bsdimp.com> To: wpaul@freebsd.org From: "M. Warner Losh" In-Reply-To: <20051120042536.E72D816A421@hub.freebsd.org> References: <20051120013530.GA55161@nowhere> <20051120042536.E72D816A421@hub.freebsd.org> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0 (harmony.bsdimp.com [127.0.0.1]); Sun, 20 Nov 2005 21:04:51 -0700 (MST) Cc: craig@xfoil.gank.org, current@freebsd.org, tillman@seekingfire.com 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 04:05:31 -0000 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... Warner