Date: Sun, 13 Jun 2021 20:18:13 +0100 From: Andrew Turner <andrew@fubar.geek.nz> To: Matthew Grooms <mgrooms@shrew.net> Cc: freebsd-arm@freebsd.org Subject: Re: arm64 stable/13 boot stuck Message-ID: <26D60C14-9A4F-4E0B-8B1B-D26483AD7B55@fubar.geek.nz> In-Reply-To: <4affccce-080b-1108-a845-8e8811fa3bd7@shrew.net> References: <4affccce-080b-1108-a845-8e8811fa3bd7@shrew.net>
next in thread | previous in thread | raw e-mail | index | archive | help
--Apple-Mail=_EA4F137B-1CD6-4302-AB72-6D3C1916CCFA Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii This should be fixed in ade8b810b02f. Andrew > On 12 Jun 2021, at 23:28, Matthew Grooms <mgrooms@shrew.net> wrote: >=20 > I just updated my rpi4 kernel sources today and get this very early in = my rpi4 boot output ... >=20 > bcm_mbox_write: STATUS_FULL stuck >=20 > 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. >=20 > Thanks, > -Matthew >=20 --Apple-Mail=_EA4F137B-1CD6-4302-AB72-6D3C1916CCFA--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?26D60C14-9A4F-4E0B-8B1B-D26483AD7B55>