Date: Sun, 19 Feb 2017 02:18:54 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-amd64@FreeBSD.org Subject: [Bug 217138] head (e.g.) -r313783 sh vs. jemalloc asserts: include/jemalloc/internal/tsd.h:687: Failed assertion: "tsd_booted" Message-ID: <bug-217138-6-quMY1lgN6G@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-217138-6@https.bugs.freebsd.org/bugzilla/> References: <bug-217138-6@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=3D217138 Mark Millard <markmi@dsl-only.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Hardware|amd64 |arm64 CC| |freebsd-arm@FreeBSD.org --- Comment #5 from Mark Millard <markmi@dsl-only.net> --- [Note: the kernels after -r313266 are messed up for at least PowerMac so-called "Quad-Core"s so the below is based on a -r313864 buildworld and a -r313266 buildkernel because I had to revert the kernel to about the last that would avoid randomly timed panics.] I did a buildworld of -r313864 for powerpc64 without having MALLOC_PRODUCTION defined and installed and booted with it in order to see if powerpc64 had the same sort of problem that aarch64 is having with jemalloc, in particular during self-hosted buildworld buildkernel activity (my test case). powerpc64 worked fine with no aborts. So. . . include/jemalloc/internal/tsd.h:687: Failed assertion: "tsd_booted" seems to be aarch64 (arm64) specific in some way. --=20 You are receiving this mail because: You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-217138-6-quMY1lgN6G>