Date: Tue, 28 Feb 2017 03:35:03 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-amd64@FreeBSD.org Subject: [Bug 217138] head (e.g.) -r313864 for arm64: sh vs. jemalloc asserts: include/jemalloc/internal/tsd.h:687: Failed assertion: "tsd_booted" once swapped in after being swapped out (comment 10) Message-ID: <bug-217138-6-7A9VIh4PEG@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 --- Comment #11 from Mark Millard <markmi@dsl-only.net> --- (In reply to Mark Millard from comment #10) I'll note that the sh.*.core files show that __je_tsd_booted and a very large area around it is all zero. (I've been seeing this for a long time but until the swapped-out-before discovery I had little information about when the big block of zeros showed up.) Some possibilities: A) The memory was not restored at all. B) Incorrect content was restored (possibly incorrect content was swapped out earlier). C) The memory and caches and such were not forced to be coherent in one or both directions of transfer. There may be other things that could be involved. --=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-7A9VIh4PEG>