Date: Sun, 13 Jun 2021 16:08:43 -0500 From: Matthew Grooms <mgrooms@shrew.net> To: freebsd-arm@freebsd.org Subject: Re: arm64 stable/13 boot stuck Message-ID: <39b72240-92a1-3f24-9ce1-3fdcc24149d8@shrew.net> In-Reply-To: <26D60C14-9A4F-4E0B-8B1B-D26483AD7B55@fubar.geek.nz> References: <4affccce-080b-1108-a845-8e8811fa3bd7@shrew.net> <26D60C14-9A4F-4E0B-8B1B-D26483AD7B55@fubar.geek.nz>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi Andrew, I can confirm the issue has been resolved with that commit. Thanks for the fast response. -Matthew On 6/13/2021 2:18 PM, Andrew Turner wrote: > This should be fixed in ade8b810b02f. > > Andrew > >> On 12 Jun 2021, at 23:28, Matthew Grooms <mgrooms@shrew.net> wrote: >> >> I just updated my rpi4 kernel sources today and get this very early in my rpi4 boot output ... >> >> bcm_mbox_write: STATUS_FULL stuck >> >> If I roll back to 043f204985261d6daae69538c4609b3e143ee444 from yesterday, it boots fine again. I assume this is related to Andrew Turner's latest batch of arm64 commits. >> >> Thanks, >> -Matthew >> >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?39b72240-92a1-3f24-9ce1-3fdcc24149d8>