From nobody Fri Nov 14 12:50:54 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 4d7H7X04jBz6GNPL; Fri, 14 Nov 2025 12:51:04 +0000 (UTC) (envelope-from ronald-lists@klop.ws) Received: from smtp-relay-int-backup.realworks.nl (smtp-relay-int-backup.realworks.nl [87.255.56.188]) (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 did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4d7H7V2lnlz47Xq; Fri, 14 Nov 2025 12:51:02 +0000 (UTC) (envelope-from ronald-lists@klop.ws) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=klop.ws header.s=rw2 header.b=T1uN0zsq; dmarc=pass (policy=quarantine) header.from=klop.ws; spf=pass (mx1.freebsd.org: domain of ronald-lists@klop.ws designates 87.255.56.188 as permitted sender) smtp.mailfrom=ronald-lists@klop.ws Received: from smtp-relay-int-backup.realworks.nl (crmpreview8.colo2.realworks.nl [10.2.52.38]) by mailrelayint1.colo2.realworks.nl (Postfix) with ESMTP id 4d7H7M0lByz5H; Fri, 14 Nov 2025 13:50:55 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=klop.ws; s=rw2; t=1763124655; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=BXHXO96dWpzzJXvun5jqBMD9m7Z6Krt8Tj5rQPkqFDI=; b=T1uN0zsqujunr1NuXlDJ/lWZMylPhyKsgv0ayNtxERL2ZrUEKuDY5lIBAnxVkt2F+ojtVc LLhm0WhaCK/w4mhtlE/ivjtmh8eNdXL4zyeO+xTlAhMQn+AK9AS2n/r4CMm68HV4y3S3MT bsB1y36fEKzTYB85z1kfTz0HEYeuvQYvx10sW2+tZfxig8eRpmo7o/aeEi0BvkU3u3riwU ETtI9OlT1I0G5F64so6VSRaHt30s53k0+73a2IjfgMkUbYutICvFiPO+0i1e6fqvMc/N/l UJcYcxwgITPoYLhoQxyp8mEUjAcng4l8TUdFEaMvPnW75jnZMdyb1Lupi1mCJg== Received: from crmpreview8.colo2.realworks.nl (localhost [127.0.0.1]) by crmpreview8.colo2.realworks.nl (Postfix) with ESMTP id 6A4AB2C04C8; Fri, 14 Nov 2025 13:50:54 +0100 (CET) Date: Fri, 14 Nov 2025 13:50:54 +0100 (CET) From: Ronald Klop To: mmel@FreeBSD.org Cc: Ronald Klop , bob prohaska , freebsd-current@freebsd.org, Carl Shapiro , freebsd-arm@freebsd.org Message-ID: <562279.6155.1763124654329@localhost> In-Reply-To: <10c8be48-e9cd-4574-868f-51b113159311@FreeBSD.org> References: <4957be52-e57f-4f5f-9626-d0f706480fe1@FreeBSD.org> <87ldkai9lu.fsf@panix.com> <5dd66c4c-ed4d-4034-9fb3-f9079a513595@FreeBSD.org> <10c8be48-e9cd-4574-868f-51b113159311@FreeBSD.org> Subject: openjdk11 compile fail on armv7 - (Re: Still seeing Failed assertion: "p[i] == 0" on armv7 buildworld) 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 Content-Type: multipart/alternative; boundary="----=_Part_6154_1449500835.1763124653925" X-Mailer: Realworks (773.19) X-Originating-Host: from (83-81-212-149.cable.dynamic.v4.ziggo.nl [83.81.212.149]) by crmpreview8.colo2.realworks.nl [10.2.52.38] with HTTP; Fri, 14 Nov 2025 13:50:54 +0100 Importance: Normal X-Priority: 3 (Normal) X-Originating-User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:145.0) Gecko/20100101 Firefox/145.0 X-Spamd-Bar: --- X-Spamd-Result: default: False [-3.50 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-0.997]; MID_RHS_NOT_FQDN(0.50)[]; DMARC_POLICY_ALLOW(-0.50)[klop.ws,quarantine]; R_DKIM_ALLOW(-0.20)[klop.ws:s=rw2]; R_SPF_ALLOW(-0.20)[+ip4:87.255.56.128/26]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; TO_MATCH_ENVRCPT_SOME(0.00)[]; FROM_HAS_DN(0.00)[]; ASN(0.00)[asn:38930, ipnet:87.255.32.0/19, country:NL]; MIME_TRACE(0.00)[0:+,1:+,2:~]; TO_DN_SOME(0.00)[]; RCVD_TLS_LAST(0.00)[]; ARC_NA(0.00)[]; HAS_X_PRIO_THREE(0.00)[3]; RCVD_COUNT_TWO(0.00)[2]; FROM_EQ_ENVFROM(0.00)[]; RCPT_COUNT_FIVE(0.00)[6]; MLMMJ_DEST(0.00)[freebsd-arm@freebsd.org,freebsd-current@freebsd.org]; DKIM_TRACE(0.00)[klop.ws:+] X-Rspamd-Queue-Id: 4d7H7V2lnlz47Xq ------=_Part_6154_1449500835.1763124653925 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Van: Michal Meloun Datum: donderdag, 13 november 2025 11:38 Aan: Ronald Klop , Carl Shapiro CC: bob prohaska , freebsd-arm@freebsd.org, freebsd-current@freebsd.org Onderwerp: Re: Still seeing Failed assertion: "p[i] == 0" on armv7 buildworld > > > 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 > > > > I was able to reproduce openjdk11 failure in an armv7 poudriere build on aarch64 Raspberry Pi. The build doesn't always fail and the output is not always the same. Here is the output of two different compile runs. [00:19:54] === Output from failing command(s) repeated here === [00:19:54] * For target jdk_modules_java.base__the.java.base_batch: [00:19:54] # [00:19:54] # A fatal error has been detected by the Java Runtime Environment: [00:19:54] # [00:19:54] # SIGBUS (0xa) at pc=0x2031ce84, pid=34578, tid=124336 [00:19:54] # [00:19:54] # JRE version: OpenJDK Runtime Environment (11.0.11+9) (build 11.0.11+9-1) [00:19:54] # Java VM: OpenJDK Server VM (11.0.11+9-1, mixed mode, g1 gc, bsd-) [00:19:54] # Problematic frame: [00:19:54] # C [libc.so.7+0x1ace84] _malloc_thread_cleanup+0xa43c [00:19:54] # [00:19:54] # Core dump will be written. Default location: /wrkdirs/usr/ports/java/openjdk11/work/jdk11u-jdk-11.0.29-7-1/make/java.core [00:19:54] # [00:19:54] # An error report file with more information is saved as: [00:19:54] # /wrkdirs/usr/ports/java/openjdk11/work/jdk11u-jdk-11.0.29-7-1/make/hs_err_pid34578.log [00:19:54] # [03:09:57] === Output from failing command(s) repeated here === [03:09:57] * For target support_jmods_java.sql.jmod: [03:09:57] # [03:09:57] # A fatal error has been detected by the Java Runtime Environment: [03:09:57] # [03:09:57] # SIGBUS (0xa) at pc=0x2169d0c4, pid=16567, tid=137017 [03:09:57] # [03:09:57] # JRE version: OpenJDK Runtime Environment (11.0.29+7) (build 11.0.29+7-1) [03:09:57] # Java VM: OpenJDK Server VM (11.0.29+7-1, mixed mode, serial gc, bsd-) [03:09:57] # Problematic frame: [03:09:57] # J 77 c2 java.io.DataInputStream.readUnsignedShort()I java.base (39 bytes) @ 0x2169d0c4 [0x2169cf40+0x00000184] [03:09:57] # [03:09:57] # Core dump will be written. Default location: /wrkdirs/usr/ports/java/openjdk11/work/jdk11u-jdk-11.0.29-7-1/make/jmod.core [03:09:57] # [03:09:57] # An error report file with more information is saved as: [03:09:57] # /wrkdirs/usr/ports/java/openjdk11/work/jdk11u-jdk-11.0.29-7-1/make/hs_err_pid16567.log This is in a poudriere build that does not leave the environment behind after a failure. This weekend I can try to run poudriere with the options to keep the jail alive and gather some more artifacts for people to analyze. What kind of info would be valuable? The *.core and the hs_err*.log file maybe. Regards, Ronald. ------=_Part_6154_1449500835.1763124653925 Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit

