From nobody Fri Jul 26 23:44:13 2024 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 4WW4960Q3dz5Rb6S for ; Fri, 26 Jul 2024 23:44:26 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-pj1-x1034.google.com (mail-pj1-x1034.google.com [IPv6:2607:f8b0:4864:20::1034]) (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-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "WR4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4WW4955lq4z41hg for ; Fri, 26 Jul 2024 23:44:25 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-pj1-x1034.google.com with SMTP id 98e67ed59e1d1-2cb81c0ecb4so1004844a91.0 for ; Fri, 26 Jul 2024 16:44:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20230601.gappssmtp.com; s=20230601; t=1722037464; x=1722642264; darn=freebsd.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=TRrdqoTZVyVV33KteZeGTJufcVpFaaJ5wYCoSrm6dqk=; b=Lag8qXPWto8BrPilCHFpn4WxwKKwPPomAJBfPMXU+jIt6o3aBMtpS4L4bcGs5nGL/g PLrIE5XltD5ozQEn6i6F8iKHKcbuhl21btQXJyCc4y87ppcq7TJKmwvcWqz5vKvOzR9U 5+Q7vjgB+jRCLNE3w/eYoaGJtgQ6ozzKwrpVwQtcylL4rKX5bw7GpwGKqXCPprXw4V+q IpExvh3qAE0wIoPjTu9z1O3gPCrrLEROsQ/nFSOokCWmuXKtCQ+fHsGSuracGFPVIKXA jc59MZSynhvXl9dqKbnoLfur+/T20E3G/JIgIiyHTKnGj/IbMjclcfPqWwagz6F8Ldja LLwQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1722037464; x=1722642264; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=TRrdqoTZVyVV33KteZeGTJufcVpFaaJ5wYCoSrm6dqk=; b=ojM0gH2ZWQ7niJ3/OEcdgCWfxI62HLIkp+jWl/dHUxZKYb8H+yJN5CW2gCIJFQ8grE vpxF69HSX26GOaJYxKLMrFUbkI9JSMv7wmTNB9lWJb9wd21nHzT66lj14JSmCiDwcTbl tV17p0rYoKh/bfg8e+knQmltzS85BzJJ6EHl2Jk6zq6pUB8TT6GT/aUd03clVPNYpcGz 7Urkxz/cS+l5dwlHoFig0EEEQc7c0vFHueFdbojqDZJ59ouyDFsSy8EyoVIONpboH24a tC8uWMUVR8T4ZAypNmeXwFjNG8fDGD8iWthW9L8lFJdJmqSflE7+wPdPCec+xu8MhGO+ aeDg== X-Forwarded-Encrypted: i=1; AJvYcCXJixxfnFdwWfO9B6z8qyGFa4f/15ixKcYQT9AsxZLXhAIWb6MjLPjeqtQ99ZRn7G6cJU5oSQxHN7BbBBelVQRGYNy10pHWg5Auq+w= X-Gm-Message-State: AOJu0YzX8/mCPuDgF4qmlAqcMkwFTf3QGAzbVfkZSwnujV6TJpnegX0Q x2YA46yRF0oR/8nw9iHm+lYSOEyiu+3FT9DFeyO0QMoeYQCIvb8MDUV6CIWsyLUY45+hAvvLOAU KmqpjsMlXzabQ0SMCxuazBbQOClMzPCLh4dlUng== X-Google-Smtp-Source: AGHT+IG5sH53XMszp2sgZ/FJmwRfnybpg22ororQ8dJf4OsWhq4TqzXb87l6pGLt6abXivbNKVByS8tmeCVZ3op2nl8= X-Received: by 2002:a17:90b:4a81:b0:2c3:34f4:5154 with SMTP id 98e67ed59e1d1-2cf7ce8754bmr1794598a91.1.1722037464395; Fri, 26 Jul 2024 16:44:24 -0700 (PDT) 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 References: <8214703E-AB28-4FB3-A3DD-03C87363D8C6@yahoo.com> <561E4947-6D56-4431-AE08-C843FF232066@yahoo.com> In-Reply-To: From: Warner Losh Date: Fri, 26 Jul 2024 17:44:13 -0600 Message-ID: Subject: Re: [main has a fix for] armv7-on-aarch64 stuck at urdlck: I got a replication of the "ampere2" bulk build hangup problem on a Windows DevKit 2023 To: Mark Millard Cc: Philip Paeps , FreeBSD ARM List , FreeBSD Mailing List , Current FreeBSD Content-Type: multipart/alternative; boundary="0000000000005b0db1061e2f1772" X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US] X-Rspamd-Queue-Id: 4WW4955lq4z41hg --0000000000005b0db1061e2f1772 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Fri, Jul 26, 2024, 5:37=E2=80=AFPM Mark Millard wrot= e: > On Jul 26, 2024, at 07:56, Philip Paeps wrote: > > > On 2024-07-26 22:46:57 (+0800), Mark Millard wrote: > >> So, it looks like updating the kernel and world on ampere2 and > >> enabling builds of main-armv7-default should no longer have > >> main-armv7-default hang-up during graphviz installation (or > >> analogous contexts). Hopefully, that means that > >> main-armv7-default builds will then complete and be distributed. > > > > I've set the stop-builds flag on the ampere machines. I'll kick off a > cluster build and upgrade them when they finish their current builds (or > get stuck). > > > > Thanks for chasing this down. > > FYI: As stands, only main has the update. The MFC will not happen > for about a week. ampere1 and ampere3 should probably wait to > upate until after the MFC since they do not build main-armv7-* . > > Note: The fix is a world change, not a kernel change. So it is > the jail's world that matters. > > I'm not sure if any existing releng/13.*/ or releng/14.*/ will > get an update for this. stable/13/ and stable/14/ are likely to. > I wonder if a rebuilt system will make it through an armv7 bsd-user poudriere bulk.... Warner =3D=3D=3D > Mark Millard > marklmi at yahoo.com > > > --0000000000005b0db1061e2f1772 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


On Fri, Jul 26, 2024, 5:37=E2=80=AFPM Mark Millard <= ;marklmi@yahoo.com> wrote:
<= /div>
On Jul 26, 2024, at 07:56, Philip Paeps= <philip@freebsd.org> wrote:

> On 2024-07-26 22:46:57 (+0800), Mark Millard wrote:
>> So, it looks like updating the kernel and world on ampere2 and
>> enabling builds of main-armv7-default should no longer have
>> main-armv7-default hang-up during graphviz installation (or
>> analogous contexts). Hopefully, that means that
>> main-armv7-default builds will then complete and be distributed. >
> I've set the stop-builds flag on the ampere machines.=C2=A0 I'= ll kick off a cluster build and upgrade them when they finish their current= builds (or get stuck).
>
> Thanks for chasing this down.

FYI: As stands, only main has the update. The MFC will not happen
for about a week. ampere1 and ampere3 should probably wait to
upate until after the MFC since they do not build main-armv7-* .

Note: The fix is a world change, not a kernel change. So it is
the jail's world that matters.

I'm not sure if any existing releng/13.*/ or releng/14.*/ will
get an update for this. stable/13/ and stable/14/ are likely to.

I wonder if= a rebuilt system will make it through an armv7 bsd-user poudriere bulk....=

Warner


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


--0000000000005b0db1061e2f1772--