Date: Sun, 1 Oct 2023 09:25:23 -0700 From: bob prohaska <fbsd@www.zefox.net> To: freebsd-arm@freebsd.org Cc: bob prohaska <fbsd@www.zefox.net> Subject: Re: Shutdown -r under -current hangs on RPi3 Message-ID: <ZRmdczYolljhsuqE@www.zefox.net> In-Reply-To: <ZRBTIi28k8dWY5eX@www.zefox.net> References: <0AADDACB-ABA3-47FF-B3A7-05B313F5326C@yahoo.com> <9D29DD48-1572-4C04-AD88-8436AC8DDDCC@yahoo.com> <ZQ85fhHaO3xrfYjK@www.zefox.net> <D384C6AD-4FB0-4130-82E4-B923E1404401@yahoo.com> <ZQ9mFBvBP7rCqj6W@www.zefox.net> <B39FB168-7A0E-4E71-AA90-10D267307975@yahoo.com> <ZQ%2BNKZuvMwQteoCE@www.zefox.net> <88F77A9A-F3BB-4FEA-8330-EC5992D7B36B@yahoo.com> <ZQ%2BhlTcZMhaRD2hi@www.zefox.net> <ZRBTIi28k8dWY5eX@www.zefox.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Sep 24, 2023 at 08:17:54AM -0700, bob prohaska wrote: > > It appears that setting > debug.bootverbose=1 > suppresses the otherwise-persistent > Khelp module "ertt" can't unload until its refcount drops from 1 to 0. > message during shutdown. No new output either, apart from the swap > removal notice. > > So far, the few shutdown -r experiments tried have not gotten stuck, > even after an OS build/install cycle. Another shutdown hang has been observed with -current on a Pi3. This time bootverbose was on, as was ucom debug. This machine has an FTDI usb-serial adaper. The serial console reported: *** FINAL System shutdown message from bob@pelorus.zefox.org *** System going down IMMEDIATELY Oct 1 08:21:26 pelorus shutdown[78571]: reboot by bob: Stopping sshd. Waiting for PIDS: 1063. Stopping cron. Waiting for PIDS: 1073. Stopping powerd. Waiting for PIDS: 1002. Stopping devd. Waiting for PIDS: 752. Writing entropy file: . Writing early boot entropy file: . . Terminated ucom_inwakeup: tp=0xffffa00021cc1c00 ucom_ioctl: cmd = 0x2000740e ucom_inwakeup: tp=0xffffa00021cc1c00 ucom_inwakeup: tp=0xffffa00021cc1c00 ucom_close: tp=0xffffa00021cc1c00 ucom_shutdown: ucom_dtr: onoff = 0 ucom_line_state: on=0x00, off=0x01 ucom_rts: onoff = 1 ucom_line_state: on=0x02, off=0x00 Oct 1 08:21:32 pelorus ucom_cfg_close: syslogd: exiting on signal 15 Waiting (max 60 seconds) for system process `vnlru' to stop... done Waiting (max 60 seconds) for system process `syncer' to stop... Syncing disks, vnodes remaining... 0 0 0 done All buffers synced. Swap device da0s2b removed. Uptime: 3d0h14m47s Resetting system ... Both Ethernet LEDs turned off, if that's significant. After about half an hour, I pulled the plug. The machine came up hands-off. Thanks for reading, bob prohaska
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ZRmdczYolljhsuqE>