From owner-freebsd-ports@FreeBSD.ORG Fri May 29 21:19:11 2015 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id E0528E49 for ; Fri, 29 May 2015 21:19:11 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mail-ig0-x232.google.com (mail-ig0-x232.google.com [IPv6:2607:f8b0:4001:c05::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A853D159D for ; Fri, 29 May 2015 21:19:11 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: by igbsb11 with SMTP id sb11so24368193igb.0 for ; Fri, 29 May 2015 14:19:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=z8ACgIduVkRIqaAeZiSpo/pisKpDn/Lmk3rRjYHA0fU=; b=NZv0lQUCF4SALlXI2FWtiRAvlp0DurDkzVI3+2Nr08EUIWllIrLDDxV6meKw4n0e4l Azg09xaBSXjcYojAgHVy5WP4LmfNsHvaryDyqKEeymg4cercNoejUpLT5hqVjL8VzpcJ YXfNZGiSTI/3sTORB6mzN/PU2q2opCpkGT0n0qq6deYu6A7pjTT6/OgLynaTz7EbvSbL hdi4g27gD7994tkbB+hgX03ZqZ7W6Oz3SghLvipn4/EFCIig9kx2vttMavkcodRcTenV StH9HrLooR37X81AdHBacghogXN6yDBz497++JinhiiKtp/oB7aDJlv4wN/0djiyOwdO 8sPw== MIME-Version: 1.0 X-Received: by 10.50.57.112 with SMTP id h16mr6522625igq.35.1432934350953; Fri, 29 May 2015 14:19:10 -0700 (PDT) Sender: kob6558@gmail.com Received: by 10.107.46.134 with HTTP; Fri, 29 May 2015 14:19:10 -0700 (PDT) In-Reply-To: <5568B6FC.60700@pinyon.org> References: <55689D79.3090907@pinyon.org> <5568B6FC.60700@pinyon.org> Date: Fri, 29 May 2015 14:19:10 -0700 X-Google-Sender-Auth: HU0lV4xN-aVEHSimXPtwGcZ9Ivo Message-ID: Subject: Re: 10/stable virtualbox-ose crashes From: Kevin Oberman To: "Russell L. Carter" Cc: FreeBSD Ports ML Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 May 2015 21:19:12 -0000 On Fri, May 29, 2015 at 11:59 AM, Russell L. Carter wrote: > Hi Kevin, > > On 05/29/15 10:38, Kevin Oberman wrote: > >> On Fri, May 29, 2015 at 10:10 AM, Russell L. Carter > > wrote: >> >> Hi, >> kldload vboxsrv crashes recent 10/stables. Last known working >> kernel/module pair is from May 5th. >> >> Not sure what is the optimal next step, suggestions welcome. >> >> >> Sounds like you have done this, but several reports have been made of >> > > > Where were these reports made? Next time I'll look it up there first. > > this recently. All were "fixed" by rebuilding virtualbox-ose-kmod. >> Always rebuild all kernel modules that are in ports when rebuilding the >> kernel, preferably by adding the appropriate PORTS_MODULES to >> /etc/src.conf. >> > > I just perused "pkg info -D virtualbox-ose" and don't see a mention of > this, it might be a good idea to add the PORTS_MODULES bit to that > message. Hmm, nvidia-driver-* doesn't have it either. > > googling, I see: > > "You can place a list in /etc/src.conf like this: > > PORTS_MODULES= emulators/virtualbox-ose-kmod sysutils/fusefs-kmod > x11/nvidia-driver > > which will cause those modules to be built and installed with all the > proper matching stuff at the same time as buildkernel and > installkernel." > > I maintain my packages with poudriere. I build the world+kernel on > another system and install via NFS onto the poudriere package builder. > poudriere keeps its own world in a chroot, of course. But it doesn't > build a kernel. Which src.conf should the PORTS_MODULES be added to? > > Thanks the help, > Russell > If you run stable or current, I would not use packages for kernel modules. Build them from ports. They have nothing to link to, so the issues with mixing ports and packages should not arise. I don't know any sane way other than this to deal with kernel modules on stable or head. -- Kevin Oberman, Network Engineer, Retired E-mail: rkoberman@gmail.com