From nobody Sun Sep 24 01:13:13 2023 X-Original-To: freebsd-arm@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 4RtSgJ0zydz4vXTx for ; Sun, 24 Sep 2023 01:13:16 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [50.1.20.27]) (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 (2048 bits) client-digest SHA256) (Client CN "www.zefox.com", Issuer "www.zefox.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4RtSgH5BCwz4P5c for ; Sun, 24 Sep 2023 01:13:15 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Authentication-Results: mx1.freebsd.org; none Received: from www.zefox.net (localhost [127.0.0.1]) by www.zefox.net (8.17.1/8.15.2) with ESMTPS id 38O1DD47036682 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Sat, 23 Sep 2023 18:13:13 -0700 (PDT) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.17.1/8.15.2/Submit) id 38O1DDhS036681; Sat, 23 Sep 2023 18:13:13 -0700 (PDT) (envelope-from fbsd) Date: Sat, 23 Sep 2023 18:13:13 -0700 From: bob prohaska To: Mark Millard Cc: freebsd-arm@freebsd.org Subject: Re: Shutdown -r under -current hangs on RPi3 Message-ID: References: <0AADDACB-ABA3-47FF-B3A7-05B313F5326C@yahoo.com> <9D29DD48-1572-4C04-AD88-8436AC8DDDCC@yahoo.com> List-Id: Porting FreeBSD to ARM processors List-Archive: https://lists.freebsd.org/archives/freebsd-arm List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arm@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:7065, ipnet:50.1.16.0/20, country:US] X-Rspamd-Queue-Id: 4RtSgH5BCwz4P5c On Sat, Sep 23, 2023 at 03:51:47PM -0700, Mark Millard wrote: > > # sysctl -Wd debug.bootverbose > debug.bootverbose: Control the output of verbose kernel messages > > So use of: > > # sysctl debug.bootverbose=1 > > before shutdown may be a way of controlling it later, after > having already booting. This might be handy if one forgot > to do the the boot -v at boot time. > Ahh, so I was being dense.... sysctl never crossed my mind. I've added sysctl debug.bootverbose=1 to /etc/sysctl.conf and rebooted. The reboot completed without complaints about errt, but as it came up multiuser the console reported: sysctl: unknown oid 'sysctl debug.bootverbose' at line 11 However, if I type sysctl debug.bootverbose=1 while logged in as root I see root@pelorus:~ # sysctl debug.bootverbose=1 debug.bootverbose: 0 -> 1 root@pelorus:~ # So, for some reason the command has to be entered interactively, at least for now. Rebooting with shutdown -r reported swap device removal. The errt complaint remained absent. There's something odd about sysctl debug.bootverbose. For example: root@pelorus:~ # sysctl -a | grep -i bootverbose <118>sysctl: unknown oid 'sysctl debug.bootverbose' at line 11 debug.bootverbose: 0 root@pelorus:~ # sysctl debug.bootverbose debug.bootverbose: 0 root@pelorus:~ # sysctl debug.bootverbose=1 debug.bootverbose: 0 -> 1 root@pelorus:~ # Am I committing some invisible (to me) typo? Thanks for writing! bob prohaska