From owner-freebsd-current@FreeBSD.ORG Wed Jul 20 22:53:11 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 1CF04106564A; Wed, 20 Jul 2011 22:53:11 +0000 (UTC) (envelope-from swills@FreeBSD.org) Received: from mouf.net (mouf.net [204.109.58.86]) by mx1.freebsd.org (Postfix) with ESMTP id 8070E8FC12; Wed, 20 Jul 2011 22:53:10 +0000 (UTC) Received: from meatwad.mouf.net (cpe-065-190-149-241.nc.res.rr.com [65.190.149.241]) (authenticated bits=0) by mouf.net (8.14.4/8.14.4) with ESMTP id p6KMMXkV081967 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Wed, 20 Jul 2011 18:22:34 -0400 (EDT) (envelope-from swills@FreeBSD.org) Message-ID: <4E275529.7050802@FreeBSD.org> Date: Wed, 20 Jul 2011 18:22:33 -0400 From: Steve Wills User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.17) Gecko/20110531 Thunderbird/3.1.10 MIME-Version: 1.0 To: John Baldwin References: <4E263EFE.3040200@FreeBSD.org> <201107200741.26362.jhb@freebsd.org> <565082b8e8b3e358266054e58e591e12@bluelife.at> <201107200904.45647.jhb@freebsd.org> In-Reply-To: <201107200904.45647.jhb@freebsd.org> X-Enigmail-Version: 1.1.2 Content-Type: multipart/mixed; boundary="------------010304030007080202090802" X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.6 (mouf.net [204.109.58.86]); Wed, 20 Jul 2011 18:22:34 -0400 (EDT) X-Virus-Scanned: clamav-milter 0.96.2 at mouf.net X-Virus-Status: Clean X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-current@FreeBSD.org, Bernhard Froehlich 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 22:53:11 -0000 This is a multi-part message in MIME format. --------------010304030007080202090802 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 07/20/11 09:04, John Baldwin wrote: > On Wednesday, July 20, 2011 8:33:07 am Bernhard Froehlich wrote: >> On Wed, 20 Jul 2011 07:41:26 -0400, John Baldwin wrote: >>> 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. >> >> Thanks a lot for the analysis! I've talked to one of the virtualbox >> developers about that but they are not aware of such problems with Linux >> or Windows guests yet. So they are currently unsure if it's a VirtualBox >> or FreeBSD fault and if it's their fault why it works fine with other >> guests. I'm also unsure because I haven't heard of that problem before >> and now multiple people complain. That looks more like a FreeBSD related >> problem on current or stable. >> >> I think it would be good if someone could try to reproduce that with >> emulators/virtualbox-ose-legacy which is 3.2.12 to get some vbox dev >> look into the problem again. > > FreeBSD just started honoring this setting in the BIOS this week and ignored > it previously. Can you get an acpidump from within VirtaulBox? I might be > able to point to a bug in it directly if so. > Thanks for the info! I've attached the acpidump and also posted a copy here: http://people.freebsd.org/~swills/vbox-4.0.8.asl.gz in case the mailing list eats it. Steve -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.17 (FreeBSD) iQEcBAEBAgAGBQJOJ1UoAAoJEPXPYrMgexuhhngIAJ/gyw1DMCciYDOw2Ek53dCb Cx2zFFm32THagLFIewKSL7RDKr6fNcNWuAdfFm/zpKq8nGUjA16p9A4eoOvdVc5u MhAu7oPZlnx9pX1o/JRjW0mtWglrHvKMapsptzlGOmS8PZMQz9s+L+IvGhsY8+qV avQ0V/w/AwG+T7x/vaCPpPdDPubuxT7vO+A5x9r4aUtFbKWIzF/1rsbq3cjIiGXw ExMpcdDBGRyLsPpB4fzhjb/drOQMJAkO2PnPPkWDociWCnC8Da/qCr6keD1lZPtD wx0UnMd/pyzJKVAuf4+VcifABIJIZeRqStIH7CB1fOKhcT+HDwatbKrEFGSvEMs= =COvj -----END PGP SIGNATURE----- --------------010304030007080202090802 Content-Type: application/octet-stream; name="vbox-4.0.8.asl.gz.sig" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="vbox-4.0.8.asl.gz.sig" iQEcBAABAgAGBQJOJ1UpAAoJEPXPYrMgexuhNxkIAK3HJ5Du4yQYivihQ87USagTHcTiytS2 PzPxTpVd+Rh1sHVAkn2UnNKowWh/7WhSdgWEqGp0ewBqtsko7aWSXsCyyuMcKubBdjTIPkIA vIMb+78iWjZN9VOvE6OLkIcQwhL4MIqHJoHHaH9Z3D99S67GCcC1IuDA4U5JXWyD12PKhMER KuwVwvRW35SI1M32hm1DSHIdeMt8U/r9Jz9qT5ECM6NsIxcmmPTFPD/VZXcZemfgrghKfVXZ lVg2y4scZd08GBsSeNwNkg0XsV1+JzNUk4JMXbefiXNke9Vzp2rohziDPWG5e3Wrvnr7uVaY ZbTao6re5G7W4OK7goZ7ipo= --------------010304030007080202090802--