From nobody Mon Jul 26 16:17:36 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 4454E127816F for ; Mon, 26 Jul 2021 16:17:56 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-qk1-x735.google.com (mail-qk1-x735.google.com [IPv6:2607:f8b0:4864:20::735]) (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 4GYQ7l71Z7z3r7F for ; Mon, 26 Jul 2021 16:17:55 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-qk1-x735.google.com with SMTP id t66so9412911qkb.0 for ; Mon, 26 Jul 2021 09:17:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=I+hQEvowRnNbA8qvcoo4+E4GDJ6eegVbIVinrpqcCvI=; b=uESUhv909W6h25vkIuNfFzOy8FYSWgxUr2RBsb3hb3Nm+ZlaYtcpg77si/uxhnXVWX 0CzOKJpD35mdBLOj5RKyIZTwEHIRLUaUq/GMOtXUjfA3wRcGlJq8L9nDDkc8phH5cTuL i9yGoxfE5T4giVOkYjM1AVEBmCshLF03akzLTNiYN8XxA9TLRL9m9KpG/42NbULssAfw XSnFe8wCxSarFWud2JEo+bMJr4jupAXDqszXzNclg2Oecvw6AUrVirhHYHS8tJw0Xf+0 GQNyJCphYvwoBE9FwsBDno+mC0OGtoDE3rii4tclrO/hgoHNqAYnMNeDU6PghEyyranj jz9A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=I+hQEvowRnNbA8qvcoo4+E4GDJ6eegVbIVinrpqcCvI=; b=lnhCOU3DwSEKETjm6cBEMiUKun5L3gDhwKeWl/fyssugBiQFXt8W0tFC41ika2bVdp zeeYz0b7tYGZBVcbExBbWNL9U0Q+aUQxRa7DQTdqAY4h1w51ItO2oZPueZRDJdzwVThJ 6jZYA427t1sb85oGJ6wsyyhJ0qPrVRY5zf/RnFMyJ1MFCeWp45zOwAOLsio+eL904PwU eoeQId6mh+5IPldeYo9ZXb0AObot5KYg9oxgeV5To/ln/QlJcURUePoARwIiY/G66G7/ GMqvFVu9dyNFru5pdYRQ4PaXHVa3mGCtLGsRyD3kHCtmK0U+F4W9W4pK61yIcEkhHKnL wxwg== X-Gm-Message-State: AOAM532GcVKC5AYuSl/n3vZUCn5cg5vtOtfxdT/fr4dCjn8rSK2nbNct 4hHZgng+4p3tXU7KyWgp9CXzRSAUh92SW9QZGMq2sg== X-Google-Smtp-Source: ABdhPJwQzYpL+fM04Saehf/ioq9Hg8+6TzjA8ZfRgYM1dDQnNTDdz5yOZh/+SYnYhC0MVxliyav752byOKB+MJJ9whM= X-Received: by 2002:a05:620a:45:: with SMTP id t5mr17258030qkt.206.1627316268823; Mon, 26 Jul 2021 09:17:48 -0700 (PDT) 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 References: <20210725092848.6f64b2d3@ernst.home> <20210725170229.50621855@ernst.home> <20210726061941.3daf514e@ernst.home> <20210726091319.213dd5ed@ernst.home> In-Reply-To: <20210726091319.213dd5ed@ernst.home> From: Warner Losh Date: Mon, 26 Jul 2021 10:17:36 -0600 Message-ID: Subject: Re: boot hangs after installworld at FreeBSD 14.0-CURRENT main-n248198-72f7ddb587a To: Gary Jennejohn Cc: FreeBSD Current Content-Type: multipart/alternative; boundary="000000000000240b1b05c809186d" X-Rspamd-Queue-Id: 4GYQ7l71Z7z3r7F X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-ThisMailContainsUnwantedMimeParts: Y --000000000000240b1b05c809186d Content-Type: text/plain; charset="UTF-8" On Mon, Jul 26, 2021, 3:13 AM Gary Jennejohn wrote: > On Mon, 26 Jul 2021 08:19:41 +0200 > Gary Jennejohn wrote: > > > 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. > > > > I decided to do a further test. > > I wanted to check whether some other change in the loader might be > implicated in the hung boot. > > I copied the old support.4th to the bad /boot (/boot.b). I then mv'd > /boot to /boot.g and /boot.b to /boot and created a nextboot.conf > there. After these steps I was still able to boot successfully. > > So, I'd say that this result is a pretty strong indication that the > new support.4th together with a nextboot.conf results in the hung > boot. > Ok. I'll revert when I'm next at a keyboard... Warner > --000000000000240b1b05c809186d--