From nobody Thu Nov 13 10:38:08 2025 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4d6cDh2GTbz6Gf3x; Thu, 13 Nov 2025 10:38:12 +0000 (UTC) (envelope-from mmel@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R13" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4d6cDh1ZZBz3Zmf; Thu, 13 Nov 2025 10:38:12 +0000 (UTC) (envelope-from mmel@FreeBSD.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1763030292; h=from:from:reply-to:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=4CbzCq6ugzjZiIVjF+CeaG/EOpwA7+V4K6vhFaw6bzk=; b=u8Ki1pMAI5BsqLkXgFptlV9aj5lGYJDYE6xPyNetanWBu8eVz8pTRNuCXMozrM9ZfVn/gh 8cElvXRe3d0Kbts/KoSYMaGfRNBGL7DNWXQHL71sjlMA71HP11bVkIWyGpeRbD1DEYm1DB TIKiAKPq9WrChwTeexav8CU59ymqTseRJUz5+pMk2aUH0E+oY8swpQRjT0vbE4W1vdIDa5 bInOht+Rz2R77ncPiwQhUZ1xFj1zybrk1e5oz6uYvvpVeUebN8Ikqwv1/cu1XtayaiR+dG ksJLVGgGL3u3eiZY0Bp2s7JHxEz819gg98l8gWO8no31WQ3427UV5CFsgv5QGg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1763030292; h=from:from:reply-to:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=4CbzCq6ugzjZiIVjF+CeaG/EOpwA7+V4K6vhFaw6bzk=; b=WSe1FPlHqQ6jTl0ioKSBav9bi6bq2c0aRTbrP/hzSE1ppR+9FrSV14EBhB1Sw9gHgUann8 ubi8rNnwSo/OcMXwJ/2R8VcsmT5n3PvKhKVEj+TiD0ELz3HgFBVHtMDYVVj0XFZs1aEh8L aPxRH8kDt6Hwk5oSUWXY5JjmukrsKQVQOcV62ERjBkt6ie06WWli5J/ZPs+gxH+Y8yr/J3 51TQiGtdEuqRFONKrhnlwjhq3u8jSk+0Imj8I27guK0QHAPNPGxVef09+VxyQzNI4iaJNC AUdM6asr5UkZ1VYodh45d0kSVFvl4LD3FUjoUUroaFmTq1rRgp1j+fRpj/2jSg== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1763030292; a=rsa-sha256; cv=none; b=mY8sZ3e/akivLAE9e4E0tHpXlcZ1IzSlVz6lHSkhvRpR4vnibjfFjjGRiA0orHKygKDIIO 6pZA36a9782HgSqVQYFhjSzFmrHRBqR5Vu5C/nxj8lb20jSWZSxK4XWtA/VWw905GNR8jl 1WmhwAnj6VipOYNoZ+a6ZASKnzE0bWDIS9CKnfaoh9MS0sGaJkKMQQKcS1hsheHOHoLgeD hDP5Qx0DGOhrccj1aWq0H/LlhyBSJTu+ASAHWFlUk/fghKoACpz0DeNQVw2OLcEBsBsp+8 a8T9oXM5bW75tTbo4HkG2cFTRuCOicHshqRKPgHeBcjAKbWTqnXa5YSpOSMPdQ== ARC-Authentication-Results: i=1; mx1.freebsd.org; none Received: from [192.168.168.195] (lety.radiolinkplus.cz [109.205.241.143]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) (Authenticated sender: mmel/mail) by smtp.freebsd.org (Postfix) with ESMTPSA id 4d6cDg3S1Vz17SJ; Thu, 13 Nov 2025 10:38:11 +0000 (UTC) (envelope-from mmel@FreeBSD.org) Message-ID: <10c8be48-e9cd-4574-868f-51b113159311@FreeBSD.org> Date: Thu, 13 Nov 2025 11:38:08 +0100 List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@FreeBSD.org MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Reply-To: mmel@FreeBSD.org Subject: Re: Still seeing Failed assertion: "p[i] == 0" on armv7 buildworld To: Ronald Klop , Carl Shapiro Cc: bob prohaska , freebsd-arm@freebsd.org, freebsd-current@freebsd.org References: <4957be52-e57f-4f5f-9626-d0f706480fe1@FreeBSD.org> <87ldkai9lu.fsf@panix.com> <5dd66c4c-ed4d-4034-9fb3-f9079a513595@FreeBSD.org> Content-Language: cs, en-US From: Michal Meloun In-Reply-To: <5dd66c4c-ed4d-4034-9fb3-f9079a513595@FreeBSD.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit On 13.11.2025 10:52, Ronald Klop wrote: > Op 13-11-2025 om 10:07 schreef Carl Shapiro: >> Ronald Klop writes: >> >>> 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 >> >> Is this build failure very reproducible?  Is there more of a stack trace >> to go with it? >> >> When the jemalloc witness code observes a locking error the process >> should abort immediately with a SIGABRT.  However, there is SIGBUS >> reported in the build output prior to the witness error which makes it >> look like OpenJDK may have been handling a signal while the witness code >> was running.  If malloc is somehow being called from a signal handler >> that is asking for trouble. >> >> Here's a closed issue from the old jemalloc repository about a witness >> error when malloc was called from a signal handler >> >> https://github.com/jemalloc/jemalloc/issues/1224 > > > Hi, > > I only have this example. I don't run armv7 myself. > Unfortunately the armv7 pkg builders don't run that often. > > This is the only failure on main-armv7, but AFAIK no new pkg build run > for main-armv7 has happened since. > https://portsfallout.com/fallout? > port=java%2Fopenjdk&maintainer=&env=armv7&category=&flavor= > > I just noticed that the full build log is also already gone from the pkg > build server. > > Regards, > Ronald. I am also a victim of this problem. In my case, unfortunately, the problem is rare and transient. It occurs intermittently and can be resolved by restarting the make. I can confirm that the problem is not related to a specific port. I have experienced it with gdal, qt6-webengine, and rust at minimum. I'm guessing it may be related to memory pressure before OOM. Unfortunately, I'm out of ideas now... Michal