From nobody Fri Feb 04 11:05:44 2022 X-Original-To: freebsd-arm@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 18A5119A5247 for ; Fri, 4 Feb 2022 11:05:50 +0000 (UTC) (envelope-from philip@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (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 "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Jqt4Z01Yfz3hZB; Fri, 4 Feb 2022 11:05:50 +0000 (UTC) (envelope-from philip@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1643972750; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=NIvun3QJ35cNLRf5dNRzh+2jANXJaO/k5szopZu5I5Y=; b=VRL4BjaFRtwdJGk2qMPiO2QZTcR7wuPtK+m7wGThjoagnwvoV3RJWJeZ+2SU2GT0jhf64C P4roNIWagKXMuaxFrzgXRGsR4D4t/Fce/6+UYIQxKjJqy91yJuDekQARMh3vCTUIEaNFYn jpx6syAq9JSqlxHrOq+YJ4Jf8ExLd4GuNe8jVOTC14Z4efAeOCUmw/NQBGcPbBlgWAjp+4 WIukeRKKF6NAcHfu26GjOZeNZIQfi+iL+MrIfVZnAbsLTrogCebgUeZ+US0hbMA7PiqWDI oPYM4YHFg+SPiTOBq+pohTFVP9h8jePMoJons738V6WFMhUUqrEdkIisG+1s8A== Received: from auth2-smtp.messagingengine.com (auth2-smtp.messagingengine.com [66.111.4.228]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) (Authenticated sender: philip/mail) by smtp.freebsd.org (Postfix) with ESMTPSA id CAF0D2FE6F; Fri, 4 Feb 2022 11:05:49 +0000 (UTC) (envelope-from philip@freebsd.org) Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailauth.nyi.internal (Postfix) with ESMTP id AA00D27C0054; Fri, 4 Feb 2022 06:05:49 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute5.internal (MEProxy); Fri, 04 Feb 2022 06:05:49 -0500 X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvvddrgeelgddvfecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhephffvufffoffkjghfgggtsehttdhmtd ertddtnecuhfhrohhmpefrhhhilhhiphcurfgrvghpshcuoehphhhilhhiphesfhhrvggv sghsugdrohhrgheqnecuggftrfgrthhtvghrnhepjeeluefhjeekteetgffhveeftdeitd ehkeeuvdeuveefvdfghfegffffheejtddunecuffhomhgrihhnpehfrhgvvggsshgurdho rhhgnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepph hhihhlihhpodhmvghsmhhtphgruhhthhhpvghrshhonhgrlhhithihqdduudeiiedviedv geekqddvfeehudektddtkedqphhhihhlihhppeepfhhrvggvsghsugdrohhrghesthhroh husghlvgdrihhs X-ME-Proxy: Received: by mail.messagingengine.com (Postfix) with ESMTPA; Fri, 4 Feb 2022 06:05:47 -0500 (EST) From: Philip Paeps To: Ronald Klop Cc: Ports Management Team , freebsd-arm@freebsd.org, clusteradm@freebsd.org Subject: Re: aarch64 build cluster and linux64.ko Date: Fri, 04 Feb 2022 19:05:44 +0800 X-Mailer: MailMate (1.14r5864) Message-ID: In-Reply-To: <1041004715.975.1643961552511@localhost> References: <1041004715.975.1643961552511@localhost> List-Id: Porting FreeBSD to ARM processors List-Archive: https://lists.freebsd.org/archives/freebsd-arm List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arm@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; format=flowed ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1643972750; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=NIvun3QJ35cNLRf5dNRzh+2jANXJaO/k5szopZu5I5Y=; b=yAq3UEuQkLDfER0hgJqj7u9t/3dB/EDl0wM65fVpE2J9WvcIMTUEWRrffXTjLBRZXCWe1v UMotm//RELonhPRmYRW/vAaB1DXsmsvd8Fz9ERxL1pCtsV5j/YGVWRLm9bAh7zK1JCFh0m 5BX0srIh+LqGfyY9Xl6iIhr8KkF6f6KEDIt6JWmEeaxjRj5QAW/zbj/GqUHVYKGqf/lZpr y+2fTBaUxIxIf67Jg7D8izrtKg+uKusYFgObnKJY8IKgLVoSQWGrxmJ6ZOOu9CE2ohtuII 8tEL4HSlnyDs7u6g8+FnPRAU/Pi1IWA4QWCW5Ut4ppRNJ7cYUlotrEKlVGqwiQ== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1643972750; a=rsa-sha256; cv=none; b=FZfKfnqZ51E6m+C9UJlIcoYJzCcMYQd2j/ZTgHc2fn4uv3yJCN9WsrkrVOxpqJSBgNhf+O nNgRXf+TCo4xiBxOYcKZJ1qBx7cn6T1e/DF9fvqpj42WxQ958uyKxkAoQ97mQy010BKs7A SmFIjhKBy5nvOfLduY2gUCjs9LeivWztxZWI2hJ+7b4jaVlCKwikKixXk50CQ63RPXkU1d WzKrwAyl91JahkXC0mnp3e9xU4Rv+hMm4UwXBk0oN78dXYx9sCo65/yizNe90FNeRJI2Xj yPwj9v+jCFx0g2Zmu/9lYkuNx7dcCcojVLjVZ7xGPDHZxbtCw3G91HMYDkM1GQ== ARC-Authentication-Results: i=1; mx1.freebsd.org; none X-ThisMailContainsUnwantedMimeParts: N On 2022-02-04 15:59:12 (+0800), Ronald Klop wrote: > Philip Paeps wrote: >> On 2022-01-26 08:58:20 (+0800), Philip Paeps wrote: >> I've upgraded one of the package builders (ampere1.nyi.freebsd.org) >> with a build including linux64.ko. The module seems to load. >> portmgr might need to do something to the builds to actually use it >> though. >> >> I'll upgrade the other aarch64 package builder when it finishes its >> current build. > > Thank you. 122arm64 quarterly build fine. 130arm64 quarterly is > hanging in :sanity: for 48 hours already. I think it is stuck. Would > you have time to check? If I understand the automation/scheduling correctly, ampere1 started a new 130arm64 quarterly build while I was upgrading it. That build got stuck in :sanity:. After being upgraded, it started on the next build in the queue, which is still running now. I believe it should start on a 130arm64 build after this. Philip -- Philip Paeps Senior Reality Engineer Alternative Enterprises