From owner-freebsd-current@FreeBSD.ORG Sun Aug 5 00:56:34 2012 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 EB76A1065670; Sun, 5 Aug 2012 00:56:34 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mail-we0-f182.google.com (mail-we0-f182.google.com [74.125.82.182]) by mx1.freebsd.org (Postfix) with ESMTP id 50B3B8FC08; Sun, 5 Aug 2012 00:56:33 +0000 (UTC) Received: by weyx56 with SMTP id x56so1518311wey.13 for ; Sat, 04 Aug 2012 17:56:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=llYCzuYon5y45b7ICIpEwXIxpUoDeRIGiZApDwd76FI=; b=mkDFNCFj7j8+rPa2ka+oX5dYymD7weLnAJdzJ/F5EGl+LpL9trs5QFvadRnPOVc5lH vlsBqme0v+XRAGGHJ4MKHtk3s6gTwLNU/Hq2oikRV+dfGFwZx+qlT2W3MIxNtWKt6eJL Lo9ObzbPuUV2LCOCc7CCoqDZWZ1CbmgYA6R6IT/DK6gJUlqWWVyRN5aN/QxaXvRrqjn1 KaoosT1JH/1nes214eyxtRsPQ92VcwPAr6A9L+IXnEzozYcwPJCFdWPhWMthV6QD5pLr laDrqrCL2+Mf6tpBYiwtMvMaOgPs529pKHTdmzsfVtNa0Zobcr6FKp6UuJmTrM1HiJFr wkLA== MIME-Version: 1.0 Received: by 10.180.97.33 with SMTP id dx1mr7507995wib.18.1344128192888; Sat, 04 Aug 2012 17:56:32 -0700 (PDT) Received: by 10.223.60.147 with HTTP; Sat, 4 Aug 2012 17:56:32 -0700 (PDT) In-Reply-To: <501D9476.80902@FreeBSD.org> References: <501A323E.6000106@zedat.fu-berlin.de> <1343972667.4952.5.camel@Nokia-N900-42-11> <20120803134123.GA52965@onelab2.iet.unipi.it> <501CD1F8.1070404@zedat.fu-berlin.de> <501D8589.50205@FreeBSD.org> <501D9476.80902@FreeBSD.org> Date: Sat, 4 Aug 2012 17:56:32 -0700 Message-ID: From: Kevin Oberman To: Doug Barton Content-Type: text/plain; charset=UTF-8 Cc: Garrett Cooper , FreeBSD Current , "O. Hartmann" Subject: Re: VirtualBox: Eating up 100% CPU, freezing Windows 7 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: Sun, 05 Aug 2012 00:56:35 -0000 On Sat, Aug 4, 2012 at 2:30 PM, Doug Barton wrote: > On 08/04/2012 14:26, Garrett Cooper wrote: >> On Sat, Aug 4, 2012 at 1:26 PM, Doug Barton wrote: >> >>> On 08/04/2012 00:40, O. Hartmann wrote: >>>> No, also in my case. I build world and the VBox software with each >>>> kernel - usually. >>> >>> You can ensure that by putting this in src.conf: >>> >>> PORTS_MODULES= emulators/virtualbox-ose-kmod >>> >>> You can place other modules in that list as well. I use vbox so you can >>> be pretty confident that this is going to keep working. :) >> >> That doesn't work > > I assure you that it does. I have put a non-zero amount of work into > fixing it, I use this method, and the resulting kernel module works just > fine. > > If you actually try it and find something is not as it should be, then > yes; please do file a PR and feel free to cc me. > > Doug I am only aware of this because of your posts. No reference to it at all in src.conf(5). It would be nice to see it there. It is mentioned in build(7), but only as a MAKE option and a lot of people are not going to realize it can be placed in src.conf. Also, for those not fairly conversant in make, it is not clear whether multiple ports should be space, comma, colon, or otherwise delimited This is a very nice option as it is very easy to overlook rebuilding kernel modules in ports when building the kernel. Thanks or working on it. -- R. Kevin Oberman, Network Engineer E-mail: kob6558@gmail.com