From owner-freebsd-arm@freebsd.org Sun Nov 1 11:28:27 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 447E244A6A6 for ; Sun, 1 Nov 2020 11:28:27 +0000 (UTC) (envelope-from ronald-lists@klop.ws) Received: from smarthost1.greenhost.nl (smarthost1.greenhost.nl [195.190.28.88]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4CPDLy1t83z42V7; Sun, 1 Nov 2020 11:28:26 +0000 (UTC) (envelope-from ronald-lists@klop.ws) Received: from smtp.greenhost.nl ([213.108.110.112]) by smarthost1.greenhost.nl with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1kZBX5-0003fh-Td; Sun, 01 Nov 2020 12:28:24 +0100 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=klop.ws; s=mail; h=In-Reply-To:Message-ID:From:Content-Transfer-Encoding:MIME-Version: Date:References:Subject:Cc:To:Content-Type:Sender:Reply-To:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=FXyCYuwa3kCSu70DEkGsICGdGYiMPH9cGHUqg1jPV6Q=; b=ojLfHx3Rxxfo2LQ8w97VUwcoIX UJNRsgRd5Vb4ompTFqL0sKlobccgNl+1Zjg43BHiOmTUhWlQ4yssx2a24se3tMEegRWNmEb226gzO gRoCEIBdmu8TSOER5vPhY+gw/sSrRyIx8c7sW9eLnHDpTGonZL3cGf2Zg3VeZ4toU96g=; Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes To: "Steve Wills" , "Kurt Jaeger" Cc: freebsd-arm@freebsd.org, "Cluster Administrators" Subject: Re: aarch64 pkg build seems broken/hanging 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> Date: Sun, 01 Nov 2020 12:28:24 +0100 MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: "Ronald Klop" Message-ID: In-Reply-To: <20200909142039.GK53210@home.opsec.eu> User-Agent: Opera Mail/12.16 (FreeBSD) X-Authenticated-As-Hash: 398f5522cb258ce43cb679602f8cfe8b62a256d1 X-Virus-Scanned: by clamav at smarthost1.samage.net X-Spam-Level: / X-Spam-Score: -0.4 X-Spam-Status: No, score=-0.4 required=5.0 tests=ALL_TRUSTED, BAYES_50, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF autolearn=disabled version=3.4.2 X-Scan-Signature: 739ba1b2be5fabc1cc6069058737919f X-Rspamd-Queue-Id: 4CPDLy1t83z42V7 X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=klop.ws header.s=mail header.b=ojLfHx3R; dmarc=none; spf=pass (mx1.freebsd.org: domain of ronald-lists@klop.ws designates 195.190.28.88 as permitted sender) smtp.mailfrom=ronald-lists@klop.ws X-Spamd-Result: default: False [-2.15 / 15.00]; RCVD_TLS_ALL(0.00)[]; ARC_NA(0.00)[]; R_DKIM_ALLOW(-0.20)[klop.ws:s=mail]; NEURAL_HAM_MEDIUM(-0.99)[-0.990]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[4]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:195.190.28.64/27]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[klop.ws]; NEURAL_HAM_LONG(-0.99)[-0.990]; RWL_MAILSPIKE_GOOD(0.00)[195.190.28.88:from]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[klop.ws:+]; NEURAL_HAM_SHORT(-0.17)[-0.167]; RCVD_IN_DNSWL_NONE(0.00)[195.190.28.88:from]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; MID_RHS_NOT_FQDN(0.50)[]; ASN(0.00)[asn:47172, ipnet:195.190.28.0/24, country:NL]; RCVD_COUNT_TWO(0.00)[2]; MAILMAN_DEST(0.00)[freebsd-arm] 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: Sun, 01 Nov 2020 11:28:27 -0000 On Wed, 09 Sep 2020 16:20:39 +0200, Kurt Jaeger 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.