Re: Shutdown -r under -current hangs on RPi3
- Reply: bob prohaska : "Re: Shutdown -r under -current hangs on RPi3"
- In reply to: Mark Millard : "Re: Shutdown -r under -current hangs on RPi3"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Sat, 23 Sep 2023 18:34:41 UTC
On Sep 23, 2023, at 11:26, Mark Millard <marklmi@yahoo.com> wrote: > On Sep 23, 2023, at 08:52, bob prohaska <fbsd@www.zefox.net> wrote: > >> From time to time, but seemingly more often lately, a Pi3 >> get stuck during shutdown -r. The machine is running -current >> from a mechanical usb hard disk through a powered hub. No micro >> SD card is used. Once up it's quite stable. >> >> The console reports >> >> login: Sep 23 08:20:37 pelorus shutdown[224]: 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 >> Sep 23 08:20:43 pelorus 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... 4 0 0 0 done >> All buffers synced. >> Uptime: 23h31m45s >> Khelp module "ertt" can't unload until its refcount drops from 1 to 0. > > I've gotten the above message on rare occasions over the years on > the amd64 system (ThreadRipper 1950X). (But reboots and shutdowns > are not frequent for this system normally.) > > There is a recent: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=271677 > > It is not just your context with the issue. > >> Resetting system ... >> >> At that point all activity ceases. The only clue I can recognize is that >> the red power LED remains off, as if FreeBSD never relinquishes control >> to the Pi firmware, which turns the LED back on at powerup. Power-cycling >> results in a normal reboot. > The system might produce more messages about the shutdown activity if it has been booted via: boot -v This might narrow down the context some for someone familiar with the messages --if oyu are lucky enough to eventually get an example from a boot -v context. === Mark Millard marklmi at yahoo.com