Date: Fri, 24 Apr 2009 11:00:09 +0100 (BST) From: Robert Watson <rwatson@FreeBSD.org> To: Gary Jennejohn <gary.jennejohn@freenet.de> Cc: pluknet <pluknet@gmail.com>, Michael Butler <imb@protected-networks.net>, Pierre Guinoiseau <geekounet@poildetroll.net>, jhb@FreeBSD.org, freebsd-current@freebsd.org Subject: Re: HEADS UP: rebuild all modules on 8.x (was: Re: 'sysctl -a | less' crashes -current) Message-ID: <alpine.BSF.2.00.0904241059060.54334@fledge.watson.org> In-Reply-To: <alpine.BSF.2.00.0904241013560.54334@fledge.watson.org> References: <49F12578.4060609@protected-networks.net> <200904241248.16562.doconnor@gsoft.com.au> <a31046fc0904232211r3a08647dte616b3ca38cf2c2f@mail.gmail.com> <49F16F9E.40306@poildetroll.net> <20090424104900.579dfa41@ernst.jennejohn.org> <alpine.BSF.2.00.0904241013560.54334@fledge.watson.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 24 Apr 2009, Robert Watson wrote: > I'll add a note to updating, but am confused about why the safety belts we > have in place to force module recompiles in this situation haven't done the > trick. Could we be dealing with straggling modules built before that was > added, or modules not built with our standard modules build parts? I've > CC'd John since he did the __FreeBSD_version-related changes, which I may > simply have misunderstood. It looks like the logic for constraining supported versions is more liberal than I assumed, so I've added a note to UPDATING. It is good practice to rebuild all modules between kernel updates on -CURRENT. If anyone can reproduce the malloc-related *after* rebuilding all modules, please let me know, it could be an indication of a bug in kern_malloc.c. Robert N M Watson Computer Laboratory University of Cambridge
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.00.0904241059060.54334>