From owner-freebsd-arm@freebsd.org Mon Nov 2 15:16:23 2020 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 541FA4542C0 for ; Mon, 2 Nov 2020 15:16:23 +0000 (UTC) (envelope-from philip@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (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 "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4CPxMW1YCyz4dwR; Mon, 2 Nov 2020 15:16:23 +0000 (UTC) (envelope-from philip@freebsd.org) Received: from weatherwax.trouble.is (weatherwax.trouble.is [46.235.227.50]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "weatherwax.trouble.is", Issuer "Let's Encrypt Authority X3" (verified OK)) (Authenticated sender: philip/mail) by smtp.freebsd.org (Postfix) with ESMTPSA id 00F0B2FF7F; Mon, 2 Nov 2020 15:16:22 +0000 (UTC) (envelope-from philip@freebsd.org) Received: from rincewind.trouble.is (rincewind.trouble.is [IPv6:2a01:4f9:2a:1715::1:1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits)) (Client CN "rincewind.trouble.is", Issuer "Let's Encrypt Authority X3" (verified OK)) by weatherwax.trouble.is (Postfix) with ESMTPS id 4CPxMV1FfTz1kDp; Mon, 2 Nov 2020 15:16:22 +0000 (UTC) Received: by rincewind.trouble.is (Postfix, authenticated sender philip) id 4CPxMQ5Szbz516w; Mon, 2 Nov 2020 15:16:18 +0000 (UTC) From: "Philip Paeps" To: "Ronald Klop" Cc: "Steve Wills" , "Kurt Jaeger" , freebsd-arm@freebsd.org, "Cluster Administrators" Subject: Re: aarch64 pkg build seems broken/hanging Date: Mon, 02 Nov 2020 23:16:14 +0800 X-Clacks-Overhead: GNU Terry Pratchett X-Mailer: MailMate (1.13.2r5726) Message-ID: <4B49B4B6-FA22-4B73-BD50-E7023D889A97@freebsd.org> In-Reply-To: References: <735767609.10.1597159067683@localhost> <504493339.1.1597829845980@localhost> <1268679721.21.1598955250524@localhost> <2128344036.116.1599572445531@localhost> <93ab93ce-8887-315e-c775-0929c716032a@FreeBSD.org> <20200909142039.GK53210@home.opsec.eu> MIME-Version: 1.0 Content-Type: text/plain; format=flowed X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Nov 2020 15:16:23 -0000 On 2020-11-01 19:28:24 (+0800), Ronald Klop wrote: > On Wed, 09 Sep 2020 16:20:39 +0200, Kurt Jaeger wrote: >>> Sorry, but this is not a portmgr@ issue, this is a clusteradm@ >>> issue. >> >> philip@ (with clusteradm@ hat) checked the issue and explained the >> cause of the problem: >> >> The thunderx hardware currently in use in the cluster is a very early >> version and has stability issues. A replacement is @work. > > I don't want to be pushing the issue, but do you have some information > about the progress of the aarch64 hardware issues? New hardware has reportedly been ordered and we're waiting for it to arrive at our NYI site. When the hardware turns up, we'll install it. Thanks for keeping our feet close to the fire! Philip -- Philip Paeps Senior Reality Engineer Alternative Enterprises