From nobody Wed Dec 06 19:02:41 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 4SlmxY4gkFz53plr for ; Wed, 6 Dec 2023 19:02:41 +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 4SlmxY0Pz8z3Gpq for ; Wed, 6 Dec 2023 19:02:40 +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 3B6J2gTt019620 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Wed, 6 Dec 2023 11:02:42 -0800 (PST) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.17.1/8.15.2/Submit) id 3B6J2fhs019619; Wed, 6 Dec 2023 11:02:41 -0800 (PST) (envelope-from fbsd) Date: Wed, 6 Dec 2023 11:02:41 -0800 From: bob prohaska To: Bob Bishop Cc: "freebsd-arm@freebsd.org" Subject: Re: RPi2 USB boot problems, maybe hardware? Message-ID: References: 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-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-Spamd-Bar: ---- X-Rspamd-Queue-Id: 4SlmxY0Pz8z3Gpq On Wed, Dec 06, 2023 at 04:37:39PM +0000, Bob Bishop wrote: > Hi, > > > On 6 Dec 2023, at 16:19, bob prohaska wrote: > > > > Since a recent build/install cycle a Pi2 v1.1 (armv7) has stopped > > booting stable/14. > > [ ... ] > > The failure to enumerate more USB devices seems odd. > > [ ... ] > > > > Thanks for reading, any suggestions appreciated! > > Check your power supplies. With the machine up, running and idling I see 5.06 volts. When shutdown -r is issued on the console the voltage rises to 5.13 with the red power LED on steadily. Meanwhile, the Pi reports root@www:~ # shutdown -r now Shutdown NOW! shutdown: [pid 1420] root@www:~ # Stopping apache24. Waiting for PIDS: 1093. Stopping cron. Waiting for PIDS: 1078. Stopping sshd. Waiting for PIDS: 1075. Stopping devd. Waiting for PIDS: 774. Writing entropy file: . Writing early boot entropy file: . . Terminated Dec 6 10:40:25 www 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 done All buffers synced. Swap device da0s2b removed. Uptime: 2h35m33s Resetting system ... U-Boot 2023.07.02 (Aug 25 2023 - 05:50:16 +0000) DRAM: 948 MiB RPI 2 Model B (0xa21041) Core: 75 devices, 12 uclasses, devicetree: board MMC: mmc@7e300000: 1 Loading Environment from FAT... ** Bad device specification mmc 0 ** In: serial Out: vidconsole Err: vidconsole Net: No ethernet found. starting USB... Bus usb@7e980000: USB DWC2 scanning bus usb@7e980000 for devices... cannot reset port 1!? 1 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found Hit any key to stop autoboot: 0 MMC Device 0 not found no mmc device at slot 0 switch to partitions #0, OK mmc1 is current device Scanning mmc 1:1... No EFI system partition No EFI system partition Failed to persist EFI variables BootOrder not defined EFI boot manager: Cannot load any image MMC Device 2 not found no mmc device at slot 2 Device 0: unknown device No ethernet found. missing environment variable: pxeuuid Retrieving file: pxelinux.cfg/00000000 No ethernet found. Retrieving file: pxelinux.cfg/0000000 No ethernet found. Retrieving file: pxelinux.cfg/000000 No ethernet found. Retrieving file: pxelinux.cfg/00000 No ethernet found. Retrieving file: pxelinux.cfg/0000 No ethernet found. Retrieving file: pxelinux.cfg/000 No ethernet found. Retrieving file: pxelinux.cfg/00 No ethernet found. Retrieving file: pxelinux.cfg/0 No ethernet found. Retrieving file: pxelinux.cfg/default-arm-bcm283x-rpi No ethernet found. Retrieving file: pxelinux.cfg/default-arm-bcm283x No ethernet found. Retrieving file: pxelinux.cfg/default-arm No ethernet found. Retrieving file: pxelinux.cfg/default No ethernet found. Config file not found No ethernet found. No ethernet found. U-Boot> usb info reports only the hub: U-Boot> usb info 1: Hub, USB Revision 1.10 - U-Boot Root Hub - Class: Hub - PacketSize: 8 Configurations: 1 - Vendor: 0x0000 Product 0x0000 Version 0.0 Configuration: 1 - Interfaces: 1 Self Powered 0mA Interface: 0 - Alternate Setting 0, Endpoints: 1 - Class Hub - Endpoint 1 In Interrupt MaxPacket 2 Interval 255ms U-Boot> This doesn't look like a power supply problem to me. The Pi gets far enough to spin up the disk, find u-boot and run it. Only then does it run into trouble. The error messages that are presented are always so. Perhaps they're symptoms of some other, underlying, problems? Thanks for reading! bob prohaska