From owner-freebsd-stable@freebsd.org  Wed Mar 28 15:18:11 2018
Return-Path: <owner-freebsd-stable@freebsd.org>
Delivered-To: freebsd-stable@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 8DAE3F67E0E
 for <freebsd-stable@mailman.ysv.freebsd.org>;
 Wed, 28 Mar 2018 15:18:11 +0000 (UTC) (envelope-from slw@zxy.spb.ru)
Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 294AD70CE7
 for <freebsd-stable@freebsd.org>; Wed, 28 Mar 2018 15:18:11 +0000 (UTC)
 (envelope-from slw@zxy.spb.ru)
Received: from slw by zxy.spb.ru with local (Exim 4.86 (FreeBSD))
 (envelope-from <slw@zxy.spb.ru>)
 id 1f1Cq1-0001jH-VW; Wed, 28 Mar 2018 18:18:09 +0300
Date: Wed, 28 Mar 2018 18:18:09 +0300
From: Slawa Olhovchenkov <slw@zxy.spb.ru>
To: Gregory Byshenk <freebsd@byshenk.net>
Cc: freebsd-stable@freebsd.org
Subject: Re: KBI unexpexted change in stable/11 ?
Message-ID: <20180328151809.GK4305@zxy.spb.ru>
References: <20180328130903.GC6612@zxy.spb.ru>
 <20180328133946.GN51114@v1.leiden.byshenk.net>
 <20180328143551.GD6612@zxy.spb.ru>
 <20180328151348.GP51114@v1.leiden.byshenk.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20180328151348.GP51114@v1.leiden.byshenk.net>
User-Agent: Mutt/1.5.24 (2015-08-30)
X-SA-Exim-Connect-IP: <locally generated>
X-SA-Exim-Mail-From: slw@zxy.spb.ru
X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.25
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-stable>, 
 <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable/>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
 <mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Mar 2018 15:18:11 -0000

On Wed, Mar 28, 2018 at 05:13:48PM +0200, Gregory Byshenk wrote:

> On Wed, Mar 28, 2018 at 05:35:51PM +0300, Slawa Olhovchenkov wrote:
> > On Wed, Mar 28, 2018 at 03:39:46PM +0200, Gregory Byshenk wrote:
> > > 
> > > Did you rebuild your virtualbox and nvidia modules for your new
> > > kernel? If you build a new kernel, then you need to rebuild any
> > > modules that were installed from ports for the new version.
> > 
> > Only for -CURRENT, not for -STABLE:
> > 
> > https://lists.freebsd.org/pipermail/svn-src-all/2018-March/159649.html
> > 
> > John Baldwin: "In theory we try to not break existing kernel
> > modules on a stable branch.  That is, one should be able to kldload an
> > if_iwn.ko built on 11.0 on a 11-stable kernel."
> 
> I understand that this is true for standard kernel modules, but
> I have frequently run into problems loading _ports_ modules on
> a new kernel - including in STABLE.

This is general _kernel_ rule, for loading all modules, mostly for
third-party modules.