From nobody Tue Oct 22 20:52:26 2024 X-Original-To: freebsd-arm@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 4XY4B66tnQz5ZMKg; Tue, 22 Oct 2024 20:52:30 +0000 (UTC) (envelope-from SRS0=V0xP=RS=klop.ws=ronald-lists@realworks.nl) Received: from smtp-relay-int.realworks.nl (smtp-relay-int.realworks.nl [194.109.157.24]) (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 4XY4B51cfxz468p; Tue, 22 Oct 2024 20:52:29 +0000 (UTC) (envelope-from SRS0=V0xP=RS=klop.ws=ronald-lists@realworks.nl) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=klop.ws header.s=rw2 header.b=LewEZL6Q; spf=pass (mx1.freebsd.org: domain of "SRS0=V0xP=RS=klop.ws=ronald-lists@realworks.nl" designates 194.109.157.24 as permitted sender) smtp.mailfrom="SRS0=V0xP=RS=klop.ws=ronald-lists@realworks.nl"; dmarc=pass (policy=quarantine) header.from=klop.ws Date: Tue, 22 Oct 2024 22:52:26 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=klop.ws; s=rw2; t=1729630347; 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; bh=NFYEe/2sTsxMDFXi6QrwHnVPl2i0Dg8BIh1iTKiPy3M=; b=LewEZL6QTn0sBE6TelhR2SPBjy7eHdUfzYNCAHN3YUOPcXmV+kiLNqO3Huj7ZlDRwGhJHE pZKY/mtPectXgamlGJELD4GsKnZLMKDEXepVgNOgvFDmkU4Upk3Bhlv8AQSz9BBcNejvi8 uSI7anwPt4NfOb4G8tmRU2a+nAwEnS+N6h21kIVE+LcTpUBUR4i+iaNBftcykHHHouMhW3 SsSWvSrY5A5Nz9Nj4uFrg3PsMbumlgAb0IJ7gCa4ZB0tJic/ordhtnSUsjMksP61zDkGPd j/F4sUyA5p14ukRTTFCJKu/ScJGBYPHsF7sHxH+o0wMyrDCc7QYflF8QECb9Hw== From: Ronald Klop To: Mark Millard Cc: FreeBSD Mailing List , Antoine Brodin , Philip Paeps , FreeBSD ARM List Message-ID: <1902543396.49319.1729630346915@localhost> In-Reply-To: <4FDD9A40-B415-42B5-BA89-B89565C2A168@yahoo.com> Subject: Re: ampere2's main-armv7 crashed after only 3 min 51 sec, nothing started to build; libdm.so.{6->7} issues List-Id: Porting FreeBSD to ARM processors List-Archive: https://lists.freebsd.org/archives/freebsd-arm List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arm@FreeBSD.org MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_49318_2106664272.1729630346910" X-Mailer: Realworks (723.281) Importance: Normal X-Priority: 3 (Normal) X-Spamd-Result: default: False [-3.19 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.99)[-0.987]; MID_RHS_NOT_FQDN(0.50)[]; DMARC_POLICY_ALLOW(-0.50)[klop.ws,quarantine]; FORGED_SENDER(0.30)[ronald-lists@klop.ws,SRS0=V0xP=RS=klop.ws=ronald-lists@realworks.nl]; R_SPF_ALLOW(-0.20)[+ip4:194.109.157.0/24]; R_DKIM_ALLOW(-0.20)[klop.ws:s=rw2]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; ASN(0.00)[asn:3265, ipnet:194.109.0.0/16, country:NL]; MIME_TRACE(0.00)[0:+,1:+,2:~]; ARC_NA(0.00)[]; RCVD_COUNT_ZERO(0.00)[0]; MLMMJ_DEST(0.00)[freebsd-arm@freebsd.org,freebsd-ports@freebsd.org]; RCPT_COUNT_FIVE(0.00)[5]; FROM_NEQ_ENVFROM(0.00)[ronald-lists@klop.ws,SRS0=V0xP=RS=klop.ws=ronald-lists@realworks.nl]; FROM_HAS_DN(0.00)[]; FREEMAIL_TO(0.00)[yahoo.com]; HAS_X_PRIO_THREE(0.00)[3]; TO_DN_ALL(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[klop.ws:+] X-Rspamd-Queue-Id: 4XY4B51cfxz468p X-Spamd-Bar: --- ------=_Part_49318_2106664272.1729630346910 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Ampere2 is building armv7 again https://pkg-status.freebsd.org/ampere2/build.html?mastername=main-armv7-default&build=p94c4ac6b071b_sc87b3f0006 BTW: I made a graph that shows how old a pkg repo is per architecture.It shows that arm/aarch64 is significantly older than i386/amd64. But also that armv7 is way behind the rest now. https://www.klop.ws/pkgstats/pkg-age.html Regards,Ronald Van: Mark Millard Datum: 14 oktober 2024 01:41 Aan: Ronald Klop CC: Antoine Brodin , FreeBSD Mailing List , FreeBSD ARM List , Philip Paeps Onderwerp: Re: ampere2's main-armv7 crashed after only 3 min 51 sec, nothing started to build; libdm.so.{6->7} issues > > > On Oct 13, 2024, at 13:18, Ronald Klop wrote: > > > On ampere3 armv7 builds crashed in the same way. > > > > https://pkg-status.freebsd.org/ampere3/ > > > > Regards, > > Ronald > > > >> Van: Mark Millard > >> Datum: 13 oktober 2024 22:13 > >> Aan: Antoine Brodin , FreeBSD Mailing List , FreeBSD ARM List > >> CC: Philip Paeps > >> Onderwerp: ampere2's main-armv7 crashed after only 3 min 51 sec, nothing started to build; libdm.so.{6->7} issues > >> > >> main-armv7 crashed before it was at a stage that has public log files to look > >> at. > >> > >> I report this mostly because the currently distributed main-packages for ports > >> that involve use of libmd.so.6 are broken because main now has/uses libmd.so.7 > >> instead --so libmd.so.6 tends to be missing. Even when libmd.so.6 and > >> libmd.so.7 both exist, the pkg (non -static) command is broken from the > >> recursive dependencies ending up referencing both. (pkg-static works but pkg > >> does not.) > >> > >> It might be that the crash is because of the libmd.so.6 to libmd.so.7 change > >> in main. But I've no access to logs to look at. > >> > >> It would be good to avoid having another main-arm64 bulk -a happen before > >> main-armv7 has a chance to produce main-armv7 packages with libmd.so.7 > >> references so that ports are again good for (modern) main-FreeBSD [so: 15]. > >> > >> But it seems that, for main-arm* port-packages, either: > >> > >> 0) various distributed ports are incompatible with libmd.so.7 based > >> main-FreeBSD (the current context for main-armv7) > >> > >> vs. > >> > >> 1) various distributed ports will be incompatible with libmd.so.6 > >> based main-FreeBSD (so: older main/15 FreeBSD installations): > >> the future contexts for main-armv7 and main-arm64 (and more). > >> > >> > >> FYI: The libmd.so.{6->7} change dates back to 2024-Sep-30 in FreeBSD's main. > >> But the __FreeBSD_version 150002{3->4} change did not happen until > >> 2024-Oct-02. > >> > >> > >> main-powerpc-default's status for such: > >> > >> Looks like FreeBSD:15:powerpc/latest/ was last updated on 2024-Mar-07 > >> and so might not have the issue --by no longer having port-package > >> updates of any kind. (32-bit powerpc is not to be supported by > >> releng/15.0 as I understand: The only 32-bit platform will be armv7 > >> as I understand.) > > Looks like I should have done a wider exploration instead > of presuming just main-armv7 was broken. > > An interesting point is that none of the *-armv7-quarterly > jails have failed so far. Just the *-armv7-default have > failed: > > main-armv7-default p149fe86b8e79_s149e1af6a , > 141releng-armv7-default 1f84c1fae602 , > 133releng-armv7-default 1f84c1fae602 . > > I'll note that the arm64 ones did not fail: > > main-arm64-default p149fe86b8e79_s149e1af6ae4 > 141arm64-default 1f84c1fae602 , > 133arm64-default 1f84c1fae602 . > > 133releng-armv7-default is the oldest failure for this issue: > Sun, 06 Oct 2024 23:33:31 GMT start with elapsed: 00:05:26 . > > 133releng-armv7-default had a prior build: Thu, 19 Sep 2024 19:55:19 GMT 58:03:54 > > 141releng-armv7-default had no prior build attempts ( was: 140releng-armv7-default ). > > main-armv7-default had a prior build: Thu, 03 Oct 2024 04:21:42 GMT 61:50:05 > > > I wonder what a common change is across the failing examples. > > > === > Mark Millard > marklmi at yahoo.com > > > > > ------=_Part_49318_2106664272.1729630346910 Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: quoted-printable Ampere2 is building armv7 again

https://pk= g-status.freebsd.org/ampere2/build.html?mastername=3Dmain-armv7-default&= ;build=3Dp94c4ac6b071b_sc87b3f0006

BTW: I mad= e a graph that shows how old a pkg repo is per architecture.
It shows that arm/aarch64 is significantly older than i386/amd64. &= nbsp;But also that armv7 is way behind the rest now.
https://www.klop.ws/pkgstats/pkg-ag= e.html

Regards,
Ronald

Van: Mark Millard <marklmi@yahoo.com&g= t;
Datum: 14 oktober 2024 01:41
Aan: Ronald Klop <ronald-lists@klop.ws>
CC: Antoine = Brodin <antoine@freebsd.org>, FreeBSD Mailing List <freebsd-ports@= freebsd.org>, FreeBSD ARM List <freebsd-arm@freebsd.org>, Philip P= aeps <philip@freebsd.org>
Onderwerp: Re: ampere2'= s main-armv7 crashed after only 3 min 51 sec, nothing started to build; li= bdm.so.{6->7} issues

On Oct 13, 2024, at 13:18, Ronald Klop wrote:<= br>
> On ampere3 armv7 builds crashed in the same way.
>
> https://pkg-status= .freebsd.org/ampere3/
>
> Regards,
> Ronald
>
>> Van: Mark Millard
>> Datum: 13 oktober 2024 22:13
>> Aan: Antoine Brodin , FreeBSD Mailing List , FreeBSD ARM List
>> CC: Philip Paeps
>> Onderwerp: ampere2's main-armv7 crashed after only 3 min 51 sec, n= othing started to build; libdm.so.{6->7} issues
>>
>> main-armv7 crashed before it was at a stage that has public log fi= les to look
>> at.
>>
>> I report this mostly because the currently distributed main-packag= es for ports
>> that involve use of libmd.so.6 are broken because main now has/use= s libmd.so.7
>> instead --so libmd.so.6 tends to be missing. Even when libmd.so.6 = and
>> libmd.so.7 both exist, the pkg (non -static) command is broken fro= m the
>> recursive dependencies ending up referencing both. (pkg-static wor= ks but pkg
>> does not.)
>>
>> It might be that the crash is because of the libmd.so.6 to libmd.s= o.7 change
>> in main. But I've no access to logs to look at.
>>
>> It would be good to avoid having another main-arm64 bulk -a happen= before
>> main-armv7 has a chance to produce main-armv7 packages with libmd.= so.7
>> references so that ports are again good for (modern) main-FreeBSD = [so: 15].
>>
>> But it seems that, for main-arm* port-packages, either:
>>
>> 0) various distributed ports are incompatible with libmd.so.7 base= d
>>     main-FreeBSD (the current context for main= -armv7)
>>
>> vs.
>>
>> 1) various distributed ports will be incompatible with libmd.so.6<= br> >>      based main-FreeBSD (so: older main/1= 5 FreeBSD installations):
>>      the future contexts for main-armv7 a= nd main-arm64 (and more).
>>
>>
>> FYI: The libmd.so.{6->7} change dates back to 2024-Sep-30 in Fr= eeBSD's main.
>> But the __FreeBSD_version 150002{3->4} change did not happen un= til
>> 2024-Oct-02.
>>
>>
>> main-powerpc-default's status for such:
>>
>> Looks like FreeBSD:15:powerpc/latest/ was last updated on 2024-Mar= -07
>> and so might not have the issue --by no longer having port-package=
>> updates of any kind. (32-bit powerpc is not to be supported by
>> releng/15.0 as I understand: The only 32-bit platform will be armv= 7
>> as I understand.)

Looks like I should have done a wider exploration instead
of presuming just main-armv7 was broken.

An interesting point is that none of the *-armv7-quarterly
jails have failed so far. Just the *-armv7-default have
failed:

main-armv7-default p149fe86b8e79_s149e1af6a ,
141releng-armv7-default 1f84c1fae602 ,
133releng-armv7-default 1f84c1fae602 .

I'll note that the arm64 ones did not fail:

main-arm64-default p149fe86b8e79_s149e1af6ae4
141arm64-default 1f84c1fae602 ,
133arm64-default 1f84c1fae602 .

133releng-armv7-default is the oldest failure for this issue:
Sun, 06 Oct 2024 23:33:31 GMT start with elapsed: 00:05:26 .

133releng-armv7-default had a  prior build: Thu, 19 Sep 2024 19:55:19 = GMT 58:03:54

141releng-armv7-default had no prior build attempts ( was: 140releng-armv7-= default ).

     main-armv7-default had a  prior build: T= hu, 03 Oct 2024 04:21:42 GMT 61:50:05


I wonder what a common change is across the failing examples.


=3D=3D=3D
Mark Millard
marklmi at yahoo.com

=




------=_Part_49318_2106664272.1729630346910--