From owner-freebsd-current@FreeBSD.ORG Wed Jul 20 11:41:27 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D55431065686; Wed, 20 Jul 2011 11:41:27 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id AE4398FC17; Wed, 20 Jul 2011 11:41:27 +0000 (UTC) Received: from bigwig.baldwin.cx (66.111.2.69.static.nyinternet.net [66.111.2.69]) by cyrus.watson.org (Postfix) with ESMTPSA id 66AFF46B1A; Wed, 20 Jul 2011 07:41:27 -0400 (EDT) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id E82558A02C; Wed, 20 Jul 2011 07:41:26 -0400 (EDT) From: John Baldwin To: freebsd-current@freebsd.org Date: Wed, 20 Jul 2011 07:41:26 -0400 User-Agent: KMail/1.13.5 (FreeBSD/8.2-CBSD-20110617; KDE/4.5.5; amd64; ; ) References: <4E263EFE.3040200@FreeBSD.org> In-Reply-To: <4E263EFE.3040200@FreeBSD.org> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201107200741.26362.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.6 (bigwig.baldwin.cx); Wed, 20 Jul 2011 07:41:27 -0400 (EDT) Cc: Steve Wills Subject: Re: em problem in virtualbox since the weekend 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: Wed, 20 Jul 2011 11:41:27 -0000 On Tuesday, July 19, 2011 10:35:42 pm Steve Wills wrote: > Hi, > > While testing some other things, I found -CURRENT from yesterday doesn't > work with the em0 in my VirtualBox 4.0.8 (a little out of date > admittedly). It worked Friday or Saturday I think. Anyone else seen this > or should I open a PR? Has the code changed or am I perhaps > misremembering dates? The error reported is: > > em0: Unable to allocate bus resource: memory > em0: Allocation of PCI resources failed This is due to a bug in VirtualBox's BIOS implementation. Someone should file a bug report with VirtualBox to ask them to fix their BIOS. The problem is that they claim that the Host-PCI bridge in their system only decodes addresses 0xa0000-0xbffff (i.e. the VGA window) via the "Producer" resources in the _CRS method of the Host-PCI bridge device. This tells the OS that all the existing PCI devices are using invalid memory address ranges but that there is also no available address space to allocate for PCI devices such as em0. You can workaround this by setting "debug.acpi.disabled=hostres" until VirtualBox fixes their code. I'm happy to provide further clarification to an existing VirtaulBox bug report if needed. -- John Baldwin