Re: Failed assertion in buildworld on armv7
- In reply to: bob prohaska : "Re: Failed assertion in buildworld on armv7"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Mon, 29 Sep 2025 14:03:28 UTC
On Fri, Sep 12, 2025 at 06:37:10AM -0700, bob prohaska wrote: > > I've used > rm /usr/src/contrib/jemalloc/include/jemalloc/internal/ehooks.h > and > git restore /usr/src/contrib/jemalloc/include/jemalloc/internal/ehooks.h > to see if that cleans things up. Buildworld has been restarted using > WITH_META_MODE. It looks like running make cleandir twice solved the problem for a while, but after two successful build/install cycles on the Pi2 I'm again seeing ... <jemalloc>: /usr/src/contrib/jemalloc/include/jemalloc/internal/ehooks.h:170: Fa iled assertion: "p[i] == 0" ... The only other oddity seen is a console message: ... Sep 28 16:11:35 pelorus sshd-session[36944]: error: PAM: Authentication error for illegal user admin from 116.99.169.111 (da0:umass-sim0:0:0:0): READ(10). CDB: 28 00 00 a0 42 98 00 00 30 00 (da0:umass-sim0:0:0:0): CAM status: CCB request completed with an error (da0:umass-sim0:0:0:0): Retrying command, 3 more tries remain Sep 28 16:35:53 pelorus sshd-session[37014]: error: Fssh_kex_exchange_identification: read: Connection reset by peer ... It seeems the retry was successful, but could it have gone wrong in a silent way? Thanks for reading, bob prohaska