From nobody Mon Jul 26 06:19:41 2021 X-Original-To: current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 2B097127B036 for ; Mon, 26 Jul 2021 06:19:45 +0000 (UTC) (envelope-from gljennjohn@gmail.com) Received: from mail-ej1-x632.google.com (mail-ej1-x632.google.com [IPv6:2a00:1450:4864:20::632]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4GY8sX1SJGz4vq3 for ; Mon, 26 Jul 2021 06:19:44 +0000 (UTC) (envelope-from gljennjohn@gmail.com) Received: by mail-ej1-x632.google.com with SMTP id o5so14832845ejy.2 for ; Sun, 25 Jul 2021 23:19:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:cc:subject:message-id:in-reply-to:references:reply-to :mime-version:content-transfer-encoding; bh=a5vX8gBmnnic5UNWxw1jVpXm3AHKRfRAvnIGLKq3V6c=; b=mK0BbuIgBcwT9I4HhmcWx8fAbwi09YCoG1EwRUswzfViYAo6ZPQg0G7J+okKHuxmWa ojFXtwKps8E0A+1t6Hpyqkt8vGorpWWjL/GkRJAnTbtKn9Cx1Q1KeLy17mMivnlvq0SR Z7ZDXubpnQYOh7eOJC1WaZd8n/X7mX1OcmnQ21hEkIf0YyO6L8max7tcaMGxULWbXqe7 w2eziJyBayKfPkblyVl4uh/dVoJc1FOdsCsh3h121PXEC99YbtSTBxRbQkOAk8enXz9o UrF3xtC2a+2G7dAlGheUso21+gHV1j0G91zj8WYelFtQ0xitY55k8pQmmnVUwTJMKIEC CD6Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:in-reply-to :references:reply-to:mime-version:content-transfer-encoding; bh=a5vX8gBmnnic5UNWxw1jVpXm3AHKRfRAvnIGLKq3V6c=; b=KBQteoi6AT7DnUetUJrpLQI6yV4TUv3KiE4VOfDJY4VC++ldjLjifbyRTY2yUZsN53 mJxBGXD/cpLIf0raOkN4gvRuqfwNBAhd2sbmSpO0jcUctGvgrq9cRTQg+eVnhSCd54y0 8tKjfU54Z8ksyhKHpHHxPNRaZp4V5yD/OdoQbMTbCx1Lzq2A3Gnd8tQ13RMtR7QD4dWg /qX/ItCAhx3fwqBwBjOG5LVQ4UFxuX9N2F42m9KEJ8aTQMewpev2RdJLzyJsG42fCmIU gsw5bGziwkw2PfWDxCiyy1DGqdsZWD7jBHqC4UyWawbApHe0xlHHnvsOSexFYkbIaOKh HE9A== X-Gm-Message-State: AOAM533C5Di1tCtkotT/7lPe1SJqBKrDqfq+oIX/sP2YrE3eLMOCljtd kM9yRTY6tZPMmUXoG3yVmMI= X-Google-Smtp-Source: ABdhPJylcFYmZ6iqSRQopQ2pllHuhujt5uPvh1MNPaUrW0muz1YXuDf2fFkuUrQT21nyDYD5pWFnGw== X-Received: by 2002:a17:906:c836:: with SMTP id dd22mr4699918ejb.3.1627280383113; Sun, 25 Jul 2021 23:19:43 -0700 (PDT) Received: from ernst.home (pd9e2360f.dip0.t-ipconnect.de. [217.226.54.15]) by smtp.gmail.com with ESMTPSA id x2sm17419555edj.37.2021.07.25.23.19.41 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sun, 25 Jul 2021 23:19:42 -0700 (PDT) Date: Mon, 26 Jul 2021 08:19:41 +0200 From: Gary Jennejohn To: Warner Losh Cc: FreeBSD Current Subject: Re: boot hangs after installworld at FreeBSD 14.0-CURRENT main-n248198-72f7ddb587a Message-ID: <20210726061941.3daf514e@ernst.home> In-Reply-To: <20210725170229.50621855@ernst.home> References: <20210725092848.6f64b2d3@ernst.home> <20210725170229.50621855@ernst.home> Reply-To: gljennjohn@gmail.com X-Mailer: Claws Mail 3.17.8 (GTK+ 2.24.33; amd64-portbld-freebsd14.0) List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4GY8sX1SJGz4vq3 X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=mK0BbuIg; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of gljennjohn@gmail.com designates 2a00:1450:4864:20::632 as permitted sender) smtp.mailfrom=gljennjohn@gmail.com X-Spamd-Result: default: False [-1.89 / 15.00]; HAS_REPLYTO(0.00)[gljennjohn@gmail.com]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36:c]; FREEMAIL_FROM(0.00)[gmail.com]; REPLYTO_ADDR_EQ_FROM(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; RCPT_COUNT_TWO(0.00)[2]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; NEURAL_HAM_SHORT(-0.89)[-0.894]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim]; ARC_NA(0.00)[]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; RECEIVED_SPAMHAUS_PBL(0.00)[217.226.54.15:received]; FROM_HAS_DN(0.00)[]; MIME_GOOD(-0.10)[text/plain]; FREEMAIL_REPLYTO(0.00)[gmail.com]; PREVIOUSLY_DELIVERED(0.00)[current@freebsd.org]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[2a00:1450:4864:20::632:from]; RCVD_TLS_ALL(0.00)[]; MAILMAN_DEST(0.00)[current] X-ThisMailContainsUnwantedMimeParts: N On Sun, 25 Jul 2021 19:02:29 +0200 Gary Jennejohn wrote: > On Sun, 25 Jul 2021 09:54:35 -0600 > Warner Losh wrote: > > > On Sun, Jul 25, 2021 at 3:30 AM Gary Jennejohn wrote: > > > > > I updated my FBSD-14 tree yesterday. > > > > > > uname -a shows FreeBSD 14.0-CURRENT #5 main-n248198-72f7ddb587a. > > > > > > Did a buildkernel and a clean buildworld yesterday. > > > > > > This morning I booted the new kernel, did an installworld and rebooted > > > the new kernel. > > > > > > Or, should I say, I tried to reboot the new kernel. > > > > > > During boot I see the following outptut: > > > > > > loading /boot/defaults/loader.conf > > > / > > > > > > and the boot hangs. > > > > > > The second line should have contained > > > /boot/test/kernel (I always install new kernels to /boot/test) > > > > > > followed by lines containing the various modules which get loaded. > > > > > > Luckily, I had a USB thumb drive with a FreeBSD memstick.img AND a > > > complete backup of the old /boot, so I could boot from the thumb > > > drive and restore /boot (but I moved /boot to /boot.bad before I > > > did that just in case). With the restored (old) /boot everything > > > works. > > > > > > > Little has changed in the boot loader. Do you know the hash that worked? Or > > if I misread above, the has that failed? > > > > The /boot code which works was installed at 07:36 UTC July 9th. So, > every change to the boot code since then is a culprit. > > Example: 9c1c02093b90ae49745a174eb26ea85dd1990eec change to support.4th. > It just so happens that I had a nextboot.conf in the "bad" /boot at the > time that the hang occurred. This is the only potential candidate I > can see. > > So I'll try overwriting support.4th with the known-good version and > see what happens. But probably not until tomorrow my time. > After deleting the nextboot.conf from the "bad" /boot I was able to boot using the "bad" /boot. That's the only change between this boot and the previous boot which hung the computer. Whether this is a strong hint that the change to support.4th is the culprit I can't say, but since the commit message explicitly mentions nextboot.conf as a reason for the change, that may very well be the case. I decided that removing nextboot.conf was a better test than using the old support.4th. The change looks very simple and innocent, but my 4th knowledge is pretty much non-existent, so I don't really understand what it does. I went back to the "old" /boot because I use nextboot.conf a lot. -- Gary Jennejohn