Date: Sun, 01 Nov 2020 12:28:24 +0100 From: "Ronald Klop" <ronald-lists@klop.ws> To: "Steve Wills" <swills@freebsd.org>, "Kurt Jaeger" <pi@opsec.eu> Cc: freebsd-arm@freebsd.org, "Cluster Administrators" <clusteradm@freebsd.org> Subject: Re: aarch64 pkg build seems broken/hanging Message-ID: <op.0teh5mejkndu52@sjakie> In-Reply-To: <20200909142039.GK53210@home.opsec.eu> 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>
index | next in thread | previous in thread | raw e-mail
On Wed, 09 Sep 2020 16:20:39 +0200, Kurt Jaeger <pi@opsec.eu> wrote: > Hi! > >> 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. > Dear clusteradm, I don't want to be pushing the issue, but do you have some information about the progress of the aarch64 hardware issues? Regards, Ronald.home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?op.0teh5mejkndu52>