From owner-freebsd-current@FreeBSD.ORG Fri Apr 24 10:00:10 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 359F01065678; Fri, 24 Apr 2009 10:00:10 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id E6F7E8FC24; Fri, 24 Apr 2009 10:00:09 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [65.122.17.41]) by cyrus.watson.org (Postfix) with ESMTPS id 9A5DA46B35; Fri, 24 Apr 2009 06:00:09 -0400 (EDT) Date: Fri, 24 Apr 2009 11:00:09 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Gary Jennejohn In-Reply-To: Message-ID: References: <49F12578.4060609@protected-networks.net> <200904241248.16562.doconnor@gsoft.com.au> <49F16F9E.40306@poildetroll.net> <20090424104900.579dfa41@ernst.jennejohn.org> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: pluknet , Michael Butler , Pierre Guinoiseau , jhb@FreeBSD.org, freebsd-current@freebsd.org Subject: Re: HEADS UP: rebuild all modules on 8.x (was: Re: 'sysctl -a | less' crashes -current) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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: Fri, 24 Apr 2009 10:00:10 -0000 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