Date: Mon, 11 Oct 2021 18:11:26 -0700 From: Mark Millard via freebsd-arm <freebsd-arm@freebsd.org> To: Free BSD <freebsd-arm@freebsd.org>, freebsd-current <freebsd-current@freebsd.org> Subject: After updating main (so: 14) Orange Pi+ 2E panicked: ucom_cons_softc "'Translation Fault (L2)' on read" while typing first command after login Message-ID: <ADD31C61-F8AF-4FBF-B29D-5E79FB2DE8C1@yahoo.com> References: <ADD31C61-F8AF-4FBF-B29D-5E79FB2DE8C1.ref@yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
I did not even get a chance to finish typing a command after
login for the fist boot after updating:
Fatal kernel mode data abort: 'Translation Fault (L2)' on read
trapframe: 0xe18d6998
FSR=3D00000007, FAR=3Dfffffff4, spsr=3Da0000013
r0 =3D00000001, r1 =3D00000000, r2 =3D00000000, r3 =3D00000000
r4 =3Dd8ce7100, r5 =3D000007d0, r6 =3D90001010, r7 =3D00000000
r8 =3Dc08dfc10, r9 =3D00000001, r10=3Dc08dfc1c, r11=3De18d6aa8
r12=3De18d69e0, ssp=3De18d6a28, slr=3De18d6a28, pc =3De18d6a4c
panic: Fatal abort
cpuid =3D 0
time =3D 1633999791
KDB: stack backtrace:
db_trace_self() at db_trace_self
pc =3D 0xc062ef7c lr =3D 0xc007eb58 =
(db_trace_self_wrapper+0x30)
sp =3D 0xe18d6770 fp =3D 0xe18d6888
db_trace_self_wrapper() at db_trace_self_wrapper+0x30
pc =3D 0xc007eb58 lr =3D 0xc030ee04 (vpanic+0x17c)
sp =3D 0xe18d6890 fp =3D 0xe18d68b0
r4 =3D 0x00000100 r5 =3D 0x00000000
r6 =3D 0xc07cac38 r7 =3D 0xc0941d68
vpanic() at vpanic+0x17c
pc =3D 0xc030ee04 lr =3D 0xc030ec88 (vpanic)
sp =3D 0xe18d68b8 fp =3D 0xe18d68bc
r4 =3D 0xe18d6998 r5 =3D 0x00000013
r6 =3D 0xfffffff4 r7 =3D 0x00000007
r8 =3D 0x00000007 r9 =3D 0xda5e9000
r10 =3D 0xfffffff4
vpanic() at vpanic
pc =3D 0xc030ec88 lr =3D 0xc0652f68 (abort_align)
sp =3D 0xe18d68c4 fp =3D 0xe18d68f0
r4 =3D 0x00000007 r5 =3D 0x00000007
r6 =3D 0xda5e9000 r7 =3D 0xfffffff4
r8 =3D 0xe18d68bc r9 =3D 0xc030ec88
r10 =3D 0xe18d68c4
abort_align() at abort_align
pc =3D 0xc0652f68 lr =3D 0xc0652a90 (abort_handler+0x2a8)
sp =3D 0xe18d68f8 fp =3D 0xe18d6990
r4 =3D 0x00000013 r5 =3D 0xfffffff4
abort_handler() at abort_handler+0x2a8
pc =3D 0xc0652a90 lr =3D 0xc063191c (exception_exit)
sp =3D 0xe18d6998 fp =3D 0xe18d6aa8
r4 =3D 0xd8ce7100 r5 =3D 0x000007d0
r6 =3D 0x90001010 r7 =3D 0x00000000
r8 =3D 0xc08dfc10 r9 =3D 0x00000001
r10 =3D 0xc08dfc1c
exception_exit() at exception_exit
pc =3D 0xc063191c lr =3D 0xe18d6a28 (0xe18d6a28)
sp =3D 0xe18d6a28 fp =3D 0xe18d6aa8
r0 =3D 0x00000001 r1 =3D 0x00000000
r2 =3D 0x00000000 r3 =3D 0x00000000
r4 =3D 0xd8ce7100 r5 =3D 0x000007d0
r6 =3D 0x90001010 r7 =3D 0x00000000
r8 =3D 0xc08dfc10 r9 =3D 0x00000001
r10 =3D 0xc08dfc1c r12 =3D 0xe18d69e0
ucom_cons_softc() at 0xe18d6a4c
pc =3D 0xe18d6a4c lr =3D 0xe18d6a28 (0xe18d6a28)
sp =3D 0xe18d6a28 fp =3D 0xe18d6aa8
KDB: enter: panic
[ thread pid 894 tid 100135 ]
Stopped at kdb_enter+0x58: ldrb r15, [r15, r15, ror r15]!
db>
It is not reliably repeatable. Unsure if I can get a repeat at
all.
There is this "mixer" oddity for each boot:
Feeding entropy: .
mixer: 75:75: no such device
mixer: 75:75: no such device
mixer: 75:75: no such device
mixer: 25:25: no such device
mixer: 75:75: no such device
mixer: 75:75: no such device
mixer: =3Drec: no such device
lo0: link state changed to UP
(in case that matters for some reason).
For reference:
# uname -apKU
FreeBSD OPiP2E_RPi2v11 14.0-CURRENT FreeBSD 14.0-CURRENT #10 =
main-n249978-032448cd2c52-dirty: Sat Oct 9 02:11:35 PDT 2021 =
root@CA72_16Gp_ZFS:/usr/obj/BUILDs/main-CA7-nodbg-clang/usr/main-src/arm.a=
rmv7/sys/GENERIC-NODBG-CA7 arm armv7 1400036 1400036
=3D=3D=3D
Mark Millard
marklmi at yahoo.com
( dsl-only.net went
away in early 2018-Mar)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ADD31C61-F8AF-4FBF-B29D-5E79FB2DE8C1>