Date: Mon, 02 Nov 2020 23:16:14 +0800 From: "Philip Paeps" <philip@freebsd.org> To: "Ronald Klop" <ronald-lists@klop.ws> Cc: "Steve Wills" <swills@freebsd.org>, "Kurt Jaeger" <pi@opsec.eu>, freebsd-arm@freebsd.org, "Cluster Administrators" <clusteradm@freebsd.org> Subject: Re: aarch64 pkg build seems broken/hanging Message-ID: <4B49B4B6-FA22-4B73-BD50-E7023D889A97@freebsd.org> In-Reply-To: <op.0teh5mejkndu52@sjakie> References: <735767609.10.1597159067683@localhost> <op.0pf4q6ofkndu52@sjakie> <504493339.1.1597829845980@localhost> <1268679721.21.1598955250524@localhost> <2128344036.116.1599572445531@localhost> <93ab93ce-8887-315e-c775-0929c716032a@FreeBSD.org> <20200909142039.GK53210@home.opsec.eu> <op.0teh5mejkndu52@sjakie>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2020-11-01 19:28:24 (+0800), Ronald Klop wrote: > On Wed, 09 Sep 2020 16:20:39 +0200, Kurt Jaeger <pi@opsec.eu> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4B49B4B6-FA22-4B73-BD50-E7023D889A97>