From nobody Mon Oct 02 16:17:34 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 4RzmMB0Lx5z4wFD5 for ; Mon, 2 Oct 2023 16:17:42 +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 4RzmM93vJ1z4MfN for ; Mon, 2 Oct 2023 16:17:41 +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 392GHZh5073833 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Mon, 2 Oct 2023 09:17:35 -0700 (PDT) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.17.1/8.15.2/Submit) id 392GHZ8x073832; Mon, 2 Oct 2023 09:17:35 -0700 (PDT) (envelope-from fbsd) Date: Mon, 2 Oct 2023 09:17:34 -0700 From: bob prohaska To: Mark Millard Cc: freebsd-arm@freebsd.org Subject: Pi3 shutdown -p [Was: Re: Shutdown -r under -current hangs on RPi3] Message-ID: References: <88F77A9A-F3BB-4FEA-8330-EC5992D7B36B@yahoo.com> <7B1D2B1C-C580-448B-BEB9-51D07417C62D@yahoo.com> <7EAAF93E-A7FF-477C-AE02-154828E9F3A7@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: <7EAAF93E-A7FF-477C-AE02-154828E9F3A7@yahoo.com> 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: 4RzmM93vJ1z4MfN [subject changed to reflect topic drift] On Sun, Oct 01, 2023 at 09:12:17PM -0700, Mark Millard wrote: > > My understanding is that the RPi3B's SOC can be powered off without > cutting the external power, leaving much of the board also powered > off despite external power. (Simplified wording.) In other words, > "shutdown -p now" has a chance of being made to largely work, if I > understand right. > Ahh, that's borne out with one of my Pi3s. It appears to be a one-way ticket, however: Ethernet status LEDs off, power LEDs on, no console response. Moreover, after power-cycling, boot stoped at the loader with an OK prompt. The next boot -r came up with a live console but still stopped at the loader prompt, proceeding only after two "boot" commands. The first was unrecognized, the second ran. It seems as if something is contaminating the console input, causing a pause at the loader prompt or corrupting the initial input. It's perhaps unfortunate, but the first Pi3 described gets its terminal service from the second, both of which have ftdi usb-serial adapters. Both exhibit stray characters when establishing a serial console connection to another host. > If the USB disk is bus powered, that stuck-on may indicate that the > SOC/board is still powered. (Not just in the external supply > sense, but operationally using that external power still.) > In both cases the disks are on a powered hub. The hub and Pi are on the same cord and so power-cycle together, but the disk isn't reliant the Pi3's power. For some months now the first particular Pi3 seems to display console output at what looks like a 9600 baud rate, though the connection via cu or tip uses 115200 baud. I've ignored it thus far, but maybe there's more going on than meets the eye. It's the same Pi3 that displayed the duplicate MAC address problem. Thanks for writing! bob prohaska