From owner-freebsd-stable@freebsd.org Wed Dec 9 06:48:39 2020 Return-Path: Delivered-To: freebsd-stable@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 2ABDE471E24 for ; Wed, 9 Dec 2020 06:48:39 +0000 (UTC) (envelope-from kp@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4CrSLb0ndfz4WJG; Wed, 9 Dec 2020 06:48:39 +0000 (UTC) (envelope-from kp@FreeBSD.org) Received: from venus.codepro.be (venus.codepro.be [5.9.86.228]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mx1.codepro.be", Issuer "Let's Encrypt Authority X3" (verified OK)) (Authenticated sender: kp) by smtp.freebsd.org (Postfix) with ESMTPSA id E854627693; Wed, 9 Dec 2020 06:48:38 +0000 (UTC) (envelope-from kp@FreeBSD.org) Received: by venus.codepro.be (Postfix, authenticated sender kp) id 12CE24DA69; Wed, 9 Dec 2020 07:48:35 +0100 (CET) From: "Kristof Provost" To: Peter Cc: freebsd-stable@freebsd.org Subject: Re: Panic: 12.2 fails to use VIMAGE jails Date: Wed, 09 Dec 2020 07:48:35 +0100 X-Mailer: MailMate (1.13.2r5673) Message-ID: <36BBA671-835F-435B-AF79-0E82FE57C6E8@FreeBSD.org> In-Reply-To: References: <20201207125451.GA11406@gate.oper.dinoex.org> <39DBEA53-960F-4D70-86D7-847E6DFA437D@FreeBSD.org> <20201207233449.GA11025@gate.oper.dinoex.org> <1AAE98C9-ADF9-4869-B863-601542CEBB67@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8"; format=flowed Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Dec 2020 06:48:39 -0000 On 9 Dec 2020, at 2:31, Peter wrote: > On Tue, Dec 08, 2020 at 08:02:47PM +0100, Kristof Provost wrote: > > ! > Sorry for the bad news. > ! > > ! You appear to be triggering two or three different bugs there. > > That is possible. Then there are two or three different bugs in the > production code. > > In any case, my current workaround, i.e. delaying in the exec.poststop > >> exec.poststop = " >> sleep 6 ; >> /usr/sbin/ngctl shutdown ${ifname1l}: ; >> "; > > helps for it all and makes the system behave solid. This is true > with and without Your patch. > > ! Can you reduce your netgraph use case to a small test case that can > trigger > ! the problem? > > I'm sorry, I fear I don't get Your point. > Assumed there are actually two or three bugs here, You are asking me > to reduce config so that it will trigger only one of them? Is that > correct? > No, we need a simple case to reproduce these problems. It’s fine if that test case triggers multiple issues. > Then let me put this different: assuming this is the OS for the life > support system of the manned Jupiter mission. Then, which one of the > bugs do You want to get fixed, and which would You prefer to keep and > make Your oxygen supply cut off? > > https://www.youtube.com/watch?v=BEo2g-w545A > Happily we’re not in space. > > ! I’m not likely to be able to do anything unless I can reproduce > ! the problem(s). > > I understand that. > From Your former mail I get the impression that you prefer to rely > on tests. I consider this a bad habit[1] and prefer logical thinking. > > (Background: It is not that I would be unwilling to create clean and > precisely reproducible scenarious, But, one of my problems is > currently, I only have two machines availabe: the graphical one where > I'm just typing, and the backend server with the jails that does > practically everything. > These issues should trigger just fine in VMs. There’s no need for hardware pain. Regards, Kristof