Date: Sun, 8 Nov 2020 09:43:36 +0900 From: Tomoaki AOKI <junchoon@dec.sakura.ne.jp> To: freebsd-current@freebsd.org Subject: Re: update UPDATING after malloc code change Message-ID: <20201108094336.4638ce33f22bf408cda31e52@dec.sakura.ne.jp> In-Reply-To: <b4981e58-60e8-3f02-2bfe-a1cef8bc135e@madpilot.net> References: <20201107162050.38fac464@ernst.home> <b4981e58-60e8-3f02-2bfe-a1cef8bc135e@madpilot.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 8 Nov 2020 00:22:26 +0100 Guido Falsi <mad@madpilot.net> wrote: > On 07/11/20 17:20, Gary Jennejohn wrote: > > It seems like an entry should be added to /usr/src/UPDATING, since the change made > > to the malloc code causes panics with KMODs from ports if they haven't been > > re-compiled. My nvidia-driver also caused a panic with a new kernel. > > > > A reminder/warning would be useful. > > > > Why? Rebuilding kmods every time you update the kernel sources is > already required by default. IIRC, there's no official documentation for it. Adding new NOTE for it into UPDATING (before the first dated entry) would be a good idea, as someone encounterd problem would read it to confirm any cautions. > You should be surprised when the old kmods still work, not the other way > around. +1. > > -- > Guido Falsi <mad@madpilot.net> > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" -- Tomoaki AOKI <junchoon@dec.sakura.ne.jp>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20201108094336.4638ce33f22bf408cda31e52>