Re: FYI: aarch64 main [so: 14] buildkernel (debug): ctfconvert: failed to get mapping for tid ?????

On 2021-Dec-3, at 07:58, Mark Johnston wrote: > On Mon, Nov 29, 2021 at 06:45:19PM -0800, Mark Millard via freebsd-arm wrote: >> For: >> >> uname -apKU >> FreeBSD CA72_4c8G_ZFS 14.0-CURRENT FreeBSD 14.0-CURRENT #22 >> main-n250972-319e9fc642a1-dirty: Tue Nov

Re: FYI: aarch64 main [so: 14] buildkernel (debug): ctfconvert: failed to get mapping for tid ?????

On 2021-Nov-29, at 18:45, Mark Millard wrote: > For: > > uname -apKU > FreeBSD CA72_4c8G_ZFS 14.0-CURRENT FreeBSD 14.0-CURRENT #22 > main-n250972-319e9fc642a1-dirty: Tue Nov 23 12:25:36 PST 2021 > root@CA72_16Gp_ZFS:/usr/obj/BUILDs/main-CA72-nodbg-clang/usr/main-src/arm64.aarch64/sys/GENER

FYI: aarch64 main [so: 14] buildkernel (debug): ctfconvert: failed to get mapping for tid ?????

For: uname -apKU FreeBSD CA72_4c8G_ZFS 14.0-CURRENT FreeBSD 14.0-CURRENT #22 main-n250972-319e9fc642a1-dirty: Tue Nov 23 12:25:36 PST 2021 root@CA72_16Gp_ZFS:/usr/obj/BUILDs/main-CA72-nodbg-clang/usr/main-src/arm64.aarch64/sys/GENERIC-NODBG-CA72 arm64 aarch64 1400042 1400042 building a va

main [so: 14]: contrib/llvm-project/libunwind/src/Unwind-EHABI.cpp:915 failure in armv7 context

In tracking down a armv7 build failure for some ports the fail during rustc, I managed to get a gdb backtrace for an example .core finally. This is based on not striping (no debug information). (rustc's build in armv7 contexts attempt links that fail for lack of a sufficient process address space.)

Re: After updating main (so: 14) Orange Pi+ 2E panicked: ucom_cons_softc "'Translation Fault (L2)' on read" while typing first command after login

On 2021-Oct-12, at 01:43, Hans Petter Selasky wrote: > On 10/12/21 3:11 AM, Mark Millard via freebsd-arm wrote: >> There is this "mixer" oddity for each boot: >> Feeding entropy: . >> mixer: 75:75: no such device >> mixer: 75:75: no such device >> m

After updating main (so: 14) Orange Pi+ 2E panicked: ucom_cons_softc "'Translation Fault (L2)' on read" while typing first command after login

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=0007, FAR=fff4, spsr=a013 r0 =0001, r1 =, r2 =, r3 = r4 =d8ce7100, r

I got a panic for "nvme0: cpl does not map to outstanding cmd" on a MACHIATObin Double Shot

# mount -onoatime 192.168.1.187:/usr/ports/ /mnt/ # diff -r /usr/ports/ /mnt/ | more nvme0: cpl does not map to outstanding cmd cdw0: sqhd:0020 sqid:0003 cid:007e p:1 sc:00 sct:0 m:0 dnr:0 panic: received completion for unknown cmd cpuid = 3 time = 1621743752 KDB: stack backtrace: db_trace_

FYI: Example USB3 boot failure on RPi4B ZFS-on-root system booting main: uhub_reattach_port notices involved

In upgrading from (grabbed from a system not updated yet): # uname -apKU FreeBSD CA72_16Gp_ZFS 14.0-CURRENT FreeBSD 14.0-CURRENT #1 main-n246411-a6ca7519f89c-dirty: Sat May 1 19:07:50 PDT 2021 root@CA72_4c8G_ZFS:/usr/obj/BUILDs/main-CA72-nodbg-clang/usr/main-src/arm64.aarch64/sys/GENERIC-NO