Date: Thu, 21 Sep 2023 14:47:29 +0000 From: "John F Carr" <jfc@mit.edu> To: Mark Millard <marklmi@yahoo.com> Cc: FreeBSD ARM List <freebsd-arm@freebsd.org>, Andrew Turner <andrew@freebsd.org> Subject: Re: How to Boot FreeBSD Using pftf/RPi4 UEFI Message-ID: <11D022AB-87B0-4271-B469-8D5BA6BD398A@mit.edu> In-Reply-To: <B611BF0F-05FD-48E1-85E9-F41B898B6AD7@yahoo.com> References: <CA%2BPGaYCCNOXPy_b-N=OvcAoQnN1WyhiLLe-a0cj9g=-3r0QCDw@mail.gmail.com> <A3A36C5F-1EFA-4F94-AD5C-374C01C3ED68@yahoo.com> <B611BF0F-05FD-48E1-85E9-F41B898B6AD7@yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> On Sep 21, 2023, at 05:26, Mark Millard <marklmi@yahoo.com> wrote: >=20 > [Andrew T.: for main this lead to > "panic: Assertion smccc_version !=3D 0 . . ." > for today's new snapshot.] I get the same error booting a fresh kernel on my Overdrive 1000 which doesn't have any of the Pi-related boot weirdness. Commits c643e82dba0b17b2716de4c9d44a3c9c547cbbd5 and 8a723e2bd8683b0e046ed9d03178082f84c8cf26 are relevant. KDB: stack backtrace: db_trace_self() at db_trace_self db_trace_self_wrapper() at db_trace_self_wrapper+0x30 vpanic() at vpanic+0x1a0 panic() at panic+0x44 smccc_arch_features() at smccc_arch_features+0x80 install_cpu_errata() at install_cpu_errata+0x4c cpu_startup() at cpu_startup+0xac mi_startup() at mi_startup+0x1dc virtdone() at virtdone+0x70 KDB: enter: panic [ thread pid 0 tid 0 ] Stopped at kdb_enter+0x44: undefined f905827f
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?11D022AB-87B0-4271-B469-8D5BA6BD398A>