Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 7 Jun 2011 10:35:37 -0400
From:      John Baldwin <jhb@freebsd.org>
To:        freebsd-current@freebsd.org
Cc:        "deeptech71@gmail.com" <deeptech71@gmail.com>
Subject:   Re: pcib allocation failure
Message-ID:  <201106071035.37662.jhb@freebsd.org>
In-Reply-To: <BANLkTi=rv8WjO3Wx15OQF-_3_S67PW4EEw@mail.gmail.com>
References:  <BANLkTikTHFTHff5iuPDMxR6zhezEcTaZSA@mail.gmail.com> <201106061052.32727.jhb@freebsd.org> <BANLkTi=rv8WjO3Wx15OQF-_3_S67PW4EEw@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Monday, June 06, 2011 11:02:59 pm deeptech71@gmail.com wrote:
> On Mon, Jun 6, 2011 at 4:52 PM, John Baldwin <jhb@freebsd.org> wrote:
> > Can you try out this change.  It is a possible "real" solution (or at 
least a
> > stopgap until we start using multipass to untangle the resource mess a bit
> > further):
> [snip]
> 
> that doesn't work. i get an allocation failure.

It is expected to still get an allocation failure.

Instead what the change does is avoid updating the registers for the window
until after all the devices on the bus have been probed.

Were you able to save a dmesg somehow from the boot with this patch?

-- 
John Baldwin



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201106071035.37662.jhb>