Date: Tue, 6 Oct 2020 14:59:26 -0400 From: Ed Maste <emaste@freebsd.org> To: freebsd-arm <freebsd-arm@freebsd.org> Subject: Re: BBB boot failure between r366365 and r366386 Message-ID: <CAPyFy2DmN4xUPWf3yN4Y=bq=LTfWu2QPOmKx8s4UHHEP5sHpNA@mail.gmail.com> In-Reply-To: <CAPyFy2A2KKH4sKS1yeQR6PvYtQJBUhDnWg_yE%2BmqkCjxHZ-A8w@mail.gmail.com> References: <CAPyFy2CHdEuPL4jaGdCzwacK2p3CbhfybOcPHPHQETd=NqFjyQ@mail.gmail.com> <CAPyFy2A2KKH4sKS1yeQR6PvYtQJBUhDnWg_yE%2BmqkCjxHZ-A8w@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 5 Oct 2020 at 15:56, Ed Maste <emaste@freebsd.org> wrote: > > On Mon, 5 Oct 2020 at 09:53, Ed Maste <emaste@freebsd.org> wrote: > > > > Sometime after r366365 and up to r366365 BBB stopped booting in the HW > > test environment. > > That should of course be after r366365 and up to (and including) > r366386. Discussed on IRC; the second U-Boot banner comes out ~60s after the first, which might suggest a watchdog timeout. We seem to get stuck after > random: unblocking device.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAPyFy2DmN4xUPWf3yN4Y=bq=LTfWu2QPOmKx8s4UHHEP5sHpNA>