Date: Thu, 13 Nov 2025 01:17:52 -0700 From: Warner Losh <imp@bsdimp.com> To: Ronald Klop <ronald@freebsd.org> Cc: bob prohaska <fbsd@www.zefox.net>, freebsd-arm@freebsd.org, freebsd-current@freebsd.org Subject: Re: Still seeing Failed assertion: "p[i] == 0" on armv7 buildworld Message-ID: <CANCZdfquwRq6=7ximOZWU%2BEyrwii1pqSjcZ6AFo1cGDgbD4=Gg@mail.gmail.com> In-Reply-To: <4957be52-e57f-4f5f-9626-d0f706480fe1@FreeBSD.org> References: <aOu7s9roGCofdCOw@www.zefox.net> <aOvTG-20QRJtJJwf@int21h> <CANCZdfrJ8rph_rkT3Mk-sNYKNspoV15SvHWLsahzS0HnULi4ww@mail.gmail.com> <aO068RrAehdiHOoZ@www.zefox.net> <aRUJPryA4Vmu8dDD@www.zefox.net> <4957be52-e57f-4f5f-9626-d0f706480fe1@FreeBSD.org>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --] On Thu, Nov 13, 2025 at 1:12 AM Ronald Klop <ronald@freebsd.org> wrote: > Op 12-11-2025 om 23:25 schreef bob prohaska: > > For lack of any better ideas I've collected some of the assertion failure > > /tmp files by host at > > http://www.zefox.net/~fbsd/assertion_failure/ > > > > Thanks for reading, > > > > bob prohaska > > > > > > A really uneducated guess, but might the update of jemalloc [1] have > introduced some subtle issues on armv7? > You can try reverting: > https://cgit.freebsd.org/src/commit/?id=c43cad87172039ccf38172129c79755ea79e6102 > . > So, is this a new assert that detects a previously undetected corruption? Or is it a new error in jemalloc, correctly detected by the assert? Warner > My thought was triggered by this as a build of opendjk11 failed with a > jemalloc error. > > https://lists.freebsd.org/archives/freebsd-pkg-fallout/2025-September/804963.html > > Regards, > Ronald. > > [1] https://cgit.freebsd.org/src/log/?qt=grep&q=jemalloc > > [-- Attachment #2 --] <div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote gmail_quote_container"><div dir="ltr" class="gmail_attr">On Thu, Nov 13, 2025 at 1:12 AM Ronald Klop <<a href="mailto:ronald@freebsd.org">ronald@freebsd.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Op 12-11-2025 om 23:25 schreef bob prohaska:<br> > For lack of any better ideas I've collected some of the assertion failure<br> > /tmp files by host at<br> > <a href="http://www.zefox.net/~fbsd/assertion_failure/" rel="noreferrer" target="_blank">http://www.zefox.net/~fbsd/assertion_failure/</a><br>; > <br> > Thanks for reading,<br> > <br> > bob prohaska<br> > <br> > <br> <br> A really uneducated guess, but might the update of jemalloc [1] have introduced some subtle issues on armv7?<br> You can try reverting: <a href="https://cgit.freebsd.org/src/commit/?id=c43cad87172039ccf38172129c79755ea79e6102" rel="noreferrer" target="_blank">https://cgit.freebsd.org/src/commit/?id=c43cad87172039ccf38172129c79755ea79e6102</a>.<br></blockquote><div><br></div><div>So, is this a new assert that detects a previously undetected corruption? Or is it a new error in jemalloc, correctly detected by the assert?</div><div><br></div><div>Warner</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"> My thought was triggered by this as a build of opendjk11 failed with a jemalloc error.<br> <a href="https://lists.freebsd.org/archives/freebsd-pkg-fallout/2025-September/804963.html" rel="noreferrer" target="_blank">https://lists.freebsd.org/archives/freebsd-pkg-fallout/2025-September/804963.html</a><br>; <br> Regards,<br> Ronald.<br> <br> [1] <a href="https://cgit.freebsd.org/src/log/?qt=grep&q=jemalloc" rel="noreferrer" target="_blank">https://cgit.freebsd.org/src/log/?qt=grep&q=jemalloc</a><br>; <br> </blockquote></div></div>help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CANCZdfquwRq6=7ximOZWU%2BEyrwii1pqSjcZ6AFo1cGDgbD4=Gg>