From owner-freebsd-arm@freebsd.org Wed Sep 5 16:03:48 2018 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id AD544FF4F99 for ; Wed, 5 Sep 2018 16:03:48 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [50.1.20.27]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "www.zefox.org", Issuer "www.zefox.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 2AD9A8801A for ; Wed, 5 Sep 2018 16:03:47 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (localhost [127.0.0.1]) by www.zefox.net (8.15.2/8.15.2) with ESMTPS id w85G3c6T000975 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 5 Sep 2018 09:03:39 -0700 (PDT) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.15.2/8.15.2/Submit) id w85G3cd7000974; Wed, 5 Sep 2018 09:03:38 -0700 (PDT) (envelope-from fbsd) Date: Wed, 5 Sep 2018 09:03:37 -0700 From: bob prohaska To: freebsd-arm@freebsd.org Subject: Checking USB ports on RPI2 Message-ID: <20180905160337.GA818@www.zefox.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.24 (2015-08-30) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Sep 2018 16:03:48 -0000 It looks as if one of the USB ports on an RPI2 has quit working. Other ports seem to work normally, is there test utility of some sort that can be used to explore in greater depth what might be going on? The machine had been idling largely unused for some weeks running FreeBSD www.zefox.com 11.2-STABLE FreeBSD 11.2-STABLE #0 r337511: Thu Aug 9 12:21:02 PDT 2018 bob@www.zefox.com:/usr/obj/usr/src/sys/RPI2 arm This morning there was a (very) brief power outage, just enough to scramble a few of the plug-in digital clocks in the house. The RPI2 was found stuck in single-user mode with /dev/da0 missing in /dev. Since /var, /tmp, /usr and swap all live on da0 that much made sense. A soft reboot from the serial console again got stuck in single-user, again with no /dev/da0. Power-cycling had the same result. Moving the flash drive to the adjacent USB port allowed a normal boot, putting it back in the old position re-created the previous failure. So, it seems the trouble is the port, not the flash drive. Initially I expected the failure to be in the drive, it has been in continuous use, mostly testing buildworld/kernel, for around two years. That the trouble seems to be in the RPI2 is a great surprise which I'd like to explore a little more carefully if it's possible. Viewed from the connector end of the Pi, with the Ethernet jack at the top, the bad port is upper right, the working port is upper left. There are three other RPI2's and one RPI3 in the cluster, the rest of which seem to be working normally. >From this I infer that the power outage was the trigger, but not the cause of the problem. Thanks for reading, and any ideas. bob prohaska