From nobody Thu Sep 23 15:43:01 2021 X-Original-To: freebsd-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 EB5F317D287C for ; Thu, 23 Sep 2021 15:43:11 +0000 (UTC) (envelope-from junchoon@dec.sakura.ne.jp) Received: from www121.sakura.ne.jp (www121.sakura.ne.jp [153.125.133.21]) (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 did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4HFfZQ573zz4tms for ; Thu, 23 Sep 2021 15:43:10 +0000 (UTC) (envelope-from junchoon@dec.sakura.ne.jp) Received: from kalamity.joker.local (123-48-130-181.area1b.commufa.jp [123.48.130.181]) (authenticated bits=0) by www121.sakura.ne.jp (8.16.1/8.16.1/[SAKURA-WEB]/20201212) with ESMTPA id 18NFh1gD017604 for ; Fri, 24 Sep 2021 00:43:01 +0900 (JST) (envelope-from junchoon@dec.sakura.ne.jp) Date: Fri, 24 Sep 2021 00:43:01 +0900 From: Tomoaki AOKI To: freebsd-current@freebsd.org Subject: Re: latest current fails to boot. Message-Id: <20210924004301.4b16fa28619ed5191b331be9@dec.sakura.ne.jp> In-Reply-To: <20210922230905.79a494a4ddbecd7d6b8179ea@dec.sakura.ne.jp> References: <20210922230905.79a494a4ddbecd7d6b8179ea@dec.sakura.ne.jp> Reply-To: junchoon@dec.sakura.ne.jp Organization: Junchoon corps X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.33; amd64-portbld-freebsd13.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: 4HFfZQ573zz4tms X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of junchoon@dec.sakura.ne.jp has no SPF policy when checking 153.125.133.21) smtp.mailfrom=junchoon@dec.sakura.ne.jp X-Spamd-Result: default: False [-1.59 / 15.00]; HAS_REPLYTO(0.00)[junchoon@dec.sakura.ne.jp]; RCVD_VIA_SMTP_AUTH(0.00)[]; MV_CASE(0.50)[]; REPLYTO_ADDR_EQ_FROM(0.00)[]; TO_DN_NONE(0.00)[]; HAS_ORG_HEADER(0.00)[]; NEURAL_HAM_SHORT(-1.00)[-1.000]; FROM_EQ_ENVFROM(0.00)[]; RCVD_TLS_LAST(0.00)[]; R_DKIM_NA(0.00)[]; ASN(0.00)[asn:7684, ipnet:153.125.128.0/18, country:JP]; MIME_TRACE(0.00)[0:+]; MID_RHS_MATCH_FROM(0.00)[]; RECEIVED_SPAMHAUS_PBL(0.00)[123.48.130.181:received]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.99)[-0.990]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; AUTH_NA(1.00)[]; RCPT_COUNT_ONE(0.00)[1]; DMARC_NA(0.00)[sakura.ne.jp]; R_SPF_NA(0.00)[no SPF record]; RCVD_COUNT_TWO(0.00)[2] X-ThisMailContainsUnwantedMimeParts: N On Wed, 22 Sep 2021 23:09:05 +0900 Tomoaki AOKI wrote: > On Wed, 22 Sep 2021 05:47:46 -0700 > David Wolfskill wrote: > > > On Wed, Sep 22, 2021 at 02:39:37PM +0200, Johan Hendriks wrote: > > > I did a git pull this morning and it fails to boot. > > > I hangs at Setting hostid : 0x917bf354 > > > > > > This is a vm running on vmware. > > > If i boot the old kernel from yesterday it boots normally. > > > > > > uname -a > > > FreeBSD varnish-cdn-node03 14.0-CURRENT FreeBSD 14.0-CURRENT #0 > > > main-n249518-5572fda3a2f: Tue Sep 21 14:40:22 CEST 2021 > > > root@varnish-cdn-node03:/usr/obj/usr/src/amd64.amd64/sys/KRNL amd64 > > > .... > > > > I had no issues with my build machine or either of two laptops, either > > from yesterday: > > > > FreeBSD g1-55.catwhisker.org 14.0-CURRENT FreeBSD 14.0-CURRENT #358 main-n249518-5572fda3a2f3: Tue Sep 21 05:15:22 PDT 2021 root@g1-55.catwhisker.org:/common/S4/obj/usr/src/amd64.amd64/sys/CANARY amd64 1400033 1400033 > > > > or today: > > > > FreeBSD g1-55.catwhisker.org 14.0-CURRENT FreeBSD 14.0-CURRENT #359 main-n249556-c96da1994587: Wed Sep 22 04:24:17 PDT 2021 root@g1-55.catwhisker.org:/common/S4/obj/usr/src/amd64.amd64/sys/CANARY amd64 1400033 1400033 > > > > [uname strings from my main laptop shown, but I keep the machines > > in sync rather aggressively.] > > > > Perhaps the issue you are encountering involves things not in my > > environment (such as VMs or ZFS)? > > > > Peace, > > david > > -- > > David H. Wolfskill david@catwhisker.org > > Life is not intended to be a zero-sum game. > > > > See https://www.catwhisker.org/~david/publickey.gpg for my public key. > > For me, on bare metal (non-vm) amd64 with root-on-ZFS, > > Fails to boot to multiuser at git: 8db1669959ce > Boot fine at git: 0b79a76f8487 > > Boot to singleuser is fine even with failed revision. > > Failure mode: > Hard hangup or spinning and non-operable. Hard power-off needed. > Seems to happen after starting rc.conf processing and before setting > hostid. > > -- > Tomoaki AOKI > Additional info and correction. *Hung up before setting hostuuid, not hostid. *^T doesn't respond at all, only hard power off worked. *`kldload nvidia-modeset.ko` on single user mode sanely work. Why I could know rc.conf is started to be processed: I have lines below at the end of /etc/rc.conf and its output is always the first line related to /etc/rc.conf, at least for non-verbose boot. The next line is normally "Setting hostuuid: " line, which was not displayed when boot hung up. kldstat -q -n nvidia.ko if [ 0 -ne $? ] ; then echo "Loading nvidia-driver modules via rc.conf." if [ -e /boot/modules/nvidia-modeset.ko ] ; then kld_list="${kld_list} nvidia-modeset.ko" else kld_list="${kld_list} nvidia.ko" fi fi -- Tomoaki AOKI