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> In-Reply-To: <20180328151348.GP51114@v1.leiden.byshenk.net> References: <20180328130903.GC6612@zxy.spb.ru> <20180328133946.GN51114@v1.leiden.byshenk.net> <20180328143551.GD6612@zxy.spb.ru> <20180328151348.GP51114@v1.leiden.byshenk.net>
next in thread | previous in thread | raw e-mail | index | archive | help
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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20180328151809.GK4305>