From owner-freebsd-current@freebsd.org Mon Feb 5 18:44:03 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7CB6BEE5A62 for ; Mon, 5 Feb 2018 18:44:03 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 116F8828AD for ; Mon, 5 Feb 2018 18:44:03 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id C6A44EE5A61; Mon, 5 Feb 2018 18:44:02 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A4727EE5A60 for ; Mon, 5 Feb 2018 18:44:02 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mail-vk0-x230.google.com (mail-vk0-x230.google.com [IPv6:2607:f8b0:400c:c05::230]) (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 3E66A828AB for ; Mon, 5 Feb 2018 18:44:02 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: by mail-vk0-x230.google.com with SMTP id q62so18275335vkb.11 for ; Mon, 05 Feb 2018 10:44:02 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=hDApsuOoeY6Vy4sM3PYhlfU5PcZ0s24A4PAK5x0wHRw=; b=hKa0zb5ziOWthv7+K7uFZBgLUA1pastT3x0lGn/afDBm9dKr6WYjan4GOWg/V3z31i TgKAHBGwZEvhxJitpMQZ/2KswY2+WKu0O7dwCFBY03jMoYKqryw9KNtKynxkeZKIG1fy 53PeRkgvSVV+mbbczuUz6/qB17GbzWb03ZVILT8lhOlh8L/R01Z5EfqwUBoPdoL4gHCB q0YA47Z8yYYd/OwPEePhOOOb7HH6co7aFmtx3VQNHTGlBWrqRg/MJc7H2ghHUR5p8Tdl rFKQMycl3YZ0uXbyHoQzX4ZiagmJQ0Rn+LJJmwJY+KKCF4gtspolB7lWpJmD1zvIOr6/ XJxg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=hDApsuOoeY6Vy4sM3PYhlfU5PcZ0s24A4PAK5x0wHRw=; b=uMxr//6pADEQshZ/5fR5AVBgqYYWjJjrX+JCLj2UGB6dvVAYuoG1XVexEZNsrEJlTC gxx79I9f3LcBAMNLKvFlkHvn2pWuV2bf1Eky5SZHn23JN5DGN9OFubEJRxYf2AvZZw5E BHVwkme6ThVSmDO2scxaWVoSyI/4+9H7B+tbwCEZi6GZ4VTwyL5CwJ7rJG+x9jToDlDZ jPahmtIfS8NF2HyUATlafJgk/yOKHi/wKVLA+tSJMHvbPUlP3FXaYp6tLyGTT8/dZVyh Nf7VnGV/6+JT2877KFZUrAz6wnxCdMLliEDembH0siEFY6GFMhcaSO8EatDxB3vWjz7s mXCg== X-Gm-Message-State: AKwxytd7uSHiQE1Cx1kgua2EXVFibFWG3mUw2oBlh3piL2rkbpujoH0d wGmRw1Sa2qRZTNN9Ia0tQkQZlua+SXhfUofL+Cs= X-Google-Smtp-Source: AH8x224lxKaGCLg7NH/AC7gsfTvTL/PtDpL/FfVfrHdXoyeEqMwFMMH3CjnNn2eEHsDLzZHcubkrZ6R6SAZ1oa4tlaE= X-Received: by 10.31.134.74 with SMTP id i71mr41871955vkd.128.1517856241658; Mon, 05 Feb 2018 10:44:01 -0800 (PST) MIME-Version: 1.0 Sender: kob6558@gmail.com Received: by 10.103.39.199 with HTTP; Mon, 5 Feb 2018 10:44:01 -0800 (PST) In-Reply-To: References: <201802041819.w14IJSFi003912@slippy.cwsent.com> From: Kevin Oberman Date: Mon, 5 Feb 2018 10:44:01 -0800 X-Google-Sender-Auth: kYsydzVvkowh7IIscf1alvwShhI Message-ID: Subject: Re: Jan 18 04:05 vboxdrv.ko breaks r328637: Wed Jan 31 kernel. crashes To: Taavi Cc: Cy Schubert , "current@freebsd.org" Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 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: Mon, 05 Feb 2018 18:44:03 -0000 On Mon, Feb 5, 2018 at 2:49 AM, Taavi wrote: > Hi > > Not really wanting to do that. Using pkg binary system for purpose > > That would lead to question why binary package driver crashes kernel? > > regards, > Taavi > This is a real problem with kmod packages. If hte kernel is modified in any way, modules must be re-built. It may take a while for the package to get re-built for a given change as the port has not been modified. The recommended method is to put port modules into /etc/src.conf PORTS_MODULES list so that kernel rebuild will always rebuild the modules, but that only works if the kernel IS built from sources and re-installed. It will be a bigger issue when more people start doing binary updates to the kernel.more routinely.