From owner-freebsd-arm@freebsd.org Sat Mar 24 18:15:47 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 0155AF6239D; Sat, 24 Mar 2018 18:15:47 +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 4D9D3782D4; Sat, 24 Mar 2018 18:15:46 +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 w2OIFmhw025320 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sat, 24 Mar 2018 11:15:49 -0700 (PDT) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.15.2/8.15.2/Submit) id w2OIFleb025319; Sat, 24 Mar 2018 11:15:47 -0700 (PDT) (envelope-from fbsd) Date: Sat, 24 Mar 2018 11:15:47 -0700 From: bob prohaska To: Ian Lepore Cc: bob prohaska , FreeBSD CURRENT , freebsd-arm@freebsd.org Subject: Re: CURRENT r331284: crashing with USB Message-ID: <20180324181547.GB25188@www.zefox.net> References: <20180321120710.4eb3b944@hermann> <20180322044934.GA13553@www.zefox.net> <20180324173912.GA25188@www.zefox.net> <1521913937.51564.20.camel@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1521913937.51564.20.camel@freebsd.org> User-Agent: Mutt/1.5.24 (2015-08-30) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 24 Mar 2018 18:15:47 -0000 On Sat, Mar 24, 2018 at 11:52:17AM -0600, Ian Lepore wrote: > > Those snippets are some of the first things uboot says when it starts. > > -- Ian Yes, understood. The initial console text flooded off the terminal scrollback, so it couldn't be captured. The portion selected was meant mostly to relieve suspicions it was a serial malfunction of some kind, copied after several attempts to reboot. It was quite surprising to see the flood of nonsense persist after a shutdown -r now had been issued, and apparently acted upon (the controlling shell exited, but the console flood continued). The console flood came back after a quick power disconnect/reconnect, but finally stopped when the power was left off for a minute or so. Then all returned to normal. Thanks for reading! bob prohaska