From owner-freebsd-arm@freebsd.org Thu Jan 4 14:45:00 2018 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 26F51EB9553 for ; Thu, 4 Jan 2018 14:45:00 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [69.239.235.194]) (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 D23AD6C612 for ; Thu, 4 Jan 2018 14:44:59 +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 w04Eiu7W017463 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 4 Jan 2018 06:44:57 -0800 (PST) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.15.2/8.15.2/Submit) id w04Eita5017462; Thu, 4 Jan 2018 06:44:55 -0800 (PST) (envelope-from fbsd) Date: Thu, 4 Jan 2018 06:44:55 -0800 From: bob prohaska To: Mark Millard Cc: Freebsd-arm , bob prohaska Subject: Re: RPI2 boot hangs with red light on Message-ID: <20180104144455.GA17191@www.zefox.net> References: <20180102222730.GB10596@www.zefox.net> <3EE68320-8359-495D-AFCE-098A2220C6AE@dsl-only.net> <20180104023257.GA15177@www.zefox.net> <1515039689.1759.27.camel@freebsd.org> <20180104054236.GA15764@www.zefox.net> <802335D5-A961-4ABB-91D8-97B108106BEB@dsl-only.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <802335D5-A961-4ABB-91D8-97B108106BEB@dsl-only.net> 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: Thu, 04 Jan 2018 14:45:00 -0000 On Wed, Jan 03, 2018 at 11:08:06PM -0800, Mark Millard wrote: > > "unable to get device descriptor (error=-22)" is from > u-boot/blob/master/common/usb.c and its usb_new_device > routine from what I can tell. It's cause and > consequences might have contributed to the "Timeout > poll on interrupt endpoint" messages from u-boot. > > May be eliminating all the usb devices that you can > might sidestep some issue? > Excellent call, removing mouse, keyboard and pl2303TA adapter eliminate the timeout messages and make the console much easier to use. Only the USB flash drive holding /usr, /var, /tmp and swap remains. It looks as if u-boot and loader are both behaving reasonably; they respond to commands, with no extraneous output. A hands-off boot still fails silently with the red LED stuck on, for both /boot/kernel and /boot/kernel.spare. /boot/kernel.old, at r327228, _does_ boot, but with errors, like so: ..... Mounting late filesystems:. Jan 4 05:38:10 www kernel: pid 502 (cp), uid 0 inumber 53912 on /: filesystem full Configuring vt: blanktime. Performing sanity check on sshd configuration. Starting sshd. Starting sendmail. Starting sendmail_msp_queue. Starting cron. Starting background file system checks in 60 seconds. Thu Jan 4 05:38:13 PST 2018 FreeBSD/arm (www.zefox.com) (ttyu0) login: UFS /dev/ufs/rootfs (/) cylinder checksum failed: cg 0, cgp: 0x9e441246 != bp: 0xfa67bf3a UFS /dev/ufs/rootfs (/) cylinder checksum failed: cg 0, cgp: 0x9e441246 != bp: 0xfa67bf3a handle_workitem_freefile: got error 5 while accessing filesystem Login on the console worked, repeated fsck -f cycles permitted return to multi-user without errors. Sources are now updated to 327548, /boot/kernel.old has been copied over /boot/kernel.spare and a new cycle of build/install in /usr/src is running. Thanks _very_ much! bob prohaska