Re: NEW_PCIB? pcib1: failed to allocate initial I/O port window: 0x4000-0x4fff

On Monday, June 06, 2011 9:33:30 pm John wrote:
> ----- 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:<ACPI PCI-PCI bridge> 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: <ACPI PCI-PCI bridge> at device 3.0 on pci0
> > > vgapci0: <VGA-compatible display> 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.

Hmmm, an MCA is not a good sign.

>    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.

Yes, there are multiple ranges.  Would it be possible to use a serial port to 
capture a full verbose dmesg up to the point where it hangs?

-- 
John Baldwin