From nobody Fri Feb 11 01:25:13 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 770F319B0714 for ; Fri, 11 Feb 2022 01:25:17 +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 4JvwsT2cd2z3H2q; Fri, 11 Feb 2022 01:25:17 +0000 (UTC) (envelope-from philip@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1644542717; 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=5Boq2f4FgxJ02DOC00zN4JpLY2Crw0oFClOYXI4+b6M=; b=OFyB9L37WUAS0LieerB2pn9ZCTRJlHWV5gSC3yo4S0yO94ifjFlL0OWyRve19UnK9Qr2EK Fj4tKYKLupnA6oZWaiGq2gc4xVzX1Ew8kYFFIw5r+pWftduqjNVWTA2A2H1eyeBLKy9jwz K4esJJsM1DPpGBfLGfXmtPIqWBg47zFJXr4GgkLw0qZFaYF9oTqTXb1aSv7EVARB+Vvk87 8OAiL9J/222DkzjBmWWdlUobWX2jWcpV0wauN5kBbke/+ZGK/BYIzGdwr05dCw3Y68/axB FsPvCQ60uwbzvKcaeIyCpSNS3nttR3POxzjEur+nbSIwyC3iXMRwnGtLD1v/RA== Received: from auth1-smtp.messagingengine.com (auth1-smtp.messagingengine.com [66.111.4.227]) (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 30482648B; Fri, 11 Feb 2022 01:25:17 +0000 (UTC) (envelope-from philip@freebsd.org) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailauth.nyi.internal (Postfix) with ESMTP id 200C527C0054; Thu, 10 Feb 2022 20:25:17 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute4.internal (MEProxy); Thu, 10 Feb 2022 20:25:17 -0500 X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvvddriedvgddvlecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecufghrlhcuvffnffculddutddmnecujfgurhephffvuf ffoffkjghfgggtsegrtdhmreertdejnecuhfhrohhmpefrhhhilhhiphcurfgrvghpshcu oehphhhilhhiphesfhhrvggvsghsugdrohhrgheqnecuggftrfgrthhtvghrnhepkedtge ehteekffdvleduhfelgffhhfeftdegudefhedugfeufeetkeegvdfhuedunecuffhomhgr ihhnpehiphhviehprhhogiihrdhnvghtpdhfrhgvvggsshgurdhorhhgnecuvehluhhsth gvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepphhhihhlihhpodhmvghs mhhtphgruhhthhhpvghrshhonhgrlhhithihqdduudeiiedviedvgeekqddvfeehudektd dtkedqphhhihhlihhppeepfhhrvggvsghsugdrohhrghesthhrohhusghlvgdrihhs X-ME-Proxy: Received: by mail.messagingengine.com (Postfix) with ESMTPA; Thu, 10 Feb 2022 20:25:14 -0500 (EST) From: Philip Paeps To: Ronald Klop Cc: clusteradm@freebsd.org, Ports Management Team , freebsd-arm@freebsd.org Subject: Re: aarch64 build cluster and linux64.ko Date: Fri, 11 Feb 2022 09:25:13 +0800 X-Mailer: MailMate (1.14r5869) Message-ID: <1666CD64-2A90-4BBC-9DEF-C9BCED4738FF@freebsd.org> In-Reply-To: <787825862.6.1644527984584@mailrelay> References: <1365005114.369.1643120837534@localhost> <993C6A92-7412-4426-903C-A2214B8A8031@freebsd.org> <55D4000E-2691-442D-9E46-E1966750344A@freebsd.org> <787825862.6.1644527984584@mailrelay> 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: multipart/alternative; boundary="=_MailMate_FD889266-A938-4762-AFCB-F7BF76969485_=" Embedded-HTML: [{"plain":[52,2930],"uuid":"1CD4FC1F-5F7F-4A46-B2A7-CB223D1AF1D9"}] ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1644542717; 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=5Boq2f4FgxJ02DOC00zN4JpLY2Crw0oFClOYXI4+b6M=; b=WRprFbC+xFzGTqoZz0OjQL/8SlsLVP/gmKP2uMAGL0DQpEIZMiIc52UhHqNIaJKVkrNF82 7dAvCGWqG/2yCl6nJ8XaQJuqqjmvzBCnb+wTCoUjs2e9hCAw5Bkqxrg38gmsMiGOUNgPnR QSylphdCl0+nF8QNecgZMdlz6uQMt4JzRPnx+D54k9vlkOH1BgTqeC1efNEepV2hUk2+xw OkFCcbLqQB47z4QE6zPM0EpPz+zleT4zlRADEquahxKbm1z3LWm8rDA20gL3PUSmvOsMXG IQd8cYHj13DLd263WbMLDxwG5tool10eWbK0romCm7GWniDk41esiAeFXpokKA== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1644542717; a=rsa-sha256; cv=none; b=cjX0ByWJVBoiKsnj5MkzVXjhDf9VYJJNH4tfXuiz9q6akmREMHF0e0vRNkxfet/5V1r/V4 X06IUHYnmse8Gyu4Jw0bKzX1SFq7uqxneQ3Umke9WAzZICA+PulQrtvpcy9naGn4zWMBEk S7WE+s0TTJsYnAuKdfr7YXVHcSCEOalzwuH4aDpJjW2kIm5ELnpy29ucaKhX+PM2SUiOjI uws9vTbZ9F6Y9fU42aoPPfdwVYxV5cu/kp6pgm+0zy8Cx9aG+FiwgaXHs4EEmy3lUCDUE1 jnwhuZdJvPK78m8k2GQ2L2wTDoU7YteM0GsC/zAmlpPssEnRySC3TzkVxHZi5w== ARC-Authentication-Results: i=1; mx1.freebsd.org; none X-ThisMailContainsUnwantedMimeParts: N --=_MailMate_FD889266-A938-4762-AFCB-F7BF76969485_= Content-Type: text/plain; format=flowed Content-Transfer-Encoding: quoted-printable On 2022-02-11 05:19:44 (+0800), Ronald Klop wrote: > Van: Philip Paeps > Datum: maandag, 31 januari 2022 04:15 > Aan: Ronald Klop > CC: clusteradm@freebsd.org, freebsd-arm@freebsd.org, Ports Management = > Team > Onderwerp: Re: aarch64 build cluster and linux64.ko >> >> On 2022-01-26 08:58:20 (+0800), Philip Paeps wrote: >>> On 2022-01-25 22:27:17 (+0800), Ronald Klop wrote: >>>> Currently the packages depending on linux_base-c7 can not be >> = >>>> pre-build on the package cluster because the kernel does not have = >>>> >> linux64.ko loaded. >>>> >>>> See: >> = >>>> http://www.ipv6proxy.net/go.php?u=3Dhttp%3A%2F%2Fampere2.nyi.freebsd= =2Eorg%2Fdata%2Fmain-arm64-default%2Fpd8f8cc3a8823_s4f0e50b293%2Flogs%2Fe= rrors%2Flinux-c7-libpng-1.5.13_3.log&b=3D0&f=3Dnorefer >>>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= > = >>>> >=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D >>>> =3D=3D=3D> linux-c7-libpng-1.5.13_3 depends on package: >> = >>>> linux_base-c7>=3D7.6.1810_7 - not found >>>> =3D=3D=3D> Installing existing package >> = >>>> /packages/All/linux_base-c7-7.9.2009.pkg >>>> [main-arm64-default-job-01] Installing linux_base-c7-7.9.2009... >>>> Cannot install package: kernel missing 64-bit Linux support >>>> pkg-static: PRE-INSTALL script failed >>>> >>>> >>>> Is it possible to have linux64.ko loaded on the pkg builders so the = >>>> >> aarch64 packages will be more complete? >>>> >>>> At least on my rpi4/aarch64 poudriere I could build pkg >> = >>>> linux-c7-libpng with linux64.ko loaded. >>> >>> We can include linux64.ko in the next cluster build for aarch64. = >>> I'll > try to find time for another cluster refresh. It's been a = >>> while since > the last one. >> >> 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. >> >> Philip >> >> -- = >> Philip Paeps >> Senior Reality Engineer >> Alternative Enterprises >> >> >> > > Hi, > > Ampere1 as well as ampere2 are upgraded but I do not see the effect of = > linux64.ko being loaded. > > e.g. = > http://ampere2.nyi.freebsd.org/data/main-arm64-default/p4970d39a547c_s5= 11b83b167/logs/errors/linux-c7-lz4-1.8.3.log = > : > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D > =3D=3D=3D> linux-c7-lz4-1.8.3 depends on package: = > linux_base-c7>=3D7.6.1810_7 - not found > =3D=3D=3D> Installing existing package = > /packages/All/linux_base-c7-7.9.2009.pkg > [main-arm64-default-job-13] Installing linux_base-c7-7.9.2009... > Cannot install package: kernel missing 64-bit Linux support > pkg-static: PRE-INSTALL script failed > > I can easily reproduce this error on my local poudriere by not loading = > the module linux64.ko. If it is loaded the linux-c7-* ports build = > fine. > Having this fixed will give quite a lot less failed+skipped ports on = > aarch64. > Who can I ask to check this? > > Regards, > Ronald. I have loaded the module on ampere1 and ampere2 and added = linux64_load=3D"YES" to their /boot/loader.conf files. I have also done = this on the new ampere3 machine portmgr hasn't taken into production yet = (I only installed that one yesterday). If that's all it takes, it should be picked up in the next build. If = poudriere needs to be taught something ... that's really a portmgr task. Philip -- = Philip Paeps Senior Reality Engineer Alternative Enterprises --=_MailMate_FD889266-A938-4762-AFCB-F7BF76969485_= Content-Type: text/html Content-Transfer-Encoding: quoted-printable

On 2022-02-11 05:19:44 (+080= 0), Ronald Klop wrote:

 

Van: Philip Paeps <philip@freebsd.org>
Datum: maandag, 31 januari 2022 04:15
Aan: Ronald Klop <ronald-lists@klop.ws>
CC: clusteradm@freebsd.org, freebsd-arm@freebsd.org, Por= ts Management Team <portmgr@freebsd.org>
Onderwerp: Re: aarch64 build cluster and linux64.ko

On 2022-01-26 08:58:20 (+0800),= Philip Paeps wrote:
> On 2022-01-25 22:27:17 (+0800), Ronald Klop wrote:
>> Currently the packages depending on linux_base-c7 can not be >= ;> pre-build on the package cluster because the kernel does not have &= gt;> linux64.ko loaded.
>>
>> See: >> http://www.ipv6proxy.net/go.php?u=3Dhttp%3A%2F%2Fampere= 2.nyi.freebsd.org%2Fdata%2Fmain-arm64-default%2Fpd8f8cc3a8823_s4f0e50b293= %2Flogs%2Ferrors%2Flinux-c7-libpng-1.5.13_3.log&b=3D0&f=3Dnorefer=
>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D<phase: run-depends    
>> >=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D
>> =3D=3D=3D>   linux-c7-libpng-1.5.13_3 depends on pa= ckage: >> linux_base-c7>=3D7.6.1810_7 - not found
>> =3D=3D=3D>   Installing existing package >> /= packages/All/linux_base-c7-7.9.2009.pkg
>> [main-arm64-default-job-01] Installing linux_base-c7-7.9.2009...=
>> Cannot install package: kernel missing 64-bit Linux support
>> pkg-static: PRE-INSTALL script failed
>>
>>
>> Is it possible to have linux64.ko loaded on the pkg builders so = the >> aarch64 packages will be more complete?
>>
>> At least on my rpi4/aarch64 poudriere I could build pkg >>= linux-c7-libpng with linux64.ko loaded.
>
> We can include linux64.ko in the next cluster build for aarch64. &nb= sp;I'll > try to find time for another cluster refresh.  It's bee= n a while since > the last one.

I've upgraded one of the package builders (ampere1.nyi.freebsd.org) with = a build including linux64.ko.  The module seems to load.  portm= gr 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 curre= nt build.

Philip

-- 
Philip Paeps
Senior Reality Engineer
Alternative Enterprises

Hi,

Ampere1 as well as ampere2 are upgraded but I do not see the effect of li= nux64.ko being loaded.

e.g. http://ampere2.nyi.freebsd.org/data/main-arm64-default/p4970d39a547c= _s511b83b167/logs/errors/linux-c7-lz4-1.8.3.log : 
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<=
phase: run-depends    >=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
=3D=3D=3D>   linux-c7-lz4-1.8.3 depends on package: linux_base-c7>=3D=
7.6.1810_7 - not found
=3D=3D=3D>   Installing existing package /packages/All/linux_base-c7-7=
=2E9.2009.pkg
[main-arm64-default-job-13] Installing linux_base-c7-7.9.2009...
Cannot install package: kernel missing 64-bit Linux support
pkg-static: PRE-INSTALL script failed

I can easily reproduce this error on my local poudriere by not loading th= e module linux64.ko. If it is loaded the linux-c7-* ports build fine.
= Having this fixed will give quite a lot less failed+skipped ports on aarc= h64.
Who can I ask to check this?

Regards,
Ronald.
 


I have loaded the module on ampere1 and ampere2 and added linux64_load=3D= "YES" to their /boot/loader.conf files. I have also done this on the new= ampere3 machine portmgr hasn't taken into production yet (I only install= ed that one yesterday).

If that's all it takes, it should be picked up in the nex= t build. If poudriere needs to be taught something ... that's really a p= ortmgr task.

Philip

-- =
Philip Paeps
Senior Reality Engineer
Alternative Enterprises

--=_MailMate_FD889266-A938-4762-AFCB-F7BF76969485_=--