Date: Sat, 16 Aug 2025 03:27:05 +0000 From: bugzilla-noreply@freebsd.org To: net@FreeBSD.org Subject: [Bug 288895] panic: exclusive sleep mutex pfsync ... locked @ /usr/src/sys/netpfil/pf/if_pfsync.c:3014 Message-ID: <bug-288895-7501-n8rxu55PcG@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-288895-7501@https.bugs.freebsd.org/bugzilla/> References: <bug-288895-7501@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=3D288895 Mark Millard <marklmi26-fbsd@yahoo.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |marklmi26-fbsd@yahoo.com --- Comment #2 from Mark Millard <marklmi26-fbsd@yahoo.com> --- Looks like there is a confusion of arm64 (64-bit) vs. armv7 (32-bit), with this being an armv7 context actually: "repros with arm64, but not amd64" but: "FreeBSD-main-armv7-test" Thee FreeBSD networking code violate alignment requirements for armv7 and there are various bugzilla reports about such. Examples include: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D272965 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D272966 So armv7 failures are not as surprising. --=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-288895-7501-n8rxu55PcG>