Date: Mon, 21 Nov 2005 13:07:02 -0500 From: John Baldwin <jhb@freebsd.org> To: freebsd-current@freebsd.org Cc: wpaul@freebsd.org, tillman@seekingfire.com, current@freebsd.org, "M. Warner Losh" <imp@bsdimp.com>, craig@xfoil.gank.org Subject: Re: Compaq ProLiant 1600 server freezes when detecting keyboard controller Message-ID: <200511211307.05043.jhb@freebsd.org> In-Reply-To: <20051120.210457.109704843.imp@bsdimp.com> References: <20051120013530.GA55161@nowhere> <20051120042536.E72D816A421@hub.freebsd.org> <20051120.210457.109704843.imp@bsdimp.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sunday 20 November 2005 11:04 pm, M. Warner Losh wrote: > 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... No, the bug was fixed, but that wasn't the fix. The fix was to bail out earlier if a BAR's base was 0 and not enable IO or MEM decoding unless a BAR had a valid base (where 0 and 0xfffffff are both invalid bases). -- John Baldwin <jhb@FreeBSD.org> <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200511211307.05043.jhb>