Re: Shutdown -r under -current hangs on RPi3

bob prohaska <[email protected]>
Newsgroups gmane.os.freebsd.devel.arm
Message-ID <[email protected]>
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
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.