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

From: John Baldwin <jhb_at_freebsd.org>
Date: Fri, 10 Jun 2011 10:52:30 -0400
On Wednesday, June 08, 2011 6:30:37 pm John wrote:
> ----- John Baldwin's Original Message -----
> > On Wednesday, June 08, 2011 12:13:05 am John wrote:
> > > ----- John Baldwin's Original Message -----
> > > > 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:
> > > > > > > 
> > > > > > >    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:
> > > > > 
> > > > >    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
> > > > > 
> > > > 
> > > > Hmmm, an MCA is not a good sign.
> > > > 
> > > > 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
> > > 
> > > Hi John
> > > 
> > >    Yes, I did get a serial console & ilo configured on the system today.
> > > I've attached two verbose consoles. The 1st is from -current as of today
> > > which fails to boot. The 2nd is from earlier this year which boot correctly.
> > 
> > Humm, is the first with any patches applied?  Earlier you reported a problem
> > that occured much later (failing to allocate the initial window) but in
> > your new dmesg it isn't getting that far.
> 
> Sorry John, here's the verbose dmesg output with your patch applied.
> 
> This is at the tail of the console:
> 
> pcib1: allocated memory range (0xf6000000-0xf6ffffff) for rid 10 of pci0:1:3:0
>         map[14]: type I/O Port, range 32, base 0x4400, size  8, enabled
> pcib1: failed to allocate initial I/O port window (0x4000-0x4fff,0x1000)
>         map[18]: type Memory, range 32, base 0xf5ff0000, size 12, enabled
> 
> 
> Output ends with a single 'M', not MCA as earlier.

Can you revert any patches I've sent you and update to the latest HEAD (I
just committed some bugfixes) and try it out please?

-- 
John Baldwin
Received on Fri Jun 10 2011 - 12:52:43 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:40:14 UTC