Van: Michal Meloun <mmel@FreeBSD.org>
Datum: donderdag, 13 november 2025 11:38
Aan: Ronald Klop <ronald@FreeBSD.org>, Carl Shapiro <cshapiro@panix.com>
CC: bob prohaska <fbsd@www.zefox.net>, freebsd-arm@freebsd.org, freebsd-current@freebsd.org
Onderwerp: Re: Still seeing Failed assertion: "p[i] == 0" on armv7 buildworld



On 13.11.2025 10:52, Ronald Klop wrote:
> Op 13-11-2025 om 10:07 schreef Carl Shapiro:
>> Ronald Klop <ronald@FreeBSD.org> 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
 


I was able to reproduce openjdk11 failure in an armv7 poudriere build on aarch64 Raspberry Pi.
The build doesn't always fail and the output is not always the same. Here is the output of two different compile runs. 
[00:19:54] === Output from failing command(s) repeated here ===
[00:19:54] * For target jdk_modules_java.base__the.java.base_batch:
[00:19:54] #
[00:19:54] # A fatal error has been detected by the Java Runtime Environment:
[00:19:54] #
[00:19:54] #  SIGBUS (0xa) at pc=0x2031ce84, pid=34578, tid=124336
[00:19:54] #
[00:19:54] # JRE version: OpenJDK Runtime Environment (11.0.11+9) (build 11.0.11+9-1)
[00:19:54] # Java VM: OpenJDK Server VM (11.0.11+9-1, mixed mode, g1 gc, bsd-)
[00:19:54] # Problematic frame:
[00:19:54] # C  [libc.so.7+0x1ace84]  _malloc_thread_cleanup+0xa43c
[00:19:54] #
[00:19:54] # Core dump will be written. Default location: /wrkdirs/usr/ports/java/openjdk11/work/jdk11u-jdk-11.0.29-7-1/make/java.core
[00:19:54] #
[00:19:54] # An error report file with more information is saved as:
[00:19:54] # /wrkdirs/usr/ports/java/openjdk11/work/jdk11u-jdk-11.0.29-7-1/make/hs_err_pid34578.log
[00:19:54] #



