Date: Tue, 20 Feb 2024 19:23:27 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 272965] 14.0-ALPHA1 too: armv7 'Alignment Fault' on read panic during udp_input for kyua's sys/netinet6/exthdr:exthdr ; other udp_input related panics Message-ID: <bug-272965-227-BdRAmCN3Se@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-272965-227@https.bugs.freebsd.org/bugzilla/> References: <bug-272965-227@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D272965 --- Comment #13 from Mark Millard <marklmi26-fbsd@yahoo.com> --- (In reply to Warner Losh from comment #8) armv7 infrastructure has problems with handling core dumps. This was on an Orange Pi+ 2e: # uname -apKU FreeBSD armv7-main-pkgs 15.0-CURRENT FreeBSD 15.0-CURRENT main-n267775-6ec8bf9f3d17 GENERIC-NODEBUG arm armv7 1500012 1500012 which is from pkgbase. I tested that the panic still happens and dumped a core out. armv7-main-pkgs dumped core - see /var/crash/vmcore.0 Tue Feb 20 18:36:46 UTC 2024 FreeBSD armv7-main-pkgs 15.0-CURRENT FreeBSD 15.0-CURRENT main-n267775-6ec8bf9f3d17 GENERIC-NODEBUG arm panic: Fatal abort Reading symbols from /boot/kernel.GENERIC-NODEBUG/kernel... Reading symbols from /usr/lib/debug//boot/kernel.GENERIC-NODEBUG/kernel.debug... /wrkdirs/usr/ports/devel/gdb/work-py39/gdb-14.1/gdb/thread.c:1362: internal-error: switch_to_thread: Assertion `thr !=3D NULL' failed. A problem internal to GDB has been detected, further debugging may prove unreliable. ----- Backtrace ----- 0xce8f93 ??? 0x11dbd7b ??? --------------------- /wrkdirs/usr/ports/devel/gdb/work-py39/gdb-14.1/gdb/thread.c:1362: internal-error: switch_to_thread: Assertion `thr !=3D NULL' failed. A problem internal to GDB has been detected, further debugging may prove unreliable. It has been a while since pkgbase updated for armv7. May be there are build failures. As yet there is no published way to monitor the build status or completions: all I can monitor is what is published. What pkgbase published still has /boot/dtb/ files bound with the kernel. So kernels conflict: at most one kernel at a time as far as pkgbase is concerned. (And not stable about what it picks by default.) --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-272965-227-BdRAmCN3Se>