From owner-freebsd-stable@freebsd.org Sat Jul 16 20:57:40 2016 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A558EB9BBE0 for ; Sat, 16 Jul 2016 20:57:40 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (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 7E6C012AB for ; Sat, 16 Jul 2016 20:57:40 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id CA7A0202F7 for ; Sat, 16 Jul 2016 16:57:33 -0400 (EDT) Received: from web2 ([10.202.2.212]) by compute3.internal (MEProxy); Sat, 16 Jul 2016 16:57:33 -0400 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=zyxst.net; h= content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-sasl-enc :x-sasl-enc; s=mesmtp; bh=qr5fJRvcg0JxL9EO7lxV7oBVCNA=; b=G6BIRk pYZbvzmYqA4zvps9THShuQSLZPqT9iAg+/2/uNvkV0DGhjjXd+fai79bt+VU2Msw 1jdvsJNyzvgnY/wYHQQL35XUSg/jL/XUoawipUAlPerDONPlF8zRdbvUqeEnQUuK u4B8KPiBsNw0GqgKPwhTn5PF92UHw81JurHp8= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-sasl-enc:x-sasl-enc; s=smtpout; bh=qr5fJRvcg0JxL9E O7lxV7oBVCNA=; b=E1/eDGyjjdLYwaBI08c+ph4slg1YZllJckZ+L3NUzKllR+7 UVtQvSdGrloQvu5pLVomn2+UxvkImkRyUmMuaF+xtddgXHIZyectFSPpPNq6mvgu apIPZNeCi8gTUSHU0sDjNC5x36Ca4WoQ2pgtUjbMjCMqlRRlu+q56hI9YuwQ= Received: by mailuser.nyi.internal (Postfix, from userid 99) id 9B6AED05AD; Sat, 16 Jul 2016 16:57:33 -0400 (EDT) Message-Id: <1468702653.2439899.668236153.3FCCA4ED@webmail.messagingengine.com> X-Sasl-Enc: g6AUmI4vVSMmzL52Gsk1VTqGvbaeHoaIE3xPKnUAyaI0 1468702653 From: John To: freebsd-stable@freebsd.org MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain X-Mailer: MessagingEngine.com Webmail Interface - ajax-bf4e2c8f In-Reply-To: <20160716134746.GN1261@albert.catwhisker.org> References: <20160716134746.GN1261@albert.catwhisker.org> Subject: Re: Building "extra" kernels in stable/11...? Date: Sat, 16 Jul 2016 21:57:33 +0100 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 16 Jul 2016 20:57:40 -0000 On Sat, 16 Jul 2016, at 14:47, David Wolfskill wrote: > Today, as part of my gradual ramp-up toward getting readyto test > stable/11 on more than just the above build machine and my laptop, I > figured I'd start building those extra kernels (along with GENERIC) when > the build machine updated its stable/11. > > Accordingly, I appended > > KERNCONF?=GENERIC ALBERT BATS > > to /etc/src.conf -- but the only kernel even attempted was GENERIC. In > reviewing the typescript (as I do all builds within script(1)), there > was no indication that the kernel-building process had any awareness > that anything other than GENERIC was wanted. > > Have I managed to overlook something obvious (again)? Hi, I noticed this stopped working a couple of months ago. I don't put it in src.conf though - mine goes in make.conf like this: KERNCONF=CUSTOMKERNEL1 GENERIC which means that both kernels would be built and installed with no special parameters to the buildkernel and installkernel commands. Less typing! I first noticed it when after building and installing a new world, the kernel came up with the warning that WITNESS was enabled (it's disabled in the custom kernel). So I had to build and install another kernel with the KERNCONF=CUSTOMKERNEL1 parameter. The problem happened at around the time I noticed GENERIC-NODEBUG appearing in /sys/amd64/conf - though this might be entirely coincidental. This was a month or so ago. I'll re-enable KERNCONF= in my make.conf, run another build and get back to you. -- John tech-lists@zyxst.net