[03:09:57] === Output from failing command(s) repeated here ===
[03:09:57] * For target support_jmods_java.sql.jmod:
[03:09:57] #
[03:09:57] # A fatal error has been detected by the Java Runtime Environment:
[03:09:57] #
[03:09:57] #  SIGBUS (0xa) at pc=0x2169d0c4, pid=16567, tid=137017
[03:09:57] #
[03:09:57] # JRE version: OpenJDK Runtime Environment (11.0.29+7) (build 11.0.29+7-1)
[03:09:57] # Java VM: OpenJDK Server VM (11.0.29+7-1, mixed mode, serial gc, bsd-)
[03:09:57] # Problematic frame:
[03:09:57] # J 77 c2 java.io.DataInputStream.readUnsignedShort()I java.base (39 bytes) @ 0x2169d0c4 [0x2169cf40+0x00000184]
[03:09:57] #
[03:09:57] # Core dump will be written. Default location: /wrkdirs/usr/ports/java/openjdk11/work/jdk11u-jdk-11.0.29-7-1/make/jmod.core
[03:09:57] #
[03:09:57] # An error report file with more information is saved as:
[03:09:57] # /wrkdirs/usr/ports/java/openjdk11/work/jdk11u-jdk-11.0.29-7-1/make/hs_err_pid16567.log

This is in a poudriere build that does not leave the environment behind after a failure. This weekend I can try to run poudriere with the options to keep the jail alive and gather some more artifacts for people to analyze.

What kind of info would be valuable? The *.core and the hs_err*.log file maybe.

Regards,
Ronald.
  ------=_Part_6154_1449500835.1763124653925--