From owner-freebsd-current@FreeBSD.ORG Tue Jun 7 01:33:30 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 821) id E529F1065675; Tue, 7 Jun 2011 01:33:30 +0000 (UTC) Date: Tue, 7 Jun 2011 01:33:30 +0000 From: John To: John Baldwin Message-ID: <20110607013330.GA75754@FreeBSD.org> References: <20110606002353.GA2518@slowblink.com> <201106061051.30425.jhb@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <201106061051.30425.jhb@freebsd.org> User-Agent: Mutt/1.4.2.1i X-Mailman-Approved-At: Tue, 07 Jun 2011 01:38:44 +0000 Cc: freebsd-current@freebsd.org Subject: Re: NEW_PCIB? pcib1: failed to allocate initial I/O port window: 0x4000-0x4fff 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: Tue, 07 Jun 2011 01:33:31 -0000 ----- John Baldwin's Original Message ----- > On Sunday, June 05, 2011 8:23:53 pm John wrote: > > Hi Folks, > > > > I just attempted to update an HP385G0 system from current as of > > 4-15-2011 to 6-2-2011. The new system will not boot, and shows the > > following message when it hangs: > > > > pcib1: at device 3.0 on pci0 > > pcib1: failed to allocate initial I/O port window: 0x4000-0x4fff > > > > From a booting system, device 3.0 shows the following in dmesg: > > > > pcib1: at device 3.0 on pci0 > > vgapci0: port 0x4400-0x44ff mem > 0xf6000000-0xf6ffffff,0xf5ff0000-0xf5ff0fff at device 3.0 on pci1 > > > > From reading other msgs that seem related to this problem, I've > > attached the dmesg, devinfo -ur, and devinfo -rv below. > > > > Thanks for any help solving this. > > Please try this patch: > Hi John, I applied your patch/rebuilt/installed/rebooted. The system seems to get farther, but still locks up tight. A screen pic is here: http://people.freebsd.org/~jwd/dmesg.jpg The -v dmesg output looks right except for the 'MCA' text at the bottom. Not sure where it's coming from. It's worth noting sometimes the MCA doesn't show up, but it always locks up at that point now. In looking at the devinfo/dmesg output, I don't think I see any actual overlapping areas, but do see multiple items within the 0x4000 to 0x4fff range. I don't claim to be an expert though. I'm definately open to other ideas. Thanks, John