From nobody Sat Apr 15 11:24:05 2023 X-Original-To: freebsd-hackers@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 4Pz9tx6Qqxz458lR for ; Sat, 15 Apr 2023 11:24:09 +0000 (UTC) (envelope-from void@f-m.fm) Received: from wout1-smtp.messagingengine.com (wout1-smtp.messagingengine.com [64.147.123.24]) (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 did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4Pz9tw6GDDz3q4S for ; Sat, 15 Apr 2023 11:24:08 +0000 (UTC) (envelope-from void@f-m.fm) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=f-m.fm header.s=fm3 header.b=k9QJg9NJ; dkim=pass header.d=messagingengine.com header.s=fm3 header.b="a VoLnDH"; spf=pass (mx1.freebsd.org: domain of void@f-m.fm designates 64.147.123.24 as permitted sender) smtp.mailfrom=void@f-m.fm; dmarc=pass (policy=none) header.from=f-m.fm Received: from compute6.internal (compute6.nyi.internal [10.202.2.47]) by mailout.west.internal (Postfix) with ESMTP id B5C493200910 for ; Sat, 15 Apr 2023 07:24:07 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute6.internal (MEProxy); Sat, 15 Apr 2023 07:24:07 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=f-m.fm; h=cc :content-transfer-encoding:content-type:content-type:date:date :from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:sender:subject:subject:to:to; s=fm3; t= 1681557847; x=1681644247; bh=CAUUtb7oBN9jNRMqgtWzvhfoMJ19cw22eia IQ/4n1gU=; b=k9QJg9NJiSFRaXH03kPnD1AsvrFDos0lr3beLq22UKZloiiYn9y O7TosdcCKc4bByxr1WAC8WTQyrvXIj30dFOXz7xRpp3Mirx5Wis5ol4Gy2sA0IVN idanMHkHo08zjGCXuL5+XXXo6OWMCeqGOsXx1Idy/20VIv84yCnga8HMX/0nNXjA pSRCf2S12uteFtj1+goxMZFDY1XZ8xIrkLGoEqeI+5wE7jgq97be5as0uWdgbQEc 4eJKfF61yDteWjas0DhAn7ZhfAqABh+Fk0VwP0lATdeQuxwwntjpslHizs6ZPyRr IvATll0N8W8YbNShrUei0+ES/CIUjyBi5EQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :content-type:date:date:feedback-id:feedback-id:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:sender:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm3; t=1681557847; x= 1681644247; bh=CAUUtb7oBN9jNRMqgtWzvhfoMJ19cw22eiaIQ/4n1gU=; b=a VoLnDHfEEiuNIsMmA2YQtGzd5Hi+TJNSVCAFdGmx83ZVcER9mK9/+X0OvO8R+fWW ABTEdJLV483eihzHsSAS3deOOXz8QL4phLpzwjDQvgLGBDQRnkJR1CAaWe+hPuvI WxGEBs3P735BFHN6hRGFBmdF05TDYRIBKM3EatN7dYEgSG2ovkz0OydBKP3F2nTQ 7FoOSOaa+LZHVazgfuLu31u1bEl/dsyn1BMYOfaOtt4A1pw88I+U2q4rR60A30f0 HLrTaqDC36kW3YOM2gpt4NXqmn9SJxlGfFoz2Wcr3fpAXBwbWYSrsowhTwy7Sdwg XXj2OhtCyVjNP4zaaYqlw== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedrvdelvddgfeejucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpeffhffvuffkfhggtggugfgjsehtke ertddttdejnecuhfhrohhmpehvohhiugcuoehvohhiugesfhdqmhdrfhhmqeenucggtffr rghtthgvrhhnpeduteevgeeggeevieetvdduudetfffffffhteejgffggeevjeffiedute eftedvkeenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhm pehvohhiugesfhdqmhdrfhhm X-ME-Proxy: Feedback-ID: i2541463c:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA for ; Sat, 15 Apr 2023 07:24:06 -0400 (EDT) Date: Sat, 15 Apr 2023 12:24:05 +0100 From: void To: freebsd-hackers@freebsd.org Subject: Re: sccache and sccache-overlay Message-ID: Mail-Followup-To: freebsd-hackers@freebsd.org References: <26c69307-5e32-16f4-898e-5ad5747ff1d7@freebsd.org> List-Id: Technical discussions relating to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-hackers List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-hackers@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: X-Spamd-Result: default: False [-4.47 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; DWL_DNSWL_LOW(-1.00)[messagingengine.com:dkim]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.87)[-0.871]; MID_RHS_NOT_FQDN(0.50)[]; DMARC_POLICY_ALLOW(-0.50)[f-m.fm,none]; R_DKIM_ALLOW(-0.20)[f-m.fm:s=fm3,messagingengine.com:s=fm3]; R_SPF_ALLOW(-0.20)[+ip4:64.147.123.24:c]; MIME_GOOD(-0.10)[text/plain]; RCVD_IN_DNSWL_LOW(-0.10)[64.147.123.24:from]; FREEMAIL_ENVFROM(0.00)[f-m.fm]; PREVIOUSLY_DELIVERED(0.00)[freebsd-hackers@freebsd.org]; TO_DN_NONE(0.00)[]; RCVD_COUNT_THREE(0.00)[4]; RCPT_COUNT_ONE(0.00)[1]; MLMMJ_DEST(0.00)[freebsd-hackers@freebsd.org]; FREEMAIL_FROM(0.00)[f-m.fm]; MIME_TRACE(0.00)[0:+]; TO_MATCH_ENVRCPT_ALL(0.00)[]; DKIM_TRACE(0.00)[f-m.fm:+,messagingengine.com:+]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:29838, ipnet:64.147.123.0/24, country:US]; FROM_HAS_DN(0.00)[]; RWL_MAILSPIKE_POSSIBLE(0.00)[64.147.123.24:from]; FROM_EQ_ENVFROM(0.00)[]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[] X-Rspamd-Queue-Id: 4Pz9tw6GDDz3q4S X-Spamd-Bar: ---- X-ThisMailContainsUnwantedMimeParts: N On Sat, Apr 15, 2023 at 11:39:03AM +0100, void wrote: >On Sat, Apr 15, 2023 at 09:45:54AM +0100, Graham Perrin wrote: >>On 15/04/2023 01:13, void wrote: >> >>> … sometimes … >> >>> Running poudriere again, and the problem is gone … >> >>Which versions of FreeBSD (jail and host), exactly? >> > >host is main-n261613-2b4b3789f877 amd64 1400083 1400083 built >19th March. > >poudriere jail is 13.2-STABLE 1302504 amd64 built 3rd March identical problem, same host, different poudriere jail, different package: [00:00:00] Host OSVERSION: 1400083 [00:00:00] Jail OSVERSION: 1301000 [00:00:05] ===> Configuring for libxml2-2.10.3_2 [00:00:05] ==> Starting sccache [00:00:05] sccache: Starting the server... [00:00:15] sccache: error: Timed out waiting for server startup [00:00:15] sccache: error: No such file or directory (os error 2) [00:00:15] *** Error code 2 [00:00:15] [00:00:15] Stop. [00:00:15] make: stopped in /usr/ports/textproc/libxml2 -- From nobody Sun Apr 16 08:36:40 2023 X-Original-To: freebsd-hackers@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 4Pzk7Q3hp9z44vbM for ; Sun, 16 Apr 2023 08:36:50 +0000 (UTC) (envelope-from thierry@pompo.net) Received: from erza.lautre.net (erza.lautre.net [80.67.160.89]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "lautre.net", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Pzk7N6yk6z4Hbr for ; Sun, 16 Apr 2023 08:36:48 +0000 (UTC) (envelope-from thierry@pompo.net) Authentication-Results: mx1.freebsd.org; dkim=none; spf=pass (mx1.freebsd.org: domain of thierry@pompo.net designates 80.67.160.89 as permitted sender) smtp.mailfrom=thierry@pompo.net; dmarc=none Received: from graf.pompo.net (graf.pompo.net [82.66.0.218]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by erza.lautre.net (Postfix) with ESMTPSA id F251EE80DC for ; Sun, 16 Apr 2023 10:36:40 +0200 (CEST) Received: by graf.pompo.net (Postfix, from userid 1001) id 6BE59DCFAF2; Sun, 16 Apr 2023 10:36:40 +0200 (CEST) Date: Sun, 16 Apr 2023 10:36:40 +0200 From: Thierry Thomas To: freebsd-hackers@freebsd.org Subject: Re: Periodic rant about SCHED_ULE Message-ID: Mail-Followup-To: freebsd-hackers@freebsd.org References: <6A29E7ED-0A1E-49F9-9224-AC3D5B0E0732.ref@yahoo.com> <6A29E7ED-0A1E-49F9-9224-AC3D5B0E0732@yahoo.com> List-Id: Technical discussions relating to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-hackers List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-hackers@freebsd.org MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="y6yU3oE7ZO8ZAHDd" Content-Disposition: inline In-Reply-To: X-Operating-System: FreeBSD 13.1-STABLE amd64 Organization: Kabbale Eros X-Face: (hRbQnK~Pt7$ct`!fupO(`y_WL4^-Iwn4@ly-.,[4xC4xc;y=\ipKMNm<1J>lv@PP~7Z<.tKjAnXLs: X-PGP: 0xF1C516B3C8359753 X-Spamd-Result: default: False [-1.72 / 15.00]; SIGNED_PGP(-2.00)[]; RBL_VIRUSFREE_BOTNET(2.00)[80.67.160.89:from]; NEURAL_HAM_MEDIUM(-0.98)[-0.979]; NEURAL_HAM_LONG(-0.83)[-0.829]; FORGED_SENDER(0.30)[thierry@freebsd.org,thierry@pompo.net]; MIME_GOOD(-0.20)[multipart/signed,text/plain]; NEURAL_HAM_SHORT(-0.12)[-0.117]; BAD_REP_POLICIES(0.10)[]; DMARC_NA(0.00)[freebsd.org]; FREEFALL_USER(0.00)[thierry]; RCPT_COUNT_ONE(0.00)[1]; FROM_HAS_DN(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-hackers@freebsd.org]; TO_MATCH_ENVRCPT_ALL(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; TO_DOM_EQ_FROM_DOM(0.00)[]; FROM_NEQ_ENVFROM(0.00)[thierry@freebsd.org,thierry@pompo.net]; HAS_ORG_HEADER(0.00)[]; TO_DN_NONE(0.00)[]; R_SPF_ALLOW(0.00)[+mx]; ARC_NA(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; R_DKIM_NA(0.00)[]; RCVD_TLS_LAST(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; ASN(0.00)[asn:20766, ipnet:80.67.160.0/19, country:FR]; MLMMJ_DEST(0.00)[freebsd-hackers@freebsd.org] X-Rspamd-Queue-Id: 4Pzk7N6yk6z4Hbr X-Spamd-Bar: - X-ThisMailContainsUnwantedMimeParts: N --y6yU3oE7ZO8ZAHDd Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Le sam. 25 mars 23 =C3=A0 20:02:43 +0100, Thierry Thomas =C3=A9crivait=C2=A0: > Le ven. 24 mars 23 =C3=A0 21:25:16 +0100, Steve Kargl > =C3=A9crivait=C2=A0: > > I can repeat the openmpi testing, but it will have to=20 > > wait for a few weeks as I have a pressing deadline. > Just a note: Intel MPI Benchmark is suitable for this kind of tests. > It is in our ports tree as benchmarks/imb, but very outdated and not > maintained. >=20 > Newer releases are now on GitHub: > . >=20 > It has been on my TODO-list to upgrade this port for quiet a long time, > but I=E2=80=99ve been busy on other side=E2=80=A6 If someone has some cyc= les, do not > hesitate! Done: . --=20 Th. Thomas. --y6yU3oE7ZO8ZAHDd Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQJ8BAEBCgBmBQJkO7OYXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRFNTM2QkU4NTM4NTM5OUQwMEI2RkFBNzZG MUM1MTZCM0M4MzU5NzUzAAoJEPHFFrPINZdTCxwP/Roj1AZwlAyevvMh4oVsRy2K LaLdocMbGHX9TeOQQHrPIupmb2PCT6b7YrdCDGPZaZVXhEFLCKRFkeW20l5ibUw0 efQX27/iN3gPULHJWnsXBoMNCtX+2UVOSLMTEMAjuFDym/6IhLn2nA5zpwxCPwpI YMlWjulz3Q107ni4sULfMw77oqXIBAneHMb+7jztp2A7rrkuTFbggS8sm2T9E5Dq FwkmAjnbDwSqvxHSIgTH4CTswMezUk2uAveLxvWpq/MCFxhcEB9rV6DBls0mzCH8 R8B559qpmBC8ZgTu0AJS9/6EVkk6z4iAOGZJ+cwln0KCEZOXDQbM5h3YJIn5vfON GddHC27EyYB2oZ6sI4WLuS6kJ4mKpMFKXXLqPDxO5fp8FQdXOqthsGjMEcNGHYbz JKsx8+UzJsMAi9pQKUmCPuidWIFM8n3ZP2tCIob3sayRfcVg9vrX2Nf4kNuBTlTo PxVKY524gB+vKnhGAp1YlWldDlXZ73U1z4jWDHjVFI+2GPlN0JEkZNcan/OvbmgW 4jSzj2J6aS8iUvWlqh8FtYc1hVgnm5pT1/JVMLGdOjeRV/fZnEI8GUPjSS+6nRnb 3HGUpZWChv7Ol6Z/GYTQZAlFKJIY5Dt4b7akjanGNwVe/H+lvT9MeXuPw0Ku1MvV zrsmdS0hb8nwEmxBG32x =9OOc -----END PGP SIGNATURE----- --y6yU3oE7ZO8ZAHDd-- From eugen@grosbein.net Mon Apr 17 11:53:31 2023 X-Original-To: freebsd-hackers@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 4Q0QSD4fgWz45nFL for ; Mon, 17 Apr 2023 11:53:48 +0000 (UTC) (envelope-from eugen@grosbein.net) Received: from hz.grosbein.net (hz.grosbein.net [IPv6:2a01:4f8:c2c:26d8::2]) (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 (2048 bits) client-digest SHA256) (Client CN "hz.grosbein.net", Issuer "hz.grosbein.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Q0QSC5mynz3rF9 for ; Mon, 17 Apr 2023 11:53:47 +0000 (UTC) (envelope-from eugen@grosbein.net) Authentication-Results: mx1.freebsd.org; dkim=none; spf=fail (mx1.freebsd.org: domain of eugen@grosbein.net does not designate 2a01:4f8:c2c:26d8::2 as permitted sender) smtp.mailfrom=eugen@grosbein.net; dmarc=fail reason="No valid SPF, No valid DKIM" header.from=grosbein.net (policy=none) Received: from eg.sd.rdtc.ru (root@eg.sd.rdtc.ru [62.231.161.221] (may be forged)) by hz.grosbein.net (8.17.1/8.17.1) with ESMTPS id 33HBrcQ7074659 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Mon, 17 Apr 2023 11:53:39 GMT (envelope-from eugen@grosbein.net) X-Envelope-From: eugen@grosbein.net X-Envelope-To: Lee.MATTHEWS.external@stormshield.eu Received: from [10.58.0.11] (dadvw [10.58.0.11] (may be forged)) by eg.sd.rdtc.ru (8.16.1/8.16.1) with ESMTPS id 33HBralT071571 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NOT); Mon, 17 Apr 2023 18:53:36 +0700 (+07) (envelope-from eugen@grosbein.net) Subject: Re: BINIT and BERR signals in MCA To: Lee MATTHEWS , "freebsd-hackers@FreeBSD.org" References: <4bd3e1017a104598ab92e658f25b5367@stormshield.eu> <24a51bf0-71de-f596-ef8b-785da4a27fd7@grosbein.net> <3a5479243699436d86ace8fff20db0ba@stormshield.eu> From: Eugene Grosbein Message-ID: <4727b400-c014-9014-9d0b-d4f15fee0e09@grosbein.net> Date: Mon, 17 Apr 2023 18:53:31 +0700 User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 List-Id: Technical discussions relating to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-hackers List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-hackers@freebsd.org MIME-Version: 1.0 In-Reply-To: <3a5479243699436d86ace8fff20db0ba@stormshield.eu> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED,SHORTCIRCUIT autolearn=disabled version=3.4.6 X-Spam-Report: * -0.0 SHORTCIRCUIT No description available. * -1.0 ALL_TRUSTED Passed through trusted hosts only via SMTP X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on hz.grosbein.net X-Spamd-Result: default: False [-1.16 / 15.00]; R_SPF_FAIL(1.00)[-all]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-0.92)[-0.920]; NEURAL_HAM_SHORT(-0.24)[-0.244]; MIME_GOOD(-0.10)[text/plain]; DMARC_POLICY_SOFTFAIL(0.10)[grosbein.net : No valid SPF, No valid DKIM,none]; MIME_TRACE(0.00)[0:+]; MLMMJ_DEST(0.00)[freebsd-hackers@FreeBSD.org]; R_DKIM_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; ASN(0.00)[asn:24940, ipnet:2a01:4f8::/32, country:DE]; RCVD_TLS_ALL(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; FREEFALL_USER(0.00)[eugen]; MID_RHS_MATCH_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; ARC_NA(0.00)[]; TO_DN_SOME(0.00)[]; TO_DN_EQ_ADDR_SOME(0.00)[] X-Rspamd-Queue-Id: 4Q0QSC5mynz3rF9 X-Spamd-Bar: - X-ThisMailContainsUnwantedMimeParts: N 17.04.2023 18:29, Lee MATTHEWS wrote: > The CPU temperature oscillates between 25 and 45 degrees Celsius, with a 10 second measurement interval. > Do you still think that temperature could be an issue? Unlikely. > Do you think defective RAM could produce this problem? It definitely could. From nobody Mon Apr 17 13:52:45 2023 X-Original-To: freebsd-hackers@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 4Q0T5n4mqxz45wWX for ; Mon, 17 Apr 2023 13:53:01 +0000 (UTC) (envelope-from david.robertsson@gmail.com) Received: from mail-pg1-x52c.google.com (mail-pg1-x52c.google.com [IPv6:2607:f8b0:4864:20::52c]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Q0T5m15pNz44cv for ; Mon, 17 Apr 2023 13:53:00 +0000 (UTC) (envelope-from david.robertsson@gmail.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20221208 header.b=VjaIvB+8; spf=pass (mx1.freebsd.org: domain of david.robertsson@gmail.com designates 2607:f8b0:4864:20::52c as permitted sender) smtp.mailfrom=david.robertsson@gmail.com; dmarc=pass (policy=none) header.from=gmail.com Received: by mail-pg1-x52c.google.com with SMTP id g70so346484pgc.9 for ; Mon, 17 Apr 2023 06:53:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1681739576; x=1684331576; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=r4wK2sOsqOCVWXAWjsa9+FHg8jfnmXAyRAflj7E/M/k=; b=VjaIvB+8zoPvckkSu3axR9z54eaLuZgsHGn7F0mPezHcb1u94oiG7h2e/kVBUcLXmL TpfVwjhhxrWVXzbjA76UujgHbxxXNGy1F3MDUXIFmlvZMVxi4yuPfTsAvQlS3LNxxYBs wG1kpNo/11notY3S3+OMbkiP5Q+voA6JoPrYDg/wRQ27A1jthLBEsCe+xk4SpkwqqO57 u0xqO8t071DWh48OZ+63qKwRkFPzWNOsafPZJskbpJ+i/4bECkorInIGvPEWO5J18Kaw GTUnFEZmL/hCzklrFkQYRmhwjJeN86qTINWxyTcoGYk8DA4yncoeuiWLQlxTuAVmRSvA 1mpA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1681739576; x=1684331576; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=r4wK2sOsqOCVWXAWjsa9+FHg8jfnmXAyRAflj7E/M/k=; b=S+X4+8Z0vFzB44Gahz5u0gPFXccI+Qi8h5K2CLAUrXLzOeVcOWT1JvjwDNeSTAv+C7 jyWi90p4wPThn7Sez4Il9u/OahD+XYFWVmLmRfYzsgTO+a7uF3KAGvaVW4FTsOn/0Xyv Z/5n9hjLv1zk1J9oR/tCpHv3baIy9XGtaeHYCsAAtjVX/9dhTHrHTmlByLcEc9oYrI1M 9+kHZC2qzuKJ2sGaYvMbStmcSLYWIgHaNIdgEcx83AJa0ubMW1QBn2/Nq9fKYhBJodl5 AeFo34W4JYdhsqK9RXeP1UBHTikSI9IGa9mRwUr1ci9rdVtqcAfTF2e5CpJ/xjKX4EJ3 dfUQ== X-Gm-Message-State: AAQBX9erO5N4S/B63EUnFF1bxKGYqCGq3gF2/t9OawD5A3xqEOiDdGY7 nEY0W0VDDJMF5DBE+/npi1A0crCeA81THMI9uMOg0yHk X-Google-Smtp-Source: AKy350Z+qkaB0thP53tH6CpIjpxcSy1FdCSAMkYVaOiXlV/H3X2xQWTObogEYQ2AyJhXSCi1k0gePdJJC5vkUk8fCcI= X-Received: by 2002:a65:670f:0:b0:513:90eb:a37c with SMTP id u15-20020a65670f000000b0051390eba37cmr3235060pgf.11.1681739576104; Mon, 17 Apr 2023 06:52:56 -0700 (PDT) List-Id: Technical discussions relating to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-hackers List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-hackers@freebsd.org MIME-Version: 1.0 From: David Robertsson Date: Mon, 17 Apr 2023 15:52:45 +0200 Message-ID: Subject: Current status of the openPOWERLINK idea? To: freebsd-hackers@freebsd.org Content-Type: multipart/alternative; boundary="0000000000000a706505f988826a" X-Spamd-Result: default: False [-2.99 / 15.00]; SUBJECT_ENDS_QUESTION(1.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.99)[-0.993]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20221208]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; TO_MATCH_ENVRCPT_ALL(0.00)[]; FROM_HAS_DN(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-hackers@freebsd.org]; RCVD_TLS_LAST(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::52c:from]; FREEMAIL_FROM(0.00)[gmail.com]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim]; MLMMJ_DEST(0.00)[freebsd-hackers@freebsd.org]; DKIM_TRACE(0.00)[gmail.com:+]; MID_RHS_MATCH_FROMTLD(0.00)[]; TO_DN_NONE(0.00)[]; ARC_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; MIME_TRACE(0.00)[0:+,1:+,2:~]; TAGGED_FROM(0.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; RCVD_COUNT_TWO(0.00)[2] X-Rspamd-Queue-Id: 4Q0T5m15pNz44cv X-Spamd-Bar: -- X-ThisMailContainsUnwantedMimeParts: N --0000000000000a706505f988826a Content-Type: text/plain; charset="UTF-8" Noticed openPowerlink was added to the ideas page, is there someone out there already working on this? Otherwise this would be something that is aligned with my personal interests to work on. Not sure what the best path forward is. The OpenPowerlink "stack" today has two options as for Linux (afaik). 1. Userspace daemon with the help of LibPcap. 2. kernel driver that unloads the driver from a network card and then uses it for communication with powerlink gear. I have been using OpenPowerlink myself since 2014 in a Linux environment, and I'm not so sure the option 2 is desired. To build the code, it assumes that you know what gear it is you want to communicate with. So from a list of gear that the user has "setup" you then import that list into openConfigurator to generate a mnobd.cdc and a xap.h file. This is then used to broadcast the binary to all the powerlink devices on the network. The xap.h file contains a struct describing the devices - for example in which order the digital input & output modules are connected to every brain module (control node). One idea I have; is to try to make a port of the userspace daemon or perhaps try to make a standalone lib that can be used in any project that aims to run a powerlink control / master node on FreeBSD. What do you all think? Best regards David --0000000000000a706505f988826a Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Noticed openPowerlink was added to the ideas page, is ther= e someone out there already working on this?

Otherwise this would be= something that is aligned with my personal interests to work on.

No= t sure what the best path forward is.

The OpenPowerlink "stack&= quot; today has two options as for Linux (afaik).

1. Userspace daemo= n with the help of LibPcap.
2. kernel driver that unloads the driver fro= m a network=C2=A0card and then uses it for communication with powerlink gea= r.

I have been using OpenPowerlink myself since 2014 in a Linux envi= ronment, and I'm not so sure the option 2 is desired.

To build t= he code, it assumes that you know what gear it is you want to communicate w= ith.
So from a list of gear that the user has "setup" you then= import that list into openConfigurator to generate a mnobd.cdc=C2=A0and a = xap.h file. This is then used to broadcast the binary to all the powerlink = devices on the network.=C2=A0The xap.h file contains a struct=C2=A0describi= ng the=C2=A0devices - for example in which order the digital input & ou= tput modules are connected to every brain module (control node).

One= idea I have; is to try to make a port of the userspace daemon or perhaps t= ry to make a standalone lib that can be used in any project that aims to ru= n a powerlink control / master node on FreeBSD.

What do you all thin= k?
Best regards
David


--0000000000000a706505f988826a-- From nobody Mon Apr 17 17:35:10 2023 X-Original-To: freebsd-hackers@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 4Q0Z2868fZz44y11 for ; Mon, 17 Apr 2023 17:35:12 +0000 (UTC) (envelope-from mjguzik@gmail.com) Received: from mail-oa1-x35.google.com (mail-oa1-x35.google.com [IPv6:2001:4860:4864:20::35]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Q0Z282yYvz46XM; Mon, 17 Apr 2023 17:35:12 +0000 (UTC) (envelope-from mjguzik@gmail.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20221208 header.b=L8SZ4rDB; spf=pass (mx1.freebsd.org: domain of mjguzik@gmail.com designates 2001:4860:4864:20::35 as permitted sender) smtp.mailfrom=mjguzik@gmail.com; dmarc=pass (policy=none) header.from=gmail.com Received: by mail-oa1-x35.google.com with SMTP id 586e51a60fabf-187e9f8c982so3993821fac.1; Mon, 17 Apr 2023 10:35:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1681752911; x=1684344911; h=cc:to:subject:message-id:date:from:references:in-reply-to :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=Nq2bIrEI9RlxvlNlXPgBIsvgRvGkjx/2EVTBtXvLLhs=; b=L8SZ4rDByGlF7N0DqRT4PXYz4BR4BJEvKb+juyhLMb4ASK6eqApDpz8lKx21BHBvY3 8T1TfJhhyfIWTBHJUVDz3ccC8FLIIFmEK9vNOtbhriPMkBEi16s91xj9Xz5Zs/awtZY3 ZyJJizAUn8zoQSVfdxAFtbVKeLkoZTJ1KM47S/kNm3sJy04RA1RAJXRyC/kpBxD/RnGZ IDV454m69GAMf7knxNmTkmD7neeBMwxNLO6jAASenxBKu4ESG1m2kpkob7nkh44SHXkf IVwv4/zGw3hpU7T0RVeDbqteHVYQHFanygmtI8+dCVYl5tnZdXfpDLyBI4seJbhvpCTD GI9A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1681752911; x=1684344911; h=cc:to:subject:message-id:date:from:references:in-reply-to :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=Nq2bIrEI9RlxvlNlXPgBIsvgRvGkjx/2EVTBtXvLLhs=; b=KJI+1ZZxtWBRw+q+7wF33pHq+DY2EHTcrObIfP9QAxL1WctxQiHySr1m8x5LaosDpj tkFY825FtcrvYRYjlyK7nPMMDFWwoRuRF17hCLJ4CH+yCeOiEen0lDT/DmVAaNg4R5tp 1CiVzBWzipZItkQgrG76cdYAbGS3puCuUcQNmrQAF3M7teK1MDz/OBLlCXhoniRj5YhC pBufCE2yPBF94QHVWfOo1AFj1AmjKkHConjZ+G4kOcEmyvOiIMfaW2vBFyw4WDlxvofR Mv6FJQ0tcYaOlc8/Dvy3G8cWfejg50+fddznjItKCcLz5WE5qBkU0tBYrIntBx4A6eY8 sOog== X-Gm-Message-State: AAQBX9cfeH2XLTuFX02N6uRhu87knv5BJusK7vBBBblKP9PwuYMqwhI5 31gzRfVaA1c0gyj2M78QlRDzu82srDjjRKIcQPfQBie7 X-Google-Smtp-Source: AKy350ZwNyo9QfL2s6HY0E/LEQ+rrtoFrxtTStOiHL1hRTnlWY2+0B8UJYAl4+75MTNS6/5zpYLMUf4Lz7/wKvKkVP4= X-Received: by 2002:a05:6870:46ab:b0:184:1a2c:83df with SMTP id a43-20020a05687046ab00b001841a2c83dfmr7104013oap.4.1681752910925; Mon, 17 Apr 2023 10:35:10 -0700 (PDT) List-Id: Technical discussions relating to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-hackers List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-hackers@freebsd.org MIME-Version: 1.0 Received: by 2002:a8a:46:0:b0:49c:b071:b1e3 with HTTP; Mon, 17 Apr 2023 10:35:10 -0700 (PDT) In-Reply-To: References: From: Mateusz Guzik Date: Mon, 17 Apr 2023 19:35:10 +0200 Message-ID: Subject: Re: Periodic rant about SCHED_ULE To: Mark Johnston Cc: freebsd-hackers@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Spamd-Result: default: False [-4.00 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-1.000]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; R_SPF_ALLOW(-0.20)[+ip6:2001:4860:4000::/36]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20221208]; MIME_GOOD(-0.10)[text/plain]; MLMMJ_DEST(0.00)[freebsd-hackers@freebsd.org]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; RCVD_IN_DNSWL_NONE(0.00)[2001:4860:4864:20::35:from]; ASN(0.00)[asn:15169, ipnet:2001:4860:4864::/48, country:US]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ARC_NA(0.00)[]; MID_RHS_MATCH_FROMTLD(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; TO_DN_SOME(0.00)[]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; FREEMAIL_FROM(0.00)[gmail.com]; RCVD_COUNT_THREE(0.00)[3]; TO_MATCH_ENVRCPT_ALL(0.00)[]; RCVD_TLS_LAST(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim] X-Rspamd-Queue-Id: 4Q0Z282yYvz46XM X-Spamd-Bar: --- X-ThisMailContainsUnwantedMimeParts: N Ops, this fell through the cracks, apologies for such a late reply. On 3/31/23, Mark Johnston wrote: > On Fri, Mar 31, 2023 at 08:41:41PM +0200, Mateusz Guzik wrote: >> On 3/30/23, Mark Johnston wrote: >> > On Thu, Mar 30, 2023 at 05:36:54PM +0200, Mateusz Guzik wrote: >> >> I looked into it a little more, below you can find summary and steps >> >> forward. >> >> >> >> First a general statement: while ULE does have performance bugs, it >> >> has better basis than 4BSD to make scheduling decisions. Most notably >> >> it understands CPU topology, at least for cases which don't involve >> >> big.LITTLE. For any non-freak case where 4BSD performs better, it is a >> >> bug in ULE if this is for any reason other than a tradeoff which can >> >> be tweaked to line them up. Or more to the point, there should not be >> >> any legitimate reason to use 4BSD these days and modulo the bugs >> >> below, you are probably losing on performance for doing so. >> >> >> >> Bugs reported in this thread by others and confirmed by me: >> >> 1. failure to load-balance when having n CPUs and n + 1 workers -- the >> >> excess one stays on one the same CPU thread continuously penalizing >> >> the same victim. as a result total real time to execute a finite >> >> computation is longer than in the case of 4BSD >> >> 2. unfairness of nice -n 20 threads vs threads going frequently off >> >> CPU (e.g., due to I/O) -- after using only a fraction of the slice the >> >> victim has to wait for the cpu hog to use up its entire slice, rinse >> >> and repeat. This extends a 7+ minute buildkernel to over 67 minutes, >> >> not an issue on 4BSD >> >> >> >> I did not put almost any effort into investigating no 1. There is code >> >> which is supposed to rebalance load across CPUs, someone(tm) will have >> >> to sit through it -- for all I know the fix is trivial. >> >> >> >> Fixing number 2 makes *another* bug more acute and it complicates the >> >> whole ordeal. >> >> >> >> Thus, bug reported by me: >> >> 3. interactivity scoring is bogus -- originally introduced to detect >> >> "interactive" behavior by equating being off CPU with waiting for user >> >> input. One part of the problem is that it puts *all* non-preempted off >> >> CPU time into one bag: a voluntary sleep. This includes suffering from >> >> lock contention in the kernel, lock contention in the program itself, >> > >> > Note that time spent off-CPU on a turnstile is not counted as sleeping >> > for the purpose of interactivity scoring, so this observation applies >> > only to sx, lockmgr and sleepable rm locks. That's not to say that >> > this >> > behaviour is correct, but it doesn't apply to some of the most >> > contended >> > locks unless I'm missing something. >> > >> >> page busy (massively contested for fork/exec), pipe_lock and even >> not-locks like waitpid(!) > > A program that spends most of its time blocked in waitpid, like a shell, > interactive or not, should indeed have a higher scheduling priority... > Maybe it should, but perhaps not at the expense of a more latency-sensitive program like a video player. The very notion that off cpu == interactive dates back to the 80s where it probably made sense, as the unix systems at the time were mostly just terminal-only and the shell would indeed fit here very nicely. >> >> file I/O and so on, none of which has bearing on how interactive or >> >> not the program might happen to be. A bigger part of the problem is >> >> that at least today, the graphical programs don't even act this way to >> >> begin with -- they stay on CPU *a lot*. >> > >> > I think this statement deserves more nuance. I was on a video call >> > just >> > now and firefox was consuming about the equivalent of 20-30% of a CPU >> > across all threads. What kind of graphical programs are you talking >> > about specifically? >> > >> >> you don't consider 20-30% a lot? > > I would expect a program consuming 20-30% of a CPU to be prioritized > higher than a CPU hog. And in my experience, running builds while on a > call doesn't hurt anything (usually). Again, there is room for > improvement, I don't claim the scheduler is perfect. > As noted one of the performance bugs is that the scheduler *unintentionally* penalizes threads which go off cpu a lot for short periods. If scheduler keeps them in the batch range and there is a hog in the area, they are using getting disproportionately less cpu. kernel build is one example I noted -- several times in increase in total real time vs cpu hogs, while struggling to get any time. For all I know this bug is why it works fine for you. >> >> I asked people to provide me with the output of: dtrace -n >> >> 'sched:::on-cpu { @[execname] = lquantize(curthread->td_priority, 0, >> >> 224, 1); }' from their laptops/desktops. >> >> >> >> One finding is that most people (at least those who reported) use >> >> firefox. >> >> >> >> Another finding is that the browser is above the threshold which would >> >> be considered "interactive" for vast majority of the time in all >> >> reported cases. >> > >> > That is not true of the output that I sent. There, most of the firefox >> > thread samples are in the interactive range [88-135]. Some show an >> > even >> > higher priority, maybe due to priority propagation. >> > >> >> That's not the interactive range. 88 is PRI_MIN_BATCH > > 88 is PRI_MIN_TIMESHARE (on main, stable/13 ranges are different I > think). PRI_MIN_BATCH is PRI_MIN_TIMESHARE + PRI_INTERACT_RANGE = 88 + > 48 = 136. Everything in [88-135] goes into the realtime queue. > You are right, I misread the code. static_boost seting prio to 72 solidified my misread. Interestingly this does not change the crux of the matter -- that not interactive processes cluster in terms of priorities with one which are interactive. You can see it in your own report. >> >> I booted a 2 thread vm with xfce and decided to click around. Spawned >> >> firefox, opened a file manager (Thunar) and from there I opened a >> >> movie to play with mpv. As root I spawned make -j 2 buildkernel. it >> >> was not particularly good :) >> >> >> >> I found that mpv spawns a bunch of threads, most notably 2 distinct >> >> threads for audio and video output. The one for video got a priority >> >> of 175, while the rest had either 88 or 89 -- the lowest for >> >> timesharing not considered interactive [note lower is considered >> >> better]. >> > >> > Presumably all of the video decoding was done in software, since you're >> > running in a VM? On my desktop, mpv does not consume much CPU and is >> > entirely interactive. Your test suggests that you expect ULE to >> > prioritize a CPU hog, which doesn't seem realistic absent some >> > scheduling hints from the user or the program itself. Problem 2 is the >> > opposite problem: timesharing CPU hogs are allowed to starve other >> > timesharing threads. >> > >> >> Now that I pointed out anything >= 88 is *NOT* interactive, are you >> sure your mpv was considered interactive anyway? > > Yes. > See above :) >> I don't expect ULE to prioritize CPU hogs. I'm pointing out how a hog >> which was a part of an interactive program got shafted, further >> showing how the method based on counting off cpu time does not work. > > You're saying that interactivity scoring should take into account > overall process behaviour instead of just thread behviour? Sure, that > could be reasonable. > That's part of it, yes. >> >> At the same time the file manager who was left in the background kept >> >> doing evil syscall usage, which as a result bouncing between a regular >> >> timesharing priority and one which made it "interactive", even though >> >> the program was not touched for minutes. >> >> >> >> Or to put it differently, the scheduler failed to recognize that mpv >> >> is the program to prioritize, all while thinking the background time >> >> waster is the thing to look after (so to speak). >> >> >> >> This brings us to fixing problem 2: currently, due to the existence of >> >> said problem, the interactivity scoring woes are less acute -- the >> >> venerable make -j example is struggling to get CPU time, as a result >> >> messing with real interactive programs to a lesser extent. If that >> >> gets fixed, we are in a different boat altogether. >> >> >> >> I don't see a clean solution. >> >> >> >> Right now I'm toying with the idea of either: >> >> 1. having programs explicitly tell the kernel they are interactive >> > >> > I don't see how this can work. It's not just traditional "interactive" >> > programs that benefit from this scoring, it applies also to network >> > servers and other programs which spend most of their time sleeping but >> > want to handle requests with low latency. >> > >> > Such an interface would also let any program request soft realtime >> > scheduling without giving up the ability to monopolize CPU time, which >> > goes against ULE's fairness goals. >> > >> >> Clearly it would be gated with some permission, so only available on a >> desktop for example. >> >> Then again see my response else in the thread: x server could be >> patched to mark threads. > > To do what? > To tell the kernel they are interactive clients so that it does not have to speculate. Same with pulseaudio and whatever direct /dev/dsp consumer. >> And it does not go against any fairness goals -- it very much can be >> achieved, but one has information who can be put off cpu for a longer >> time without introducing issues. >> >> >> 2. adding a scheduler hook to /dev/dsp -- the observation is that if a >> >> program is producing sound it probably should get some cpu time in a >> >> timely manner. this would cover audio/video players and web browsers, >> > >> > On my system at least firefox doesn't open /dev/dsp, it sends audio >> > streams to pulseaudio. >> > >> >> I think I noted elsewhere in the thread that pulseaudio may need the >> same treatment as the x server. >> >> >> but would not cover other programs (say a pdf reader). it may be it is >> >> good enough though >> > >> > I think some more thorough analysis, using tools like schedgraph or >> > KUtrace[1], is needed to characterize the problems you are reporting >> > with interactivity scoring. It's also not clear how any of this would >> > address the problem that started this thread, wherein two competing >> > timesharing (i.e., non-interactive) workloads get uneven amounts of CPU >> > time. >> > >> >> I explicitly stated I have not looked into this bit. >> >> > There is absolutely room for improvement in ULE's scheduling decisions. >> > It seems to be common practice to tune various ULE parameters to get >> > better interactive performance, but in general I see no analysis >> > explaining /why/ exactly they help and what goes wrong with the default >> > parameter values in specific workloads. schedgraph is a very useful >> > tool for this sort of thing. >> > >> >> I tried schedgraph in the past to look at buildkernel and found it >> does not cope with the amount of threads, at least on my laptop. >> >> > Such tools also required to rule out bugs in ULE itself, when looking >> > at >> > abnormal scheduling behaviour. Last year some scheduler races[2] were >> > fixed that apparently hurt system performance on EPYC quite a bit. I >> > was told privately that applying those patches to 13.1 improved IPSec >> > throughput by ~25% on EPYC, and I wouldn't be surprised if there are >> > more improvements to be had which don't involve modifying core >> > heuristics of the scheduler. Either way this requires deeper analysis >> > of ULE's micro-level behaviour; I don't think "interactivity scoring is >> > bogus" is a useful starting point. >> > >> >> I provided explicit examples how it marked a background thread as >> interactive, while the real hard worker (if you will) as not >> interactive, because said worker was not acting the way ULE expects. >> >> A bandaid for the time being will stop shafting processes giving up >> their time slice early in the batch queue, along with some fairness >> for the rest who does not (like firefox). I'll hack it up for testing. >> >> -- >> Mateusz Guzik > -- Mateusz Guzik From nobody Tue Apr 18 07:25:47 2023 X-Original-To: freebsd-hackers@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 4Q0wZ140z3z45ttW for ; Tue, 18 Apr 2023 07:30:33 +0000 (UTC) (envelope-from fernando.apesteguia@gmail.com) Received: from mail-lj1-x231.google.com (mail-lj1-x231.google.com [IPv6:2a00:1450:4864:20::231]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Q0wZ01M7gz3wcr; Tue, 18 Apr 2023 07:30:32 +0000 (UTC) (envelope-from fernando.apesteguia@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-lj1-x231.google.com with SMTP id 38308e7fff4ca-2a8b3ecf59fso18257691fa.0; Tue, 18 Apr 2023 00:30:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1681803030; x=1684395030; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=TzFq95rTeNbNXfwnenlgx43+6cyjHBiD9Ek0/8yVYHQ=; b=p44gcZDVsSaZ9g8RJ66QPebERo7QWD53YJofjepFkWpNuajvpHTOA12cFOizY8oWsb vuSsPnZxNFPYtaTCpe0IspWOEzc5eVdwio4Gjp9l+2CYvZAadVpE0bKfkrQkKUyjIecW wx9Kzi8VLUeQfqV8GI+kPJxV9Mr/lvI/2KLLsqN5ZSS0vpuF9BQM0dJ0D6r7ucPs3O+C nJ4vtP0coYFNfzYCW+yz/kFC5/kkJEOAL3fo5xh7322QzfKoZzrbTQ4qyGTdFFZRDXcO awwIcxu/Xz2rsRjBRy++qp/2TqMmIZp+5r8Kpiphy5gb/W0niCm9HJq53RsL2Vhfxm+/ Qgaw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1681803030; x=1684395030; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=TzFq95rTeNbNXfwnenlgx43+6cyjHBiD9Ek0/8yVYHQ=; b=VDRu0SPAh8Vc3+nCfGyT4eEIR1WozRhEW37dvy47AJgGAFBxESv6cVgS55BFRSlhYg jbgkqD0u+p+zxEiOsN7KYy6++ypewQDxPrvL60tThBMLRxJ9i05vIvDsYAVZKxv2qpkP oNhcxIsXDN3f4YCWkpxhUsNphfE/BXj4CEg4JIbdAjFQ9gr8hyF4AdTJPnS6Bbhy+ev7 vbpP/uZ3l6nJsmK37alFYwXIAd5sDhscaouELVDL/d3fCtrMFQnHsytW0Bp8hQGeaolo Au9PzH1raKOV7Nr4YIbnDABat/xmnZBgkZczJrpp33x7Nn4n/um0I3DuDRqEzShl0rq4 95BQ== X-Gm-Message-State: AAQBX9esNUrN2j46r0mpXRVWgoRcioeue9KW8gxCm/Zu6dotLwTb+0ek rRoAy3PV0HcJRgv6laYT+wAu6YEiRdnAt3DuIjEnaTwb X-Google-Smtp-Source: AKy350auzd8lDupW7KjmuKnYEWfU1+6zhdwzGcT0eAt0ECmmYqbz7T+TwvOtg8LV9EuXW1n9sPJWbF2H/FjD0NStitY= X-Received: by 2002:a19:c20d:0:b0:4ed:b22a:da25 with SMTP id l13-20020a19c20d000000b004edb22ada25mr2884902lfc.11.1681803029747; Tue, 18 Apr 2023 00:30:29 -0700 (PDT) List-Id: Technical discussions relating to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-hackers List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-hackers@freebsd.org MIME-Version: 1.0 References: In-Reply-To: From: =?UTF-8?Q?Fernando_Apestegu=C3=ADa?= Date: Tue, 18 Apr 2023 09:25:47 +0200 Message-ID: Subject: Re: Periodic rant about SCHED_ULE To: Mateusz Guzik Cc: Mark Johnston , freebsd-hackers@freebsd.org Content-Type: multipart/alternative; boundary="0000000000002b9b9505f99748f9" X-Rspamd-Queue-Id: 4Q0wZ01M7gz3wcr X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; TAGGED_FROM(0.00)[]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N --0000000000002b9b9505f99748f9 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Mon, Apr 17, 2023 at 7:35=E2=80=AFPM Mateusz Guzik w= rote: > Ops, this fell through the cracks, apologies for such a late reply. > > On 3/31/23, Mark Johnston wrote: > > On Fri, Mar 31, 2023 at 08:41:41PM +0200, Mateusz Guzik wrote: > >> On 3/30/23, Mark Johnston wrote: > >> > On Thu, Mar 30, 2023 at 05:36:54PM +0200, Mateusz Guzik wrote: > >> >> I looked into it a little more, below you can find summary and step= s > >> >> forward. > >> >> > >> >> First a general statement: while ULE does have performance bugs, it > >> >> has better basis than 4BSD to make scheduling decisions. Most notab= ly > >> >> it understands CPU topology, at least for cases which don't involve > >> >> big.LITTLE. For any non-freak case where 4BSD performs better, it i= s > a > >> >> bug in ULE if this is for any reason other than a tradeoff which ca= n > >> >> be tweaked to line them up. Or more to the point, there should not = be > >> >> any legitimate reason to use 4BSD these days and modulo the bugs > >> >> below, you are probably losing on performance for doing so. > >> >> > >> >> Bugs reported in this thread by others and confirmed by me: > >> >> 1. failure to load-balance when having n CPUs and n + 1 workers -- > the > >> >> excess one stays on one the same CPU thread continuously penalizing > >> >> the same victim. as a result total real time to execute a finite > >> >> computation is longer than in the case of 4BSD > >> >> 2. unfairness of nice -n 20 threads vs threads going frequently off > >> >> CPU (e.g., due to I/O) -- after using only a fraction of the slice > the > >> >> victim has to wait for the cpu hog to use up its entire slice, rins= e > >> >> and repeat. This extends a 7+ minute buildkernel to over 67 minutes= , > >> >> not an issue on 4BSD > >> >> > >> >> I did not put almost any effort into investigating no 1. There is > code > >> >> which is supposed to rebalance load across CPUs, someone(tm) will > have > >> >> to sit through it -- for all I know the fix is trivial. > >> >> > >> >> Fixing number 2 makes *another* bug more acute and it complicates t= he > >> >> whole ordeal. > >> >> > >> >> Thus, bug reported by me: > >> >> 3. interactivity scoring is bogus -- originally introduced to detec= t > >> >> "interactive" behavior by equating being off CPU with waiting for > user > >> >> input. One part of the problem is that it puts *all* non-preempted > off > >> >> CPU time into one bag: a voluntary sleep. This includes suffering > from > >> >> lock contention in the kernel, lock contention in the program itsel= f, > >> > > >> > Note that time spent off-CPU on a turnstile is not counted as sleepi= ng > >> > for the purpose of interactivity scoring, so this observation applie= s > >> > only to sx, lockmgr and sleepable rm locks. That's not to say that > >> > this > >> > behaviour is correct, but it doesn't apply to some of the most > >> > contended > >> > locks unless I'm missing something. > >> > > >> > >> page busy (massively contested for fork/exec), pipe_lock and even > >> not-locks like waitpid(!) > > > > A program that spends most of its time blocked in waitpid, like a shell= , > > interactive or not, should indeed have a higher scheduling priority... > > > > Maybe it should, but perhaps not at the expense of a more > latency-sensitive program like a video player. > > The very notion that off cpu =3D=3D interactive dates back to the 80s > where it probably made sense, as the unix systems at the time were > mostly just terminal-only and the shell would indeed fit here very > nicely. > > >> >> file I/O and so on, none of which has bearing on how interactive or > >> >> not the program might happen to be. A bigger part of the problem is > >> >> that at least today, the graphical programs don't even act this way > to > >> >> begin with -- they stay on CPU *a lot*. > >> > > >> > I think this statement deserves more nuance. I was on a video call > >> > just > >> > now and firefox was consuming about the equivalent of 20-30% of a CP= U > >> > across all threads. What kind of graphical programs are you talking > >> > about specifically? > >> > > >> > >> you don't consider 20-30% a lot? > > > > I would expect a program consuming 20-30% of a CPU to be prioritized > > higher than a CPU hog. And in my experience, running builds while on a > > call doesn't hurt anything (usually). Again, there is room for > > improvement, I don't claim the scheduler is perfect. > > > > As noted one of the performance bugs is that the scheduler > *unintentionally* penalizes threads which go off cpu a lot for short > periods. If scheduler keeps them in the batch range and there is a hog > in the area, they are using getting disproportionately less cpu. > kernel build is one example I noted -- several times in increase in > total real time vs cpu hogs, while struggling to get any time. For all > I know this bug is why it works fine for you. > > >> >> I asked people to provide me with the output of: dtrace -n > >> >> 'sched:::on-cpu { @[execname] =3D lquantize(curthread->td_priority,= 0, > >> >> 224, 1); }' from their laptops/desktops. > >> >> > >> >> One finding is that most people (at least those who reported) use > >> >> firefox. > >> >> > >> >> Another finding is that the browser is above the threshold which > would > >> >> be considered "interactive" for vast majority of the time in all > >> >> reported cases. > >> > > >> > That is not true of the output that I sent. There, most of the > firefox > >> > thread samples are in the interactive range [88-135]. Some show an > >> > even > >> > higher priority, maybe due to priority propagation. > >> > > >> > >> That's not the interactive range. 88 is PRI_MIN_BATCH > > > > 88 is PRI_MIN_TIMESHARE (on main, stable/13 ranges are different I > > think). PRI_MIN_BATCH is PRI_MIN_TIMESHARE + PRI_INTERACT_RANGE =3D 88= + > > 48 =3D 136. Everything in [88-135] goes into the realtime queue. > > > > You are right, I misread the code. static_boost seting prio to 72 > solidified my misread. > > Interestingly this does not change the crux of the matter -- that not > interactive processes cluster in terms of priorities with one which > are interactive. You can see it in your own report. > > >> >> I booted a 2 thread vm with xfce and decided to click around. Spawn= ed > >> >> firefox, opened a file manager (Thunar) and from there I opened a > >> >> movie to play with mpv. As root I spawned make -j 2 buildkernel. it > >> >> was not particularly good :) > >> >> > >> >> I found that mpv spawns a bunch of threads, most notably 2 distinct > >> >> threads for audio and video output. The one for video got a priorit= y > >> >> of 175, while the rest had either 88 or 89 -- the lowest for > >> >> timesharing not considered interactive [note lower is considered > >> >> better]. > >> > > >> > Presumably all of the video decoding was done in software, since > you're > >> > running in a VM? On my desktop, mpv does not consume much CPU and i= s > >> > entirely interactive. Your test suggests that you expect ULE to > >> > prioritize a CPU hog, which doesn't seem realistic absent some > >> > scheduling hints from the user or the program itself. Problem 2 is > the > >> > opposite problem: timesharing CPU hogs are allowed to starve other > >> > timesharing threads. > >> > > >> > >> Now that I pointed out anything >=3D 88 is *NOT* interactive, are you > >> sure your mpv was considered interactive anyway? > > > > Yes. > > > > See above :) > > >> I don't expect ULE to prioritize CPU hogs. I'm pointing out how a hog > >> which was a part of an interactive program got shafted, further > >> showing how the method based on counting off cpu time does not work. > > > > You're saying that interactivity scoring should take into account > > overall process behaviour instead of just thread behviour? Sure, that > > could be reasonable. > > > > That's part of it, yes. > > >> >> At the same time the file manager who was left in the background ke= pt > >> >> doing evil syscall usage, which as a result bouncing between a > regular > >> >> timesharing priority and one which made it "interactive", even thou= gh > >> >> the program was not touched for minutes. > >> >> > >> >> Or to put it differently, the scheduler failed to recognize that mp= v > >> >> is the program to prioritize, all while thinking the background tim= e > >> >> waster is the thing to look after (so to speak). > >> >> > >> >> This brings us to fixing problem 2: currently, due to the existence > of > >> >> said problem, the interactivity scoring woes are less acute -- the > >> >> venerable make -j example is struggling to get CPU time, as a resul= t > >> >> messing with real interactive programs to a lesser extent. If that > >> >> gets fixed, we are in a different boat altogether. > >> >> > >> >> I don't see a clean solution. > >> >> > >> >> Right now I'm toying with the idea of either: > >> >> 1. having programs explicitly tell the kernel they are interactive > >> > > >> > I don't see how this can work. It's not just traditional > "interactive" > >> > programs that benefit from this scoring, it applies also to network > >> > servers and other programs which spend most of their time sleeping b= ut > >> > want to handle requests with low latency. > >> > > >> > Such an interface would also let any program request soft realtime > >> > scheduling without giving up the ability to monopolize CPU time, whi= ch > >> > goes against ULE's fairness goals. > >> > > >> > >> Clearly it would be gated with some permission, so only available on a > >> desktop for example. > >> > >> Then again see my response else in the thread: x server could be > >> patched to mark threads. > > > > To do what? > > > > To tell the kernel they are interactive clients so that it does not > have to speculate. > > Same with pulseaudio and whatever direct /dev/dsp consumer. > I'm a bit concerned about the scalability of this approach. Wouldn't that be like *a lot* of patching? Somehow it feels to me that the scheduler should be the one correctly discerning if a process is interactive or not instead of the client application defining itself as such. If the scheduler does the job, then it should be able to update the "interactivity status" of a client if the client behavior changes. Otherwise I suppose that change in behavior should be implemented in the patch itself which might not be easy to do (or could introduce poor performance if done improperly). I'm thinking of graphical applications that might be considered interactive but that at some point consume a lot of cpu like shotcut or openshot, or probably these days even web browsers. Also, since the scheduler is such a critical piece of software, I agree with Jeff Roberson that a bigger test suite, including regression tests, are necessary to ensure nothing breaks and we don't trade some use cases for others. P.S: This is a really informative thread. Thanks for working on this! > > >> And it does not go against any fairness goals -- it very much can be > >> achieved, but one has information who can be put off cpu for a longer > >> time without introducing issues. > >> > >> >> 2. adding a scheduler hook to /dev/dsp -- the observation is that i= f > a > >> >> program is producing sound it probably should get some cpu time in = a > >> >> timely manner. this would cover audio/video players and web browser= s, > >> > > >> > On my system at least firefox doesn't open /dev/dsp, it sends audio > >> > streams to pulseaudio. > >> > > >> > >> I think I noted elsewhere in the thread that pulseaudio may need the > >> same treatment as the x server. > >> > >> >> but would not cover other programs (say a pdf reader). it may be it > is > >> >> good enough though > >> > > >> > I think some more thorough analysis, using tools like schedgraph or > >> > KUtrace[1], is needed to characterize the problems you are reporting > >> > with interactivity scoring. It's also not clear how any of this wou= ld > >> > address the problem that started this thread, wherein two competing > >> > timesharing (i.e., non-interactive) workloads get uneven amounts of > CPU > >> > time. > >> > > >> > >> I explicitly stated I have not looked into this bit. > >> > >> > There is absolutely room for improvement in ULE's scheduling > decisions. > >> > It seems to be common practice to tune various ULE parameters to get > >> > better interactive performance, but in general I see no analysis > >> > explaining /why/ exactly they help and what goes wrong with the > default > >> > parameter values in specific workloads. schedgraph is a very useful > >> > tool for this sort of thing. > >> > > >> > >> I tried schedgraph in the past to look at buildkernel and found it > >> does not cope with the amount of threads, at least on my laptop. > >> > >> > Such tools also required to rule out bugs in ULE itself, when lookin= g > >> > at > >> > abnormal scheduling behaviour. Last year some scheduler races[2] we= re > >> > fixed that apparently hurt system performance on EPYC quite a bit. = I > >> > was told privately that applying those patches to 13.1 improved IPSe= c > >> > throughput by ~25% on EPYC, and I wouldn't be surprised if there are > >> > more improvements to be had which don't involve modifying core > >> > heuristics of the scheduler. Either way this requires deeper analys= is > >> > of ULE's micro-level behaviour; I don't think "interactivity scoring > is > >> > bogus" is a useful starting point. > >> > > >> > >> I provided explicit examples how it marked a background thread as > >> interactive, while the real hard worker (if you will) as not > >> interactive, because said worker was not acting the way ULE expects. > >> > >> A bandaid for the time being will stop shafting processes giving up > >> their time slice early in the batch queue, along with some fairness > >> for the rest who does not (like firefox). I'll hack it up for testing. > >> > >> -- > >> Mateusz Guzik > > > > > -- > Mateusz Guzik > > --0000000000002b9b9505f99748f9 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


=
On Mon, Apr 17, 2023 at 7:35=E2=80=AF= PM Mateusz Guzik <mjguzik@gmail.com> wrote:
Ops, this fell through the cracks, apologies for such a l= ate reply.

On 3/31/23, Mark Johnston <markj@freebsd.org> wrote:
> On Fri, Mar 31, 2023 at 08:41:41PM +0200, Mateusz Guzik wrote:
>> On 3/30/23, Mark Johnston <markj@freebsd.org> wrote:
>> > On Thu, Mar 30, 2023 at 05:36:54PM +0200, Mateusz Guzik wrote= :
>> >> I looked into it a little more, below you can find summar= y and steps
>> >> forward.
>> >>
>> >> First a general statement: while ULE does have performanc= e bugs, it
>> >> has better basis than 4BSD to make scheduling decisions. = Most notably
>> >> it understands CPU topology, at least for cases which don= 't involve
>> >> big.LITTLE. For any non-freak case where 4BSD performs be= tter, it is a
>> >> bug in ULE if this is for any reason other than a tradeof= f which can
>> >> be tweaked to line them up. Or more to the point, there s= hould not be
>> >> any legitimate reason to use 4BSD these days and modulo t= he bugs
>> >> below, you are probably losing on performance for doing s= o.
>> >>
>> >> Bugs reported in this thread by others and confirmed by m= e:
>> >> 1. failure to load-balance when having n CPUs and n + 1 w= orkers -- the
>> >> excess one stays on one the same CPU thread continuously = penalizing
>> >> the same victim. as a result total real time to execute a= finite
>> >> computation is longer than in the case of 4BSD
>> >> 2. unfairness of nice -n 20 threads vs threads going freq= uently off
>> >> CPU (e.g., due to I/O) -- after using only a fraction of = the slice the
>> >> victim has to wait for the cpu hog to use up its entire s= lice, rinse
>> >> and repeat. This extends a 7+ minute buildkernel to over = 67 minutes,
>> >> not an issue on 4BSD
>> >>
>> >> I did not put almost any effort into investigating no 1. = There is code
>> >> which is supposed to rebalance load across CPUs, someone(= tm) will have
>> >> to sit through it -- for all I know the fix is trivial. >> >>
>> >> Fixing number 2 makes *another* bug more acute and it com= plicates the
>> >> whole ordeal.
>> >>
>> >> Thus, bug reported by me:
>> >> 3. interactivity scoring is bogus -- originally introduce= d to detect
>> >> "interactive" behavior by equating being off CP= U with waiting for user
>> >> input. One part of the problem is that it puts *all* non-= preempted off
>> >> CPU time into one bag: a voluntary sleep. This includes s= uffering from
>> >> lock contention in the kernel, lock contention in the pro= gram itself,
>> >
>> > Note that time spent off-CPU on a turnstile is not counted as= sleeping
>> > for the purpose of interactivity scoring, so this observation= applies
>> > only to sx, lockmgr and sleepable rm locks.=C2=A0 That's = not to say that
>> > this
>> > behaviour is correct, but it doesn't apply to some of the= most
>> > contended
>> > locks unless I'm missing something.
>> >
>>
>> page busy (massively contested for fork/exec), pipe_lock and even<= br> >> not-locks like waitpid(!)
>
> A program that spends most of its time blocked in waitpid, like a shel= l,
> interactive or not, should indeed have a higher scheduling priority...=
>

Maybe it should, but perhaps not at the expense of a more
latency-sensitive program like a video player.

The very notion that off cpu =3D=3D interactive dates back to the 80s
where it probably made sense, as the unix systems at the time were
mostly just terminal-only and the shell would indeed fit here very
nicely.

>> >> file I/O and so on, none of which has bearing on how inte= ractive or
>> >> not the program might happen to be. A bigger part of the = problem is
>> >> that at least today, the graphical programs don't eve= n act this way to
>> >> begin with -- they stay on CPU *a lot*.
>> >
>> > I think this statement deserves more nuance.=C2=A0 I was on a= video call
>> > just
>> > now and firefox was consuming about the equivalent of 20-30% = of a CPU
>> > across all threads.=C2=A0 What kind of graphical programs are= you talking
>> > about specifically?
>> >
>>
>> you don't consider 20-30% a lot?
>
> I would expect a program consuming 20-30% of a CPU to be prioritized > higher than a CPU hog.=C2=A0 And in my experience, running builds whil= e on a
> call doesn't hurt anything (usually).=C2=A0 Again, there is room f= or
> improvement, I don't claim the scheduler is perfect.
>

As noted one of the performance bugs is that the scheduler
*unintentionally* penalizes threads which go off cpu a lot for short
periods. If scheduler keeps them in the batch range and there is a hog
in the area, they are using getting disproportionately less cpu.
kernel build is one example I noted -- several times in increase in
total real time vs cpu hogs, while struggling to get any time. For all
I know this bug is why it works fine for you.

>> >> I asked people to provide me with the output of: dtrace -= n
>> >> 'sched:::on-cpu { @[execname] =3D lquantize(curthread= ->td_priority, 0,
>> >> 224, 1); }' from their laptops/desktops.
>> >>
>> >> One finding is that most people (at least those who repor= ted) use
>> >> firefox.
>> >>
>> >> Another finding is that the browser is above the threshol= d which would
>> >> be considered "interactive" for vast majority o= f the time in all
>> >> reported cases.
>> >
>> > That is not true of the output that I sent.=C2=A0 There, most= of the firefox
>> > thread samples are in the interactive range [88-135].=C2=A0 S= ome show an
>> > even
>> > higher priority, maybe due to priority propagation.
>> >
>>
>> That's not the interactive range. 88 is PRI_MIN_BATCH
>
> 88 is PRI_MIN_TIMESHARE (on main, stable/13 ranges are different I
> think).=C2=A0 PRI_MIN_BATCH is PRI_MIN_TIMESHARE + PRI_INTERACT_RANGE = =3D 88 +
> 48 =3D 136.=C2=A0 Everything in [88-135] goes into the realtime queue.=
>

You are right, I misread the code. static_boost seting prio to 72
solidified my misread.

Interestingly this does not change the crux of the matter -- that not
interactive processes cluster in terms of priorities with one which
are interactive. You can see it in your own report.

>> >> I booted a 2 thread vm with xfce and decided to click aro= und. Spawned
>> >> firefox, opened a file manager (Thunar) and from there I = opened a
>> >> movie to play with mpv. As root I spawned make -j 2 build= kernel. it
>> >> was not particularly good :)
>> >>
>> >> I found that mpv spawns a bunch of threads, most notably = 2 distinct
>> >> threads for audio and video output. The one for video got= a priority
>> >> of 175, while the rest had either 88 or 89 -- the lowest = for
>> >> timesharing not considered interactive [note lower is con= sidered
>> >> better].
>> >
>> > Presumably all of the video decoding was done in software, si= nce you're
>> > running in a VM?=C2=A0 On my desktop, mpv does not consume mu= ch CPU and is
>> > entirely interactive.=C2=A0 Your test suggests that you expec= t ULE to
>> > prioritize a CPU hog, which doesn't seem realistic absent= some
>> > scheduling hints from the user or the program itself.=C2=A0 P= roblem 2 is the
>> > opposite problem: timesharing CPU hogs are allowed to starve = other
>> > timesharing threads.
>> >
>>
>> Now that I pointed out anything >=3D 88 is *NOT* interactive, a= re you
>> sure your mpv was considered interactive anyway?
>
> Yes.
>

See above :)

>> I don't expect ULE to prioritize CPU hogs. I'm pointing ou= t how a hog
>> which was a part of an interactive program got shafted, further >> showing how the method based on counting off cpu time does not wor= k.
>
> You're saying that interactivity scoring should take into account<= br> > overall process behaviour instead of just thread behviour?=C2=A0 Sure,= that
> could be reasonable.
>

That's part of it, yes.

>> >> At the same time the file manager who was left in the bac= kground kept
>> >> doing evil syscall usage, which as a result bouncing betw= een a regular
>> >> timesharing priority and one which made it "interact= ive", even though
>> >> the program was not touched for minutes.
>> >>
>> >> Or to put it differently, the scheduler failed to recogni= ze that mpv
>> >> is the program to prioritize, all while thinking the back= ground time
>> >> waster is the thing to look after (so to speak).
>> >>
>> >> This brings us to fixing problem 2: currently, due to the= existence of
>> >> said problem, the interactivity scoring woes are less acu= te -- the
>> >> venerable make -j example is struggling to get CPU time, = as a result
>> >> messing with real interactive programs to a lesser extent= . If that
>> >> gets fixed, we are in a different boat altogether.
>> >>
>> >> I don't see a clean solution.
>> >>
>> >> Right now I'm toying with the idea of either:
>> >> 1. having programs explicitly tell the kernel they are in= teractive
>> >
>> > I don't see how this can work.=C2=A0 It's not just tr= aditional "interactive"
>> > programs that benefit from this scoring, it applies also to n= etwork
>> > servers and other programs which spend most of their time sle= eping but
>> > want to handle requests with low latency.
>> >
>> > Such an interface would also let any program request soft rea= ltime
>> > scheduling without giving up the ability to monopolize CPU ti= me, which
>> > goes against ULE's fairness goals.
>> >
>>
>> Clearly it would be gated with some permission, so only available = on a
>> desktop for example.
>>
>> Then again see my response else in the thread: x server could be >> patched to mark threads.
>
> To do what?
>

To tell the kernel they are interactive clients so that it does not
have to speculate.

Same with pulseaudio and whatever direct /dev/dsp consumer.

I'm a bit concerned about the scalability of this = approach. Wouldn't that be like *a lot* of patching?

Somehow it feels to me that the scheduler should be the one correctl= y discerning if a process is interactive or not instead of the client appli= cation defining itself as such.
If the scheduler does the job, th= en it should be able to update the "interactivity status" of a cl= ient if the client behavior changes.
Otherwise I suppose that cha= nge in behavior should be implemented in the patch itself which might not b= e easy to do (or could introduce poor performance if done improperly).
I'm thinking of graphical applications that might be considered i= nteractive but that at some point consume a lot of cpu like shotcut or open= shot, or probably these days even web browsers.

Also, since the scheduler is such a critical piece of software, I agree w= ith Jeff Roberson that a bigger test suite, including regression tests, are= necessary to ensure nothing breaks and we don't trade some use cases f= or others.

P.S: This is a really informative t= hread. Thanks for working on this!
=C2=A0

>> And it does not go against any fairness goals -- it very much can = be
>> achieved, but one has information who can be put off cpu for a lon= ger
>> time without introducing issues.
>>
>> >> 2. adding a scheduler hook to /dev/dsp -- the observation= is that if a
>> >> program is producing sound it probably should get some cp= u time in a
>> >> timely manner. this would cover audio/video players and w= eb browsers,
>> >
>> > On my system at least firefox doesn't open /dev/dsp, it s= ends audio
>> > streams to pulseaudio.
>> >
>>
>> I think I noted elsewhere in the thread that pulseaudio may need t= he
>> same treatment as the x server.
>>
>> >> but would not cover other programs (say a pdf reader). it= may be it is
>> >> good enough though
>> >
>> > I think some more thorough analysis, using tools like schedgr= aph or
>> > KUtrace[1], is needed to characterize the problems you are re= porting
>> > with interactivity scoring.=C2=A0 It's also not clear how= any of this would
>> > address the problem that started this thread, wherein two com= peting
>> > timesharing (i.e., non-interactive) workloads get uneven amou= nts of CPU
>> > time.
>> >
>>
>> I explicitly stated I have not looked into this bit.
>>
>> > There is absolutely room for improvement in ULE's schedul= ing decisions.
>> > It seems to be common practice to tune various ULE parameters= to get
>> > better interactive performance, but in general I see no analy= sis
>> > explaining /why/ exactly they help and what goes wrong with t= he default
>> > parameter values in specific workloads.=C2=A0 schedgraph is a= very useful
>> > tool for this sort of thing.
>> >
>>
>> I tried schedgraph in the past to look at buildkernel and found it=
>> does not cope with the amount of threads, at least on my laptop. >>
>> > Such tools also required to rule out bugs in ULE itself, when= looking
>> > at
>> > abnormal scheduling behaviour.=C2=A0 Last year some scheduler= races[2] were
>> > fixed that apparently hurt system performance on EPYC quite a= bit.=C2=A0 I
>> > was told privately that applying those patches to 13.1 improv= ed IPSec
>> > throughput by ~25% on EPYC, and I wouldn't be surprised i= f there are
>> > more improvements to be had which don't involve modifying= core
>> > heuristics of the scheduler.=C2=A0 Either way this requires d= eeper analysis
>> > of ULE's micro-level behaviour; I don't think "i= nteractivity scoring is
>> > bogus" is a useful starting point.
>> >
>>
>> I provided explicit examples how it marked a background thread as<= br> >> interactive, while the real hard worker (if you will) as not
>> interactive, because said worker was not acting the way ULE expect= s.
>>
>> A bandaid for the time being will stop shafting processes giving u= p
>> their time slice early in the batch queue, along with some fairnes= s
>> for the rest who does not (like firefox). I'll hack it up for = testing.
>>
>> --
>> Mateusz Guzik <mjguzik gmail.com>
>


--
Mateusz Guzik <mjguzik gmail.com>

--0000000000002b9b9505f99748f9-- From nobody Tue Apr 18 18:22:03 2023 X-Original-To: freebsd-hackers@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 4Q1C1q2xtSz45TNN for ; Tue, 18 Apr 2023 18:22:07 +0000 (UTC) (envelope-from dan@langille.org) Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) (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 did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4Q1C1p3F0tz3k8x; Tue, 18 Apr 2023 18:22:06 +0000 (UTC) (envelope-from dan@langille.org) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=langille.org header.s=fm3 header.b=cqb9YF4C; dkim=pass header.d=messagingengine.com header.s=fm3 header.b=Iw7se3Cd; spf=pass (mx1.freebsd.org: domain of dan@langille.org designates 66.111.4.27 as permitted sender) smtp.mailfrom=dan@langille.org; dmarc=pass (policy=none) header.from=langille.org Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id 6D6FA5C0080; Tue, 18 Apr 2023 14:22:05 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute3.internal (MEProxy); Tue, 18 Apr 2023 14:22:05 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=langille.org; h= cc:cc:content-type:content-type:date:date:from:from:in-reply-to :in-reply-to:message-id:mime-version:references:reply-to:sender :subject:subject:to:to; s=fm3; t=1681842125; x=1681928525; bh=qj o3ew19coZuLvMDdwZWn0dK9dB12shp9CGx0UJ8K/s=; b=cqb9YF4C9cl03cjws8 CVs4FbXW8hjKCmsu3V3AHzy99kOy2OSoS2tDDn9DxQeKzczmQYThsv2TuZH+b1xy ZvdAwDFFfQdJkVDfWRZ/ZoLZuyCyL3jOdbS2RqJYEUJU1LbkVd4lUflIwuqL5Fm9 yKM2gyfzdEazRGVf24j4vxVRwkeoMWKKDth4NDURo22HHSDxWIRdx+63lLFUZrdr C5+cyWkPozfga3MGbDYkvA7+90WyU558hR+0nJL6umL02vwlOJLKdJqXSzHdZZYv +yPfT1m1WMOmR9E4dVPfcL8RZCAb7LRopm8pUNybgjKT6UBXoca48Kc6rH/q+/6h FoHA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-type:content-type:date:date :feedback-id:feedback-id:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:sender:subject :subject:to:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm3; t=1681842125; x=1681928525; bh=qjo3ew19coZuL vMDdwZWn0dK9dB12shp9CGx0UJ8K/s=; b=Iw7se3Cdh2fwpP7FY4c8wd2AAWdud CvUQbSZUeAFJEMA/wacNzJsx2nRMsNbXf8wnM3c/O+qRttSlT3umzpUpphYd34Tu SejFpzmJP062ZnXrExNA6xJjJJQk+8QCkvXNzS63WZNoY5Apw3ImFgeF4vCeRE3P oVJWchI098acpDMx0IGJKC7NqrimLkGYTSOOPu+SOYI8NPHgoCN/YG6DixUO217o iH1TiV4PhBgwOIfNIKiF70Hun/C1slFV0MEW4h7w9V6BcIBLPzHWQevWBj49YvR9 N5Tj/rdJyWUIDS1H5ZMAiMa7IMuYuF3Q21YJkCXu+IiZMUhSyu24yu1DA== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedrvdelkedguddvhecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmd enucfjughrpefuvfevfhfhkffffgggjggtsegrtderredtfeejnecuhfhrohhmpeffrghn ucfnrghnghhilhhlvgcuoegurghnsehlrghnghhilhhlvgdrohhrgheqnecuggftrfgrth htvghrnhepgefftdfftdegtdfgleevfedukeffheehtddvleekgeelueejhedtveefuedt ieejnecuffhomhgrihhnpehlrghnghhilhhlvgdrohhrghenucevlhhushhtvghrufhiii gvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpegurghnsehlrghnghhilhhlvgdrohhr gh X-ME-Proxy: Feedback-ID: ifbf9424e:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Tue, 18 Apr 2023 14:22:05 -0400 (EDT) Subject: Re: gpart destroy, in depth To: Graham Perrin Cc: freebsd-hackers@FreeBSD.org References: <64e88636-1e03-7ff5-7d3f-e8a36117cdbe@freebsd.org> <29390cd8-56cd-aced-990a-f2b25a00aaed@freebsd.org> From: Dan Langille Message-ID: <0acc8ae5-b154-dd5f-1d63-fb8c00f260ed@langille.org> Date: Tue, 18 Apr 2023 14:22:03 -0400 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.16; rv:52.0) Gecko/20100101 PostboxApp/7.0.60 List-Id: Technical discussions relating to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-hackers List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-hackers@freebsd.org MIME-Version: 1.0 In-Reply-To: <29390cd8-56cd-aced-990a-f2b25a00aaed@freebsd.org> Content-Type: multipart/alternative; boundary="------------419845F67D488413A84F975E" Content-Language: en-US X-Spamd-Result: default: False [-5.10 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; DWL_DNSWL_LOW(-1.00)[messagingengine.com:dkim]; NEURAL_HAM_SHORT(-1.00)[-1.000]; DMARC_POLICY_ALLOW(-0.50)[langille.org,none]; R_DKIM_ALLOW(-0.20)[langille.org:s=fm3,messagingengine.com:s=fm3]; R_SPF_ALLOW(-0.20)[+ip4:66.111.4.27]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; RCVD_IN_DNSWL_LOW(-0.10)[66.111.4.27:from]; TO_DN_SOME(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; MLMMJ_DEST(0.00)[freebsd-hackers@FreeBSD.org]; RWL_MAILSPIKE_POSSIBLE(0.00)[66.111.4.27:from]; MIME_TRACE(0.00)[0:+,1:+,2:~]; ASN(0.00)[asn:19151, ipnet:66.111.4.0/24, country:US]; RCVD_TLS_LAST(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; ARC_NA(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; FROM_HAS_DN(0.00)[]; FREEFALL_USER(0.00)[dan]; RCVD_COUNT_THREE(0.00)[4]; DKIM_TRACE(0.00)[langille.org:+,messagingengine.com:+]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[] X-Rspamd-Queue-Id: 4Q1C1p3F0tz3k8x X-Spamd-Bar: ----- X-ThisMailContainsUnwantedMimeParts: N This is a multi-part message in MIME format. --------------419845F67D488413A84F975E Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Graham Perrin wrote on 4/11/23 1:46 PM: > On 11/04/2023 14:32, Dmitry Morozovsky wrote: >>> … >> I suppose sysutils/testdisk will be useful for recovering, as most of actual >> file systems are left intact > > > Thanks, I forgot that the utility has this capability. > > This reignites hope of recovery without a third party. > > Re: my question to Warner about preciseness, now I realise, the answer > is almost certainly "Yes", because the manual page for gpart(8) notes > that the 'restore' argument/command, which does not affect the content > of partitions, can be preceded by destruction (-F). > > Also, thanks to the people who responded privately. > Any update on this please? -- Dan Langille dan@langille.org : https://langille.org/ --------------419845F67D488413A84F975E Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit Graham Perrin wrote on 4/11/23 1:46 PM:
On 11/04/2023 14:32, Dmitry Morozovsky wrote:
… 
I suppose sysutils/testdisk will be useful for recovering, as most of actual 
file systems are left intact


Thanks, I forgot that the utility has this capability.

This reignites hope of recovery without a third party.

Re: my question to Warner about preciseness, now I realise, the answer is almost certainly "Yes", because the manual page for gpart(8) notes that the 'restore' argument/command, which does not affect the content of partitions, can be preceded by destruction (-F). 

Also, thanks to the people who responded privately.

Any update on this please?

--
Dan Langille
dan@langille.org : https://langille.org/
--------------419845F67D488413A84F975E-- From nobody Wed Apr 19 08:09:58 2023 X-Original-To: freebsd-hackers@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 4Q1YPG3Qmzz458Kw; Wed, 19 Apr 2023 08:10:10 +0000 (UTC) (envelope-from egoitz@ramattack.net) Received: from cu01208b.smtpx.saremail.com (cu01208b.smtpx.saremail.com [195.16.151.183]) (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 did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4Q1YPF1wvMz3rgt; Wed, 19 Apr 2023 08:10:09 +0000 (UTC) (envelope-from egoitz@ramattack.net) Authentication-Results: mx1.freebsd.org; dkim=none; spf=pass (mx1.freebsd.org: domain of egoitz@ramattack.net designates 195.16.151.183 as permitted sender) smtp.mailfrom=egoitz@ramattack.net; dmarc=pass (policy=reject) header.from=ramattack.net Received: from www.saremail.com (unknown [194.30.0.183]) by sieve-smtp-backend01.sarenet.es (Postfix) with ESMTPA id CB10660CB9E; Wed, 19 Apr 2023 10:09:58 +0200 (CEST) List-Id: Technical discussions relating to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-hackers List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-hackers@freebsd.org MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="=_43fa8d3da048465d410f8cbd6ce665a7" Date: Wed, 19 Apr 2023 10:09:58 +0200 From: egoitz@ramattack.net To: Freebsd fs , Freebsd hackers , freebsd-hardware@freebsd.org Cc: owner-freebsd-hardware@freebsd.org Subject: Re: M2 NVME support In-Reply-To: References: Message-ID: <53338a6f44438ed85ebc4ca08c317dbc@ramattack.net> X-Sender: egoitz@ramattack.net User-Agent: Saremail webmail X-Spamd-Result: default: False [-3.52 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.73)[-0.731]; DMARC_POLICY_ALLOW(-0.50)[ramattack.net,reject]; R_SPF_ALLOW(-0.20)[+ip4:195.16.151.0/24]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; XM_UA_NO_VERSION(0.01)[]; ASN(0.00)[asn:3262, ipnet:195.16.128.0/19, country:ES]; MLMMJ_DEST(0.00)[freebsd-fs@freebsd.org,freebsd-hackers@freebsd.org,freebsd-hardware@freebsd.org]; MIME_TRACE(0.00)[0:+,1:+,2:~]; R_DKIM_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; FROM_NO_DN(0.00)[]; RCVD_TLS_LAST(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; RCPT_COUNT_THREE(0.00)[4]; ARC_NA(0.00)[]; TO_DN_SOME(0.00)[]; MID_RHS_MATCH_FROM(0.00)[] X-Rspamd-Queue-Id: 4Q1YPF1wvMz3rgt X-Spamd-Bar: --- X-ThisMailContainsUnwantedMimeParts: N --=_43fa8d3da048465d410f8cbd6ce665a7 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=UTF-8 Hi! Thank you so much mates for all your opinions and contributions. Perhaps enterprise wide for using NVME drivers, the most used format is really de U2. I assume it's just one of the form factors of NVME standard but... any issues with it mates?. Cheers, El 2023-04-13 13:25, egoitz@ramattack.net escribió: > ATENCIÓN: este correo se ha enviado desde fuera de la organización. No pinche en los enlaces ni abra los adjuntos a no ser que reconozca el remitente y sepa que el contenido es seguro. > > Hi!, > > We are in the process of buying new hardware for use with FreeBSD and ZFS. We are planning whether to buy M2 NVME disks or just SATA SSD disks (probably Samsung PM* ones). How is you experience with them?. Do you recommend one over the another?. Is perhaps better support from some of them from a specificic version to newer?. Or do they perhaps work better with some specific disk controller?. > > Best regards, --=_43fa8d3da048465d410f8cbd6ce665a7 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=UTF-8

Hi!


Thank you so much mates for all your opinions and contributions. Perhaps= enterprise wide for using NVME drivers, the most used format is really de = U2. I assume it's just one of the form factors of NVME standard but... any = issues with it mates?.


Cheers,

 


El 2023-04-13 13:25, egoitz@ramattack.net escribió:


ATENCIÓN: este correo se ha e= nviado desde fuera de la organización. No pinche en los enlaces ni a= bra los adjuntos a no ser que reconozca el remitente y sepa que el contenid= o es seguro.

Hi!,


We are in the process of buying new hardware for use with FreeBSD and ZF= S. We are planning whether to buy M2 NVME disks or just SATA SSD disks (pro= bably Samsung PM* ones). How is you experience with them?. Do you recommend= one over the another?. Is perhaps better support from some of them from a = specificic version to newer?. Or do they perhaps work better with some spec= ific disk controller?.


Best regards,

--=_43fa8d3da048465d410f8cbd6ce665a7-- From nobody Wed Apr 19 08:25:41 2023 X-Original-To: freebsd-hackers@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 4Q1YlX4RJlz459fV; Wed, 19 Apr 2023 08:26:00 +0000 (UTC) (envelope-from otis@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (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 4Q1YlW6Sffz4NN4; Wed, 19 Apr 2023 08:25:59 +0000 (UTC) (envelope-from otis@FreeBSD.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1681892759; 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: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=iiByMDj/rCq53+kqcCsjES50IqEDHXTLxW29BxU28K4=; b=o3NJ/4Nl5hQ7R235CSMgxh441MaptYwDypKJ+EAiNEVonS5GUCgq4LX4IfKNyxxWloX40A Kt/XLBGXUcBygX8Q2GPvbK8RZO/gYINte/HFHr4yj0BZEVNeJS+uk3+xYioDFz/U0+qAqg 46V6d5z0K6pUVyFLS2Iamc34JFymyui9cr4eycSAY2FS5VaklBwcrlPrVF+UJ1pAOonoo5 X2tJKqcz9kmh/hFIQd353x3b8P87T4iKokxVxAe9rQogEDvdXSvWs4McS+XIf6QVvYsFT0 jv9GBounTMhs1gRMD5izFNy5SX0n6gndDFp5FAJhbbxYqKxahTB9BQF3v6QtUA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1681892759; 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: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=iiByMDj/rCq53+kqcCsjES50IqEDHXTLxW29BxU28K4=; b=vc2kFCTHXNYV22MqzmyalXCpIUsV1hJZ9+xTKqCFQTMpNKr3qOOQitz6TnMVD5sugn/HAv nUiVbTX1cX0dO10wwugRb68JUeDRik77T8g3rfVnrSkwa9hf86EnPOUhgmOL6TrlrGZwbf tFa2IAK8eTZre0C5EO4Ht/ME311ET/ao1gPRDQOXAohvcmtZwPKgLOn3eBVD4AbmZPz7eR rubAZNLmuGj/FlJQuw+n8KxbyB9RZ72GuNZiCTM6zmmcuUnkX1JIv4nYW/4NErxJGyGxH0 ruJw4iMtlsDIUatNyuVF15+rHxlcuqxuoNhAZm7vCu0Js4LnkRL74++U2GXe+A== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1681892759; a=rsa-sha256; cv=none; b=qIAuNBErttreTGEM6cDK3CfcHSpQz/+bB/UOZerCfyGXowrY9BwjLPjGZO6c68vU7DOAOR IdxFC0SCGadEFxj+yWIb0Y4KZ7Mb7+VBp7OCwfdKSG/bYVjvQiDq+pjSggCmeoCVHa1SEb 8rXSPpdwobTBZDaZfzYGT8SE9+kVrE0g7hHdoCdZgqn6PRrlVU//ypBpogBtdxk4Ssu8Oz T+1JKZNplnzaiLkEMuebN4g4wSIjIKK9qEHoy/MFWAHMwZNPWPrv8yjqch68RxobU6jFek VO5+TJo2FT7uk+ohHD9SiVSiY1FHWetZ2ElwqehZLJQ8rSAkm6tZgFFC6l0yYQ== Received: from ns2.wilbury.net (ns2.wilbury.net [IPv6:2a01:b200:0:1:f816:3eff:fecd:13e6]) (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 ECDSA (P-256) client-digest SHA256) (Client CN "svc.wilbury.net", Issuer "R3" (verified OK)) (Authenticated sender: otis) by smtp.freebsd.org (Postfix) with ESMTPSA id 4Q1YlW4dXXz1QXg; Wed, 19 Apr 2023 08:25:59 +0000 (UTC) (envelope-from otis@FreeBSD.org) Received: from smtpclient.apple (unknown [217.73.28.193]) (Authenticated sender: juraj@lutter.sk) by svc.wilbury.net (Postfix) with ESMTPSA id 9521645CF6D; Wed, 19 Apr 2023 10:25:52 +0200 (CEST) Content-Type: text/plain; charset=utf-8 List-Id: Technical discussions relating to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-hackers List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-hackers@freebsd.org Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.500.231\)) Subject: Re: M2 NVME support From: Juraj Lutter In-Reply-To: Date: Wed, 19 Apr 2023 10:25:41 +0200 Cc: Freebsd fs , Freebsd hackers , freebsd-hardware@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <69E452A7-0B2C-49EE-A503-808A07EE1052@FreeBSD.org> References: To: egoitz@ramattack.net X-Mailer: Apple Mail (2.3731.500.231) X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED,BAYES_00 autolearn=ham autolearn_force=no version=4.0.0 X-Spam-Checker-Version: SpamAssassin 4.0.0 (2022-12-14) on ns2.wilbury.net X-ThisMailContainsUnwantedMimeParts: N > On 13 Apr 2023, at 13:25, egoitz@ramattack.net wrote: >=20 > Hi!, >=20 > We are in the process of buying new hardware for use with FreeBSD and = ZFS. We are planning whether to buy M2 NVME disks or just SATA SSD disks = (probably Samsung PM* ones). How is you experience with them?. Do you = recommend one over the another?. Is perhaps better support from some of = them from a specificic version to newer?. Or do they perhaps work better = with some specific disk controller?. My $0.02: We use DELL r740xd with NVMe and FreeBSD 13.0-STABLE (with = some NFS patches from Rick Macklem, that are now included in releng/13) and ZFS. NVMe disks are of Dell (type Dell Express Flash PM1725b 1.6TB SFF = 1.2.2). So far we haven=E2=80=99d experienced any issues with them, neither with = the server as such. The only change from the =E2=80=9Cstock=E2=80=9D state of the HW was = that we replaced Broadcom bnxt(4) NIC with Intel ix(4) NIC. The server provides NFS shares for OpenStack compute nodes. otis =E2=80=94 Juraj Lutter otis@FreeBSD.org From nobody Wed Apr 19 11:55:41 2023 X-Original-To: freebsd-hackers@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 4Q1fPm2Srgz45N3F; Wed, 19 Apr 2023 11:55:56 +0000 (UTC) (envelope-from mizhka@gmail.com) Received: from mail-lf1-x131.google.com (mail-lf1-x131.google.com [IPv6:2a00:1450:4864:20::131]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Q1fPm0Fx3z3l0d; Wed, 19 Apr 2023 11:55:56 +0000 (UTC) (envelope-from mizhka@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-lf1-x131.google.com with SMTP id 2adb3069b0e04-4ec8143400aso2862384e87.0; Wed, 19 Apr 2023 04:55:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1681905354; x=1684497354; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=nEfV0hTZhKAty+TrhWuYvkWQexPhInoBFiiSzezo5DE=; b=bn/9wk8Ur0u+UaPfse9ILSNEz+yml4LXxJ2uiSzP/Xz8j6eKJZo6KxdzkxtSZ3Pkzz N5kPrF/v8mzQ2/5N39GZF2pYAL8jhW71WC72bOkwusnaBZg5ngA6ZcZDL/1iEyT7rFoi 450sJtZucJ030Ftf/PqY9ixTylMrHZoslh5UlYeQkggmCLaHTZnAS0lfMmnMhzLe1rBB tTIBH1lEW94MvyV5jI2pxItV+X8wSAo4D9AqffDWwGtWKth4zvI/tzBm10GC42YfomCT 3V/86YdK+N2kfyTzNPxr/8tPCSo7Y1etYKqEDE5VTbjPe3g2L80oR5BChan5qy3qzf2z ucoQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1681905354; x=1684497354; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=nEfV0hTZhKAty+TrhWuYvkWQexPhInoBFiiSzezo5DE=; b=j5dknBN90ONz5dDcL/k1bZAwsQ/3RWr0ppkP/3zZFevgK1xWBEHxVj7b0oTDHIZsjk rJfJWIhZW9m64JEwbe6j/6fS/GCngOrb7Hhu6nr+XRVAc9TORoqdjSlXomAxAb3vV3Om Xx3VEG8A0JaE6Q3uYRRHtpabau0UuydaVtNSkPw2k5Wb+8UJmzjcX6G7qqJD7pbwjCxL TykvXN2U1qoO1kgNyVRnzZUQrVpCYErq1gmjRDK8rQQZLGoGw+uDzo2L97lkW573Y4+h a+QUjAejGc/yEfEW56nyw4ZTA2IZYwrjAu1TcZQRt+tQCWm0uW3j+otggts2sCycln0a 07UQ== X-Gm-Message-State: AAQBX9dKjhhBXfK73d2KIE4N7yxlOG/kThmzFKutHUw12mBgBdTOxd3k E8uIKkRfJQQdA6ukIyqoRV7AM61vZd2OazbmlZv44QFrGkM= X-Google-Smtp-Source: AKy350aNe+ujrGUvVMB5vmP37+9AlE/jskaTxEJocNk2qsDl3Hk1vqiK2PwkCB1P69xNhdvbCIW52kCMHoKFvQk5F3g= X-Received: by 2002:a05:6512:517:b0:4eb:a8c:5f22 with SMTP id o23-20020a056512051700b004eb0a8c5f22mr4146855lfb.5.1681905353644; Wed, 19 Apr 2023 04:55:53 -0700 (PDT) List-Id: Technical discussions relating to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-hackers List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-hackers@freebsd.org MIME-Version: 1.0 References: <69E452A7-0B2C-49EE-A503-808A07EE1052@FreeBSD.org> In-Reply-To: <69E452A7-0B2C-49EE-A503-808A07EE1052@FreeBSD.org> From: Michael Zhilin Date: Wed, 19 Apr 2023 14:55:41 +0300 Message-ID: Subject: Re: M2 NVME support To: Juraj Lutter Cc: egoitz@ramattack.net, Freebsd fs , Freebsd hackers , freebsd-hardware@freebsd.org Content-Type: multipart/alternative; boundary="00000000000026619e05f9af1bac" X-Rspamd-Queue-Id: 4Q1fPm0Fx3z3l0d X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N --00000000000026619e05f9af1bac Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Wed, Apr 19, 2023 at 11:26=E2=80=AFAM Juraj Lutter wr= ote: > > > > On 13 Apr 2023, at 13:25, egoitz@ramattack.net wrote: > > > > Hi!, > > > > We are in the process of buying new hardware for use with FreeBSD and > ZFS. We are planning whether to buy M2 NVME disks or just SATA SSD disks > (probably Samsung PM* ones). How is you experience with them?. Do you > recommend one over the another?. Is perhaps better support from some of > them from a specificic version to newer?. Or do they perhaps work better > with some specific disk controller?. > > > My $0.02: We use DELL r740xd with NVMe and FreeBSD 13.0-STABLE (with some > NFS patches from Rick Macklem, that are > now included in releng/13) and ZFS. > > NVMe disks are of Dell (type Dell Express Flash PM1725b 1.6TB SFF 1.2.2). > > So far we haven=E2=80=99d experienced any issues with them, neither with = the > server as such. > The only change from the =E2=80=9Cstock=E2=80=9D state of the HW was that= we replaced > Broadcom bnxt(4) NIC with Intel ix(4) NIC. > > The server provides NFS shares for OpenStack compute nodes. > > otis > > =E2=80=94 > Juraj Lutter > otis@FreeBSD.org > > > My tuppenceworth: 2x Gold 6338 2GHz ZFS pool - 10 disks Samsung PM9A3 7.68TB, 5 mirrors Gigabyte R182 NA0 No issues. Server is used as iSCSI provider for VMs (performance testing farm for databases). BR, Michael --00000000000026619e05f9af1bac Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


=
On Wed, Apr 19, 2023 at 11:26=E2=80= =AFAM Juraj Lutter <otis@freebsd.org= > wrote:
=

> On 13 Apr 2023, at 13:25, egoitz@ramattack.net wrote:
>
> Hi!,
>
> We are in the process of buying new hardware for use with FreeBSD and = ZFS. We are planning whether to buy M2 NVME disks or just SATA SSD disks (p= robably Samsung PM* ones). How is you experience with them?. Do you recomme= nd one over the another?. Is perhaps better support from some of them from = a specificic version to newer?. Or do they perhaps work better with some sp= ecific disk controller?.


My $0.02: We use DELL r740xd with NVMe and FreeBSD 13.0-STABLE (with some N= FS patches from Rick Macklem, that are
now included in releng/13) and ZFS.

NVMe disks are of Dell (type Dell Express Flash PM1725b 1.6TB SFF 1.2.2).
So far we haven=E2=80=99d experienced any issues with them, neither with th= e server as such.
The only change from the =E2=80=9Cstock=E2=80=9D state of the HW was that w= e replaced Broadcom bnxt(4) NIC with Intel ix(4) NIC.

The server provides NFS shares for OpenStack compute nodes.

otis

=E2=80=94
Juraj Lutter
otis@FreeBSD.org



My tuppenceworth:
2x Gold 63= 38 2GHz
ZFS pool - 10 disks Samsung PM9A3 7.68TB, 5 mirrors
=
Gigabyte R182 NA0

No issues. Server is used a= s iSCSI provider for VMs (performance testing farm for databases).

BR, Michael
=C2=A0
--00000000000026619e05f9af1bac-- From nobody Wed Apr 19 14:26:22 2023 X-Original-To: freebsd-hackers@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 4Q1jlM1TJ7z462jg; Wed, 19 Apr 2023 14:26:23 +0000 (UTC) (envelope-from salvadore@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [96.47.72.132]) (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 "freefall.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Q1jlM103jz3hMy; Wed, 19 Apr 2023 14:26:23 +0000 (UTC) (envelope-from salvadore@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1681914383; 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: content-transfer-encoding:content-transfer-encoding; bh=JV2s/JkH9Ish3E3BvLWHck5+PWnbW5z5nZBTxT3Yg44=; b=cE9HjZnPWVcozrYikyaTxr/tkMktZlMAkbOeYFccJa2lqfU3ztd6u2a8Jww3f61RYyiHAZ nr0qGizfpSSAz+6qKzynJKjMmf1XM7NV4m0ygMtcHQDZyiR+tuSMqRv/zmco1iIdLqNRAy ACTdKCyRiAPh2xBbCS+aT9mNUaED+tAVF1fe8VmmKaqGTzOaldnCf8n7Nfw44GOcL2E9sh toAT81psV8YUzp/a3y8PyIk9n/9HDT+yNe40+C7d2KCPvAYypB4PEEYg670Es9mXIC3VsG P8oP9JFP4XOEOxK+Y8fqsD69nixQonHv7o+wQKKTuKiGqRNekJ1VdKwbwiyVCg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1681914383; 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: content-transfer-encoding:content-transfer-encoding; bh=JV2s/JkH9Ish3E3BvLWHck5+PWnbW5z5nZBTxT3Yg44=; b=GdXfCzDoyBO7SjCB9GTW8peifnNrUze/y+Q54naVn/RFSfyvaNK7Qo0RYG40awQtHNr81E TKWcJx3TQybWk7lUgiJT/iy6kh6ExSp3NyAd16ag92PM9fSZYxtX5SnJRppOMS72v9fBH9 Y/1ZiYm902M+HRY1MRNZASDuPgVJb1qlcBD8qXhVVUZZUy2iChJI+fsVIIR2UgQRBGu1Ji dVk7LA3VZmhT/TZ6xVsYtS4FvzyrHqffgWWTSn4TkccqQ/WfOGbwr5m0uQTKaE1tvGqmvM l3r46fQ+WBXJXVFHdFgaiuKWIleJGi7fT/+29tjNtkwEcVhbmxrsu2u/otkTxw== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1681914383; a=rsa-sha256; cv=none; b=dzwrWULQcAFe4d/PztAL/PbFnTuDJTQoVnk2ghWyYaHcry2Ql1sVS7b1mqGp40X7KZtV8q gcj73ZwVW75zVqc+hOQEtQfzjFyP23IREVtSxyFfijnHuBuHqyG46e14TqloRoQAT5OFxR yEEx+eqwSgFrlE2rZ2B8Ug5pEBQ2AR3609KNHdXqF3p2fymR/8JuzgLqpFXJnjYhJEGFx6 6kRa++Xt4B291oOwglRoPpNCH0IpTh/D5vnzTXC9AnxwrLKtNNFr5SO2NZBXLA+jY03U/u frgyopgnblugOoDcvZfQiF3hvazscxmrj5/o9K6WM5pkRVJpVz9VCoCkh3FwUA== Received: by freefall.freebsd.org (Postfix, from userid 1472) id 05AA91E88B; Wed, 19 Apr 2023 14:26:23 +0000 (UTC) Date: Wed, 19 Apr 2023 14:26:22 +0000 From: Lorenzo Salvadore To: freebsd-hackers@freebsd.org Cc: freebsd-current@freebsd.org, freebsd-stable@freebsd.org Subject: FreeBSD Status Report - First Quarter 2023 Message-ID: List-Id: Technical discussions relating to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-hackers List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-hackers@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline; filename="report.txt" Content-Transfer-Encoding: 8bit X-ThisMailContainsUnwantedMimeParts: N FreeBSD Status Report First Quarter 2023 Here is the first status report of 2023, including 25 reports: we have our usual team reports, some news about cloud projects, progress in the src, ports and doc trees and more. We also provide some information about 13.2-RELEASE, which was postponed to the beginning of 2023Q2; but since this report is being published after the new version release, it is already available for installation. Users of RELEASE versions can now take advantage of many improvements such as better support for iwlwifi(4) driver or the new rtw88(4) driver, topics that have been covered in past status reports. Have a nice read. Lorenzo Salvadore, on behalf of the status team. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ A rendered version of this report is available here: https://www.freebsd.org/status/report-2023-01-2023-03/ ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Table of Contents • FreeBSD Team Reports □ FreeBSD Core Team □ FreeBSD Foundation □ FreeBSD Release Engineering Team □ Cluster Administration Team □ Continuous Integration □ Ports Collection □ Status Team • Userland □ daemon(8) improvements • Kernel □ Enabling Snapshots on Filesystems Using Journaled Soft Updates in 13.2 □ Improve the kinst DTrace provider □ Native Linux timerfd • Architectures □ Kernel Address Sanitizer on AArch64 □ bsd-user: Upstreaming and Status Report • Cloud □ FreeBSD as a Tier 1 cloud-init Platform □ OpenStack on FreeBSD • Documentation □ Documentation Engineering Team □ The FreeBSD Russian Documentation Project • Ports □ Freshports: SQL Injection Attack and Help Request □ DRM drivers (i.e. GPU drivers) □ KDE on FreeBSD □ FSX □ GCC on FreeBSD □ Valgrind - Preparing for Valgrind 3.21 • Third Party Projects □ PkgBase.live □ Containers and FreeBSD: Pot, Potluck and Potman ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ FreeBSD Team Reports Entries from the various official and semi-official teams, as found in the Administration Page. FreeBSD Core Team Contact: FreeBSD Core Team The FreeBSD Core Team is the governing body of FreeBSD. Items Core Team Charter: Draft At the first Core Team meeting of 2023, Team delegates from the December 2022 meeting in Boulder, US presented the delegation’s conclusions to the entire Team. The Team will continue to discuss the issues and work together with the FreeBSD Foundation. FreeBSD annual developers survey The Core Team together with the FreeBSD Foundation have decided that the FreeBSD Foundation will be in charge of conducting the annual developers survey. Matrix IM solution The Core Team continues to evaluate Matrix as an IM solution for FreeBSD developers. An instance has already been prepared and tests are underway. Commit bits • Core approved the src commit bit for Cheng Cui (cc@) • Core approved the restore of the src commit bit for Joseph Koshy (jkoshy@). ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ FreeBSD Foundation Links: FreeBSD Foundation URL: https://www.freebsdfoundation.org Technology Roadmap URL: https://freebsdfoundation.org/blog/technology-roadmap/ Donate URL: https://www.freebsdfoundation.org/donate/ Foundation Partnership Program URL: https://freebsdfoundation.org/our-donors/ freebsd-foundation-partnership-program/ FreeBSD Journal URL: https://www.freebsdfoundation.org/journal/ Foundation News and Events URL: https://www.freebsdfoundation.org/news-and-events/ Contact: Deb Goodkin The FreeBSD Foundation is a 501(c)(3) non-profit organization dedicated to supporting and promoting the FreeBSD Project and community worldwide. Donations from individuals and corporations are used to fund and manage software development projects, conferences, and developer summits. We also provide travel grants to FreeBSD contributors, purchase and support hardware to improve and maintain FreeBSD infrastructure, and provide resources to improve security, quality assurance, and release engineering efforts. We publish marketing material to promote, educate, and advocate for the FreeBSD Project, facilitate collaboration between commercial vendors and FreeBSD developers, and finally, represent the FreeBSD Project in executing contracts, license agreements, and other legal arrangements that require a recognized legal entity. Fundraising Efforts We finally have our 2022 fundraising numbers in and we raised a total of $1,231,096! We were short of our goal, which forced us to pull around $74,000 from our longer term investments. Besides receiving a lot of donations from you our users and contributors, we received larger donations from Juniper, Meta, Arm, Netflix, Beckhoff, Tarsnap, Modirum, Koum Family Foundation, and Stormshield. I’d like to extend a heartfelt thank you on behalf of the Foundation to everyone, including individuals and corporations, for your financial contributions in 2022! This year our budget is around $2,230,000, which includes increased spending towards FreeBSD advocacy and software development. More than half our budget is allocated towards work directly related to improving FreeBSD and keeping it secure. To fund the 2023 budget, we increased our fundraising goal and plan on using some of our investment money. When we received our first million dollar donation, the plan was to use up to 10% of it each year to increase our work to improve FreeBSD, so this has been part of our funding plan for a few years now. The 2023 budget is in the process of being approved by the board of directors and will be published once it is approved. This quarter we received donations from Juniper, Tarsnap, Microsoft, and Stormshield. So, we are already off to a great start! But, we definitely need more to support our planned efforts for 2023. If you want to help us continue our efforts, please consider making a donation towards our 2023 fundraising campaign! https://www.freebsdfoundation.org/donate/ We also have a Partnership Program for larger commercial donors. You can read about it at https://freebsdfoundation.org/our-donors/freebsd-foundation-partnership-program/. OS Improvements During the first quarter of 2023, 226 src, 39 ports, and 12 doc tree commits identified the Foundation as a sponsor. Some of this sponsored work is described in separate report entries: • Continuous Integration • Enabling Snapshots on Filesystems Using Journaled Soft Updates • FreeBSD as a Tier 1 cloud-init Platform • FreeBSD Release Engineering Team • Improve the kinst DTrace provider • OpenStack on FreeBSD Other Foundation-sponsored work included: • OpenSSH fixes and updates to versions 9.2p1 and 9.3p1 • a vendor import and update of libpcap to version 1.10.3 • improvements to tmpfs, msdosfs, and makefs • the addition of a new kqueue1 syscall • man page updates • dtrace and bhyve fixes • LinuxKPI work Continuous Integration and Quality Assurance The Foundation provides a full-time staff member and funds projects to improve continuous integration, automated testing, and overall quality assurance efforts for the FreeBSD project. You can read more about CI work in a dedicated report entry. A current project that is being funded by the FreeBSD Foundation is one to develop a set of scripts to help src developers conduct CI tests themselves. One of the main goals is to offer more visibility at the pre-commit stage. A review for the first milestone has been submitted. FreeBSD Advocacy and Education Much of our effort is dedicated to the FreeBSD Project advocacy. This may involve highlighting interesting FreeBSD work, producing literature and video tutorials, attending events, or giving presentations. The goal of the literature we produce is to teach people FreeBSD basics and help make their path to adoption or contribution easier. Other than attending and presenting at events, we encourage and help community members run their own FreeBSD events, give presentations, or staff FreeBSD tables. The FreeBSD Foundation sponsors many conferences, events, and summits around the globe. These events can be BSD-related, open source, or technology events geared towards underrepresented groups. We support the FreeBSD-focused events to help provide a venue for sharing knowledge, working together on projects, and facilitating collaboration between developers and commercial users. This all helps provide a healthy ecosystem. We support the non-FreeBSD events to promote and raise awareness of FreeBSD, to increase the use of FreeBSD in different applications, and to recruit more contributors to the Project. We are back to attending events mostly in person and began planning the in person May 2023 Developer Summit, co-located with BSDCan. In addition to attending and planning events, we are continually working on new training initiatives and updating our selection of how-to guides to facilitate getting more folks to try out FreeBSD. Check out some of our advocacy and education work: • Hosted a stand at FOSDEM 2023, February 4-5, 2023 in Brussels, Belgium. Check out the trip report. • Hosted a table at State of Open Con 2023, February, 7-8, 2023, in London, England. Read more about it. • Sponsored, held a workshop and hosted a booth at SCALE 20x, in March 9-12, 2023, Pasadena, California. Check out the trip report. • Sponsored Open Source 101, March 23 2023, in Charlotte, NC. • Sponsored and began planning the in-person May 2023 Developer Summit taking place May 17-18, 2023 in Ottawa, Ontario • Secured our Media Partner sponsorship status and submitted a workshop for All Things Open, October 15-17, 2023 in Raleigh, NC. • Submitted a Workshop proposal for FOSSY, July 13-16, 2023, in Portland, OR. • The FreeBSD Project was accepted as a Participating Organization for Google Summer of Code. • We held GSoC Office Hours to help prospective participants with questions. • Published March Newsletter • Additional Blog Posts □ Under the Hood with FreeBSD and Ampere Altra □ New Open Position: FreeBSD Userland Software Developer - Note: Posting is closed. □ BSDCan 2023 Travel Grant Application Now Open - Note: Applications are closed • FreeBSD in the News: □ VMBlog State of Open Con Q&A with Deb Goodkin We help educate the world about FreeBSD by publishing the professionally produced FreeBSD Journal. As we mentioned previously, the FreeBSD Journal is now a free publication. Find out more and access the latest issues at https://www.freebsdfoundation.org/journal/. You can find out more about events we attended and upcoming events at https://www.FreeBSDfoundation.org/news-and-events/. Legal/FreeBSD IP The Foundation owns the FreeBSD trademarks, and it is our responsibility to protect them. We also provide legal support for the core team to investigate questions that arise. Go to https://www.freebsdfoundation.org to find more about how we support FreeBSD and how we can help you! ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ FreeBSD Release Engineering Team Links: FreeBSD 13.2-RELEASE schedule URL: https://www.freebsd.org/releases/13.2R/schedule/ FreeBSD 14.0-RELEASE schedule URL: https://www.freebsd.org/releases/14.0R/schedule/ FreeBSD releases URL: https://download.freebsd.org/releases/ISO-IMAGES/ FreeBSD development snapshots URL: https://download.freebsd.org/snapshots/ISO-IMAGES/ Contact: FreeBSD Release Engineering Team, The FreeBSD Release Engineering Team is responsible for setting and publishing release schedules for official project releases of FreeBSD, announcing code freezes and maintaining the respective branches, among other things. During the first quarter of 2023, the Release Engineering Team started work on the upcoming 13.2-RELEASE. As of this writing, the 13.2 cycle has followed the originally set schedule, with the addition of fourth, fifth and sixth RC builds, postponing the final release from the end of March to early April. The Release Engineering Team continued providing weekly development snapshot builds for the main, stable/13, and stable/12 branches. Sponsor: Rubicon Communications, LLC ("Netgate") Sponsor: Tarsnap Sponsor: The FreeBSD Foundation ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Cluster Administration Team Links: Cluster Administration Team members URL: https://www.freebsd.org/administration/#t-clusteradm Contact: Cluster Administration Team FreeBSD Cluster Administration Team members are responsible for managing the machines the Project relies on to synchronise its distributed work and communications. In this quarter, the team has worked on the following: • Regular support for FreeBSD.org user accounts. • Regular disk and parts support (and replacement) for all physical hosts and mirrors. • Improve the PowerPC package builders. □ With new parts obtained through the FreeBSD Foundation, the builders now have new NVMEs with heatsinks and more memory. It helped seize the heat issue, and they are building packages faster now. • Decouple dynamic resources from the main websites. □ Work in coordination with doceng and webmaster to decouple dynamic resources from the websites, www.FreeBSD.org, and docs.FreeBSD.org. Work in progress • Large-scale network upgrade at our primary site. □ New Juniper switches arrived at our primary site to replace the former ones. We thank Juniper for the donation. • Replace old servers in our primary site and a few mirrors. □ Besides the broken CI servers, we have a few old servers with broken disks and faulty PSUs. This task is in conjunction with the FreeBSD Foundation and donors/sponsors. • Deploy infrastructure to mirror the websites. □ Since the FreeBSD website is now mostly static, we have begun deploying infrastructure to mirror www.FreeBSD.org and docs.FreeBSD.org around the world in FreeBSD project-managed mirrors. • Create a new search database engine for internal FreeBSD.org searching needs like mailing list and docs. FreeBSD Official Mirrors Overview Current locations are Australia, Brazil, Germany, Japan (two full mirror sites), Malaysia, South Africa, Taiwan, United Kingdom (full mirror site), United States of America (California, New Jersey [the primary site], and Washington). The hardware and network connection have been generously provided by: • Bytemark Hosting • Cloud and SDN Laboratory at BroadBand Tower, Inc • Department of Computer Science, National Yang Ming Chiao Tung University • Equinix • Internet Association of Australia • Internet Systems Consortium • INX-ZA • KDDI Web Communications Inc • Malaysian Research & Education Network • Metapeer • New York Internet • NIC.br • Your.Org. The Frankfurt single server mirror is the primary Europe mirror in bandwidth and usage. We are still looking for an additional full mirror site (five servers) in Europe to replace old servers in the United Kingdom full mirror site. We see a good pattern in having single mirrors in Internet Exchange Points worldwide (Australia, Brazil, and South Africa); if you know or work for some of them that could sponsor a single mirror server, please get in touch. United States (West Coast) and Europe (anywhere) are preferable places. See generic mirrored layout for full mirror site specs and tiny-mirror for a single mirror site. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Continuous Integration Links: FreeBSD Jenkins Instance URL: https://ci.FreeBSD.org FreeBSD CI artifact archive URL: https://artifact.ci.FreeBSD.org FreeBSD Jenkins wiki URL: https://wiki.FreeBSD.org/Jenkins Hosted CI wiki URL: https://wiki.FreeBSD.org/HostedCI 3rd Party Software CI URL: https://wiki.FreeBSD.org/3rdPartySoftwareCI Tickets related to freebsd-testing@ URL: https://bugs.freebsd.org/bugzilla/buglist.cgi?bug_status=open&email1=testing%40FreeBSD.org&emailassigned_to1=1&emailcc1=1&emailtype1=equals FreeBSD CI Repository URL: https://github.com/freebsd/freebsd-ci dev-ci Mailing List URL: https://lists.FreeBSD.org/subscription/dev-ci Contact: Jenkins Admin Contact: Li-Wen Hsu Contact: freebsd-testing Mailing List Contact: IRC #freebsd-ci channel on EFNet In the first quarter of 2023, we worked with the project contributors and developers to address their testing requirements. Concurrently, we collaborated with external projects and companies to enhance their products by testing more on FreeBSD. Important completed tasks: • FreeBSD-main-aarch64-KASAN_test and its supporting jobs have been added. • FreeBSD-stable-13-amd64-KASAN_test and its supporting jobs have been added. • FreeBSD-main-amd64-gcc12_build now sends failing reports to the committers whose commits may be related. • Various fixes or workarounds to the tests of non-x86 architectures from trasz@ • Present Testing/CI Status Update in AsiaBSDCon 2023 Developer Summit Work in progress tasks: • Designing and implementing pre-commit CI building and testing (to support the workflow working group) • Designing and implementing use of CI cluster to build release artifacts as release engineering does • Simplifying CI/test environment setting up for contributors and developers • Setting up the CI stage environment and putting the experimental jobs on it • Organizing the scripts in freebsd-ci repository to prepare for merging to src repository • Improving the hardware test lab and adding more hardware for testing • Merge https://reviews.freebsd.org/D38815 • Merge https://reviews.freebsd.org/D36257 Open or queued tasks: • Collecting and sorting CI tasks and ideas • Setting up public network access for the VM guest running tests • Implementing use of bare-metal hardware to run test suites • Adding drm ports building tests against -CURRENT • Planning to run ztest tests • Helping more software get FreeBSD support in its CI pipeline (Wiki pages: 3rdPartySoftwareCI, HostedCI) • Working with hosted CI providers to have better FreeBSD support Please see freebsd-testing@ related tickets for more WIP information, and don’t hesitate to join the effort! Sponsor: The FreeBSD Foundation ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Ports Collection Links: About FreeBSD Ports URL: https://www.FreeBSD.org/ports/ Contributing to Ports URL: https://docs.freebsd.org/en/articles/contributing/#ports-contributing FreeBSD Ports Monitoring URL: http://portsmon.freebsd.org/ Ports Management Team URL: https://www.freebsd.org/portmgr/ Ports Tarball URL: http://ftp.freebsd.org/pub/FreeBSD/ports/ports/ Contact: René Ladan Contact: FreeBSD Ports Management Team The Ports Management Team is responsible for overseeing the overall direction of the Ports Tree, building packages (through its subsidiary pkgmgr), and personnel matters. Below is what happened in this quarter. Currently we have around 33,500 ports in the tree. For these ports, there are 3,021 open problem reports, of which 764 are unassigned. The first three months of this year saw 9,021 commits by 163 committers for the main branch and 701 commits by 55 committers for the 2023Q1 branch. Compared to 2022Q4, this means a slight increase in the number of ports, port PRs, ports commits, and active port committers. During this quarter, we welcomed Robert Clausecker (fuz@), Vladimir Druzenko (vvd@), Robert Nagy (rnagy@), welcomed back Norikatsu Shigemura (nork@), and said goodbye to Marius Strobl (marius@). Portgmr added Muhammad Moinur Rahman (bofh@) as a new member after a successful lurkership. During the bi-weekly portmgr meetings, the following topics were discussed: • improving the situation of binary packages for kernel modules • ways to measure the impact of ports on their dependencies and how to maintain high-impact ports. During this quarter, 32 exp-runs were run to test port updates, updating default versions (LLVM to 15, MySQL to 8.0, Ruby to 3.1), and updating byacc in base. Furthermore, the default version of Go switched to 1.20 and that of Lazarus to 2.2.6. Four new USES were introduced: • budgie to support ports related to the Budgie Desktop • ldap to provide support for OpenLDAP, with a new default version of 26 (i.e. 2.6) • nextcloud to support Nextcloud applications • ruby to provide support for Ruby ports (formerly bsd.ruby.mk). ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Status Team Links: FreeBSD status reports URL: https://www.freebsd.org/status/ FreeBSD Status Report Process URL: https://docs.freebsd.org/en/articles/freebsd-status-report-process/ Archived status reports GitHub repository URL: https://github.com/freebsd/freebsd-quarterly Contact: The new workflow has started In the first quarter of this year, the status team has started implementing the new workflow that was announced at the end of 2022. Here are some details. New email addresses Last quarter we have announced the creation of new email addresses: • , for interacting with the status team directly; • , a mailing list to which you can subscribe to get reminders about status report submission deadlines. Unfortunately, the mailing list does not work as expected at the moment. The issue has been reported but no solution could be found yet. However, a work around allowed to send the second and the last reminder to the list. Automation Some automation has been introduced to ensure that no report submission is lost: • on Phabricator a herald rule automatically blocks any review touching the status reports directory: even if a report submitter forgets to add the status team as reviewer, salvadore@ (member of the status team) will block the patch anyway. The same rule will also block any review that includes the status team as reviewer, to ensure that at least one member of status has reviewed the patch before commit. • a GitHub action automatically adds the newly introduced status report label to any pull request touching the status reports directory. The GitHub action should be easily modifiable by anyone wanting to apply more labels automatically depending on the path of the modified files. More automation is planned. Documentation reorganization The status report README and How To have been updated and merged in one unique document: the FreeBSD status report process. You can check it out to read details about reports submission and publication. It will be updated regularly as the status team proceeds with the implementation of its new workflow. In particular, new material about automation is coming soon. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Userland Changes affecting the base system and programs in it. daemon(8) improvements Links: daemon(8) URL: https://man.freebsd.org/daemon/8 Libera IRC URL: https://libera.chat/ Contact: Ihor Antonov Contact: Kyle Evans An ongoing effort to improve code quality and supervision capabilities of the daemon utility. Daemon is a tool that can daemonize (send to background) or supervise any running process, automatically restarting it if it crashes. Daemon is widely used in the ports tree and can be used more in base. This quarter long_opts support was added and the codebase went through an initial refactoring phase to prepare it for further changes. There are no functional changes so far but more changes are coming. Please contact directly or on #freebsd-dev on Libera IRC if you encounter unexpected bugs. Planned work items for the next quarter: • use of kqueue for all event sources • fix Bug #268580 • fix Bug #236117 • fix Bug #254511 • fix Bug #212829 • procctl PROC_REAP_ACQUIRE We are looking for feedback, bug reports (old and new) and feature requests. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Kernel Updates to kernel subsystems/features, driver support, filesystems, and more. Enabling Snapshots on Filesystems Using Journaled Soft Updates in 13.2 Contact: Marshall Kirk McKusick The ability to make UFS/FFS filesystem snapshots when running with journaled soft updates, and using them for doing background dumps on a live filesystem, was merged to releng/13.2 during the first quarter of 2023, and lands in FreeBSD 13.2-RELEASE. Background dumps are requested by using the -L flag to dump(8). The details of this project were described in the 2022 fourth quarter report. Sponsored by: The FreeBSD Foundation ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Improve the kinst DTrace provider Links: libdtrace: implement inline function tracing URL: https://reviews.freebsd.org/D38825 dtrace(1): add -d flag to dump D script post-dt_sugar URL: https://reviews.freebsd.org/D38732 Contact: Christos Margiolis Contact: Mark Johnston kinst is a new DTrace provider created by christos@ and markj@ that allows for arbitrary instruction tracing in a kernel function. kinst has been added to the base system in FreeBSD 14.0. The 2022Q3 status report gives a brief introduction to kinst. We’re now working on inline function tracing (see review D38825 above) — a much-requested DTrace feature — by using kernel DWARF and ELF info to find the call sites of each inline copy and use that information to transform D syntax by turning kinst probes of the form: kinst::: // { } To: kinst:::, kinst:::, kinst::: // { } For example: # dtrace -dn 'kinst::cam_iosched_has_more_trim:entry { printf("\t%d\t%s", pid, execname); }' kinst::cam_iosched_get_trim:13, kinst::cam_iosched_next_bio:13, kinst::cam_iosched_schedule:40 { printf("\t%d\t%s", pid, execname); } dtrace: description 'kinst::cam_iosched_has_more_trim:entry ' matched 3 probes CPU ID FUNCTION:NAME 2 79315 cam_iosched_next_bio:13 0 kernel 2 79316 cam_iosched_schedule:40 0 kernel 0 79316 cam_iosched_schedule:40 12 intr 2 79315 cam_iosched_next_bio:13 0 kernel 2 79316 cam_iosched_schedule:40 0 kernel 0 79316 cam_iosched_schedule:40 12 intr ^C A new -d flag has also been added to dtrace(1) which dumps the D script after libdtrace has applied syntactic transformations. Further goals include: • Implement a locals structure in D which stores the local variables of the traced function. For example with kinst::foo:, we could print the local variable bar by doing print(locals→bar) inside a D script. • Port kinst to riscv and/or arm64. Sponsor: The FreeBSD Foundation ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Native Linux timerfd Links: Differential revision URL: https://reviews.freebsd.org/D38459 Contact: Jake Freeland The timerfd facility is a set of Linux-standard system calls that operate on interval timers. These timers are analogous to per-process timers but are represented by a file descriptor, rather than a process. These file descriptors may be passed to other processes, are preserved across fork(2), and may be monitored via kevent(2), poll(2), or select(2). A timerfd implementation in FreeBSD already exists for Linux compatibility, but this differential revision makes the interface native. The goal behind this change is to ease the FreeBSD porting process for programs that include timerfd. This specific implementation avoids adding new names to the system call table. Instead, timerfd_create() is wrapped by the specialfd() system call. The timerfd_gettime() and `timerfd_settime() calls are wrapped ioctl() s. Developers that wish to support FreeBSD should avoid using timerfd. The kqueue () EVFILT_TIMER filter is preferred for establishing arbitrary timers. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Architectures Updating platform-specific features and bringing in support for new hardware platforms. Kernel Address Sanitizer on AArch64 Contact: Kyle Evans Sanitizers are bug detection facilities which use a combination of instrumentation inserted by the compiler (LLVM in this case) and runtime state tracking to detect bugs in C code. They can automatically detect many types of C programming bugs, such as use-after-frees and uses of uninitialized variables, which may otherwise require substantial effort to identify. They are particularly effective in combination with regression testing suites or fuzzing tools such as syzkaller. Unlike tools such as Valgrind, software must be recompiled to enable a given sanitizer, but sanitizers can be used in the kernel. Kernels with sanitizers enabled incur a significant performance overhead from the runtime, in both CPU utilization and memory usage. As of 89c52f9d59fa, the kernel address sanitizer that was previously exclusive to amd64 is ported to arm64. Prior testing has been done on a decent variety of machines, including: • Various Ampere Altra machines • QEMU • Microsoft’s "Volterra" Devkit • bhyve (WIP). Further testing on other hardware would be both welcomed and appreciated. Sponsor: Juniper Networks, Inc. Sponsor: Klara, Inc. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ bsd-user: Upstreaming and Status Report Links: QEMU Project URL: https://qemu.org FreeBSD bsd-user qemu fork URL: https://github.com/qemu-bsd-user/qemu-bsd-user QEMU Project’s gitlab mirror URL: https://gitlab.com/qemu-project/qemu Contact: Warner Losh In this quarter, Warner upstreamed two patch sets in the qemu-project repo (with a third pending). Doug Rabson submitted some optimizations to save a handle to the qemu-user emulator in the kernel for future exec. Contact has been made with some folks interested in getting bsd-user working on NetBSD. Summer of Code project to upstream shows some interest. Upstreaming Efforts The sysctl system call was upstreamed this quarter. Doug’s changes were also upstreamed (see below). Some cleanups around NetBSD and OpenBSD and to generate syscalls on the fly are pending. Doug Rabson’s Changes As part of his container work, Doug submitted changes that allows the kernel to cache the emulator used to run programs. This allows the kernel to directly exec the new binary with that cached emulator. This simplifies bsd-user and removes one source of difference between it and linux-user. Doug also provided an important fix that prevented aarch64 from running. Bug Fixes and Improvements In addition to Doug’s fixes, Warner cleaned up things a bit this quarter. • Warner removed the final bits of 'run on any BSD code' that was present in the emulator. • While the basic system calls could be emulated between all the BSDs, their system call interface has diverged too much, and it is too feature rich for this to be feasible any time soon. • Warner had planned to just remove the NetBSD and OpenBSD bits, but there is some interest from at least the NetBSD folks for making things build. • Now that the NetBSD folks have contact information, and know direction, Warner hopes they will submit a pull request to build bsd-user on NetBSD for NetBSD. • Warner added SIGSYS support so that we can catch unimplemented system calls sooner, and improved reporting of them to get more data about what fails. • Warner cleaned up some code in the blitz branch. • We’re merged up to 8.0rc1 in upstream in the blitz branch we’re using to stay current. Summer of Code Projects There’s much interest in the bsd-user upstreaming task Warner added to Qemu’s project list. With luck, we’ll have a student to fund to do the job of upstreaming all the system calls needed to run simple programs. With a lot of luck, we’ll be able to run any program that does the same thing(s) that clang does (one goal is to have it compile hello world). Future quarterly reports will provide details, should we be fortunate enough to get a slot for this. Help Needed We can always use help with bsd-user. • Pull requests for new system calls are welcome. • Automation in generating many of the things we do by hand would be helpful (like system call argument tracing). • Enthusiastic volunteers who want to help me with the upstreaming (many tasks are easy and quick if you don’t want to commit). • Coordination with the NetBSD folks and cleanup they come up with. • Bug fixes (especially thread bugs) are needed. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Cloud Updating cloud-specific features and bringing in support for new cloud platforms. FreeBSD as a Tier 1 cloud-init Platform Links: cloud-init Website URL: https://cloud-init.io/ cloud-init Documentation URL: https://cloudinit.readthedocs.io/en/latest/ cloud-init ongoing refactorization URL: https://github.com/canonical/cloud-init/blob/main/WIP-ONGOING-REFACTORIZATION.rst Contact: Mina Galić cloud-init is the standard way of provisioning servers in the cloud. Unfortunately, cloud-init support for operating systems other than Linux is rather poor, and the lack of cloud-init support on FreeBSD is a hindrance to cloud providers who want to offer FreeBSD as a Tier 1 platform. To remedy the situation, this project aims to bring FreeBSD cloud-init support on par with Linux support. The broader plan is to lift support across all BSDs. This quarter has been going very, very slowly, for personal reasons — also for lack of access to the right resources. I have been trying to port the Infiniband functions. This has proven difficult, because it falsified my thesis that ifconfig(8) is all that is needed to figure out network interfaces on FreeBSD. While waiting for resources, I debugged a boot panic and got it fixed: 499171a98c88. This now makes it possible to boot FreeBSD on LXD — cloud-init’s CI platform. We still need to fix the high CPU usage problem, but there is already an accepted review: D38898 A cloud-init colleague who works for Azure managed to give me access to an HPC VM on Azure. Unfortunately, it was only for a limited time, and that was not enough to figure out how to get Infiniband up and running on FreeBSD — a task handled by Azure Agent on Linux, but FreeBSD’s sysutils/azure-agent is rather lacking. People interested in helping with this project could provide ifconfig(8), ibstat(8), ibv_devinfo(1), etc… pastes from their Infiniband systems. I would also be very happy about getting access to hardware with Infiniband NICs, or hearing from people who have successfully used FreeBSD on Azure HPC with Infiniband. If there is interest in that platform, I will direct some energy to fixing Azure Agent. Sponsor: The FreeBSD Foundation ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ OpenStack on FreeBSD Links: OpenStack URL: https://www.openstack.org/ OpenStack on FreeBSD URL: https://github.com/openstack-on-freebsd Contact: Chih-Hsin Chang Contact: Li-Wen Hsu This project aims to port key OpenStack components so that FreeBSD can function as an OpenStack host. In 2023 Q1, the big news is that we’re able to spawn FreeBSD instances with bhyve(8) on the OpenStack platform. But there are still some major limitations regarding the capabilities of the spawned instances that need to be resolved: • No self-service networks (only support the flat network) • No network connectivity inside the instance • Only support FreeBSD raw images (FreeBSD-13.1-RELEASE-amd64.raw tested) • No disk resize • No console integration (need to use cu(1) command manually) The step-by-step documents for constructing a POC site can be found in the docs repository. The patched version of each OpenStack component is under the same GitHub organization. Also, we attended AsiaBSDCon 2023 at the end of March and gave a short talk about the current project status at the developer summit. We got precious feedback at the event and will focus on the following for the next quarter: • Resolve the Open vSwitch networking issue • Convert each OpenStack component into FreeBSD ports People interested in helping with the project can first help check the documentation by following the installation guide. And here is an open task for the project: • FreeBSD-specific implementation for the oslo.privsep library Feedback and help are always welcome. Sponsor: The FreeBSD Foundation ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Documentation Noteworthy changes in the documentation tree, manual pages, or new external books/documents. Documentation Engineering Team Links: FreeBSD Documentation Project URL: https://www.freebsd.org/docproj/ FreeBSD Documentation Project Primer for New Contributors URL: https://docs.freebsd.org/en/books/fdp-primer/ Documentation Engineering Team URL: https://www.freebsd.org/administration/#t-doceng Contact: FreeBSD Doceng Team The doceng@ team is a body to handle some of the meta-project issues associated with the FreeBSD Documentation Project; for more information, see FreeBSD Doceng Team Charter. During the last quarter: • The doc commit bit for Pau Amma was taken in. • Lorenzo Salvadore has been proposed as doc committer. carlavilla@ and dbaio@ will mentor him. • Ryusuke SUZUKI steps down from doceng. doceng would like to thank ryusuke@ for his service. Items pending and in the discussion: • A new document about licensing has been added to the documentation set. Porter’s Handbook: Three new Uses knobs have been added to the Handbook: • New Uses = ruby. • New Uses = ldap. • New Uses = budgie. Also: • The NVIDIA install and configure options have been fixed • The Advanced Networking chapter has been improved FreeBSD Translations on Weblate Link: Translate FreeBSD on Weblate Link: FreeBSD Weblate Instance Q4 2022 Status • 12 languages • 150 registered users Languages • Chinese (Simplified) (zh-cn) (progress: 14%) • Chinese (Traditional) (zh-tw) (progress: 11%) • Dutch (nl) (progress: 1%) • French (fr) (progress: 1%) • German (de) (progress: 1%) • Indonesian (id) (progress: 1%) • Italian (it) (progress: 10%) • Korean (ko) (progress: 11%) • Norwegian (nb-no) (progress: 1%) • Persian (fa-ir) (progress: 6%) • Portuguese (pt-br) (progress: 29%) • Sinhala (si) (progress: 1%) • Spanish (es) (progress: 37%) • Turkish (tr) (progress: 5%) We want to thank everyone that contributed, translating or reviewing documents. And please, help promote this effort on your local user group, we always need more volunteers. FreeBSD Handbook working group Contact: Sergio Carlavilla Chapters 1 to 6 have been updated. Chapter 7 is work in progress. FreeBSD Website Revamp - WebApps working group Contact: Sergio Carlavilla Working group in charge of creating the new FreeBSD Documentation Portal and redesigning the FreeBSD main website and its components. FreeBSD developers can follow and join the working group on the FreeBSD Slack channel #wg-www21. The work will be divided into four phases: 1. Redesign of the Documentation Portal Create a new design, responsive and with global search. (Complete) 2. Redesign of the Manual Pages on web Scripts to generate the HTML pages using mandoc. (Complete) Public instance on https://man-dev.FreeBSD.org 3. Redesign of the Ports page on web Ports scripts to create an applications portal. (Work in progress) 4. Redesign of the FreeBSD main website New design, responsive and dark theme. (Work in progress) ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ The FreeBSD Russian Documentation Project Links: FAQ URL: https://docs.freebsd.org/ru/books/faq/ Web URL: https://www.freebsd.org/ru/ Contact: Andrey Zakhvatov The FreeBSD Russian Documentation Project current goal is to provide up-to-date Russian translations of the most significant parts of FreeBSD documentation (FAQ, Handbook, Web). It is important to support Russian-speaking persons with high-quality official technical materials and increase acceptance of the operating system around the globe. We hope that this activity will receive some support within the Russian-speaking FreeBSD community and lead to an increased number of translated materials. FAQ translation was updated and synched with the latest original version. There is also a very slight progress with web pages updates. Check the official translation guide in case you are willing to help. We will appreciate your help with translation of the following materials: • Web pages (easy) • Handbook sections (only the X11 section is in progress right now) • Articles ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Ports Changes affecting the Ports Collection, whether sweeping changes that touch most of the tree, or individual ports themselves. Freshports: SQL Injection Attack and Help Request Links: FreshPorts URL: freshports.org FreshPorts blog URL: https://news.freshports.org/ Contact: Dan Langille FreshPorts and FreshSource have reported upon FreeBSD commits for 20 years. They cover all commits, not just ports. FreshPorts tracks the commits and extracts data from the port Makefiles to create a database of information useful to both port maintainers and port users. For example, https://www.freshports.org/security/acme.sh/ shows the history of the security/acme.sh port, back to its creation in May 2017. Also available are dependencies, flavors, configuration options, and available packages. All of this is useful for both users and developers of ports. SQL Injection Attack In March, an SQL injection attack was noticed and the website was patched. Notices were sent out via our Twitter account, our status page, and a notice on the top of each page of the website. The immediate attack vector was shutdown and soon patched. Additional preventative patches were added across the website. Everything we know about has been fixed. Users were notified and advised to change their passwords. Details at: • https://news.freshports.org/2023/03/24/sql-inejection-issues-fixed/ • https://news.freshports.org/2023/03/24/freshsource-code-fixes/ Help Needed It has been over 22 years since FreshPorts started. Others must take over eventually. I’d like to start that process now. There are several aspects to FreshPorts: • FreeBSD admin (updating the OS and packages) • front end code (website - mostly PHP) • back end code (commit processing - Perl, Python, shell) • database design (PostgreSQL). The database does not change very often and requires little maintenance compared to the applications and OS. The website pretty much runs itself. From time to time, a change to the FreeBSD ports infrastructure breaks something or requires a modification, but there is rarely any urgency to fix that. This is not a huge time commitment. There is a lot of learning. While not a complex application, FreshPorts is also not trivial. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ DRM drivers (i.e. GPU drivers) Links: Git repository on GitHub URL: https://github.com/freebsd/drm-kmod Contact: Emmanuel Vadot Contact: Jean-Sébastien Pédron Contact: The Graphics team GPUs are driven by DRM drivers. They are developed specifically for Linux using a permissive license. Our mission is to port those drivers to FreeBSD to make sure modern GPUs are fully supported. We didn’t publish a report to share our progress for a long time. Therefore this status report entry will cover more than just the last quarter. Update to Linux 5.15 LTS and Linux 5.16 As of this status report, the graphics/drm-kmod meta port still installs the DRM drivers from Linux 5.10 (released on December 13, 2020) on FreeBSD 13.1 and greater. This version of the driver lacks support for recent GPUs, in particular Intel 12th gen Alder Lake ones. In the past months, we worked to update the DRM drivers to bring support for more modern AMD and Intel GPUs. The drm-kmod Git repository master branch was first updated to Linux 5.15 (released on October 31, 2021). This is an LTS branch in Linux and we wanted to take advantage of that. Thus at that point, we followed two paths: • A 5.15-lts branch was created to backport all bug fixes from Linux 5.15.x patch releases. This work is now available in the drm-515-kmod port. • The porting effort from subsequent Linux versions continued. The master branch is now at Linux 5.16 (release on January 9, 2022). The Intel driver from Linux 5.15 LTS supports 12th gen GPUs (Alder Lake). It looks to work on FreeBSD but we only tested it lightly so far. We still need more of that, that’s why graphics/drm-kmod still installs graphics/drm-510-kmod instead of graphics/drm-515-kmod. At last, FreeBSD should run as a desktop on this GPU generation and several new AMD GPUs, though problems will surely appear through real test and use. In the process, we updated firmwares to linux-firmware 20230210. Linux 5.17 and future work DRM drivers from Linux 5.17 (released on March 20, 2022) were already ported but this work still sits in its own branch. A couple of issues block further testing and the merge into the master branch: • Our current integration with vt(4), the console/terminal driver, is quite far from the DRM drivers expectations which are based on Linux' fbdev KPI. Something changed in both the Intel and AMD drivers, meaning that vt(4) breaks with the 5.17 update. • The initial Linux 5.17 release does not contain the fixes backported to Linux 5.15 LTS. It seems quite unstable with the Intel 12th gen GPU mentioned earlier. To address the issue with our vt(4) integration layer, we started to write a new vt backend specifically to use the fbdev callbacks exposed by the DRM drivers. This backend will be provided with the DRM drivers, not the FreeBSD kernel, to make it easier to maintain as the drivers evolve. This is still a work in progress and locking in particular is tricky to get right. Regarding the bad support of Intel 12th gen in the 5.17 update, bug fixes backported to Linux 5.17.x patch releases will probably not be ported as part of this work. Instead we will focus on Linux 5.18 (released on May 22, 2022) and following. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ KDE on FreeBSD Links: KDE FreeBSD URL: https://freebsd.kde.org/ KDE Community FreeBSD URL:https://community.kde.org/FreeBSD Contact: Adriaan de Groot The KDE on FreeBSD project packages CMake, Qt, and software from the KDE Community, for the FreeBSD ports tree. The software includes a full desktop environment called KDE Plasma (for both X11 and Wayland) and hundreds of applications that can be used on any FreeBSD machine. The KDE team (kde@) is part of desktop@ and x11@, building the software stack to make FreeBSD beautiful and usable as a daily-driver graphics-based desktop machine. The notes below describe mostly ports for KDE, but also include items that are important for the entire desktop stack. Infrastructure • The Qt5 ports were updated to the KDE patch collection release 5.15.8. • The Qt6 ports — these are not used by KDE yet, but there are many ports that can use Qt6 and have Qt6 flavors — were updated to release 6.4.2. Python bindings for the Qt6 release of WebEngine were added. • The cmake ports were updated to release 3.25.1 and the CPack generator for FreeBSD packages was repaired. • The graphics/poppler port — used by many PDF-viewers — was updated to release 23.01. • The sysutils/bsdisks port — used as a shim for applications that expect Linux udisks, which means most desktop environments — was updated to release 0.29. KDE Stack KDE Gear releases happen every quarter, KDE Plasma updates once a month, and KDE Frameworks have a new release every month as well. These (large) updates land shortly after their upstream release and are not listed separately. • KDE Frameworks updated to 5.104. • KDE Gear updated to 22.12.3. • KDE Plasma Desktop was updated to version 5.27. This was a long delayed update, due to unresolved issues in the support stack and a misplaced patch from an earlier release of KDE Plasma. Thanks to arrowd@ and Serenity Cybersecurity, LLC for sorting that out. • New port devel/ktextaddons was added to the tree. This is part of the KDE PIM suite, and slated to become a new KDE Framework in some future release. Related Ports • audio/amarok, one of the most popular KDE audio players of the early 2000’s, has been marked deprecated in the ports tree. It is no longer maintained upstream. • astro/kstars, an interactive planetarium, was updated to release 3.6.3. • devel/gitqlient, a graphical user interface for git, was updated to release 1.6.1 with support for new git commands. • devel/okteta, a hex viewer and editor for binary files, was updated to release 0.26.10. • devel/qcoro, C++ coroutines with Qt support, was updated to release 0.8.0. • graphics/krita, an application for painting and graphical work, was updated to release 5.1.5. • graphics/quickqanava, a graph visualization library, got a real release and an update in the ports tree. • irc/kvirc, an IRC client, was updated to the latest commit; there is no real release but there are bugfixes. • multimedia/haruna, a video and audio player, was updated to release 0.10.3. • net-im/neochat, one of a handful of Matrix clients, was updated to chase a new release of net-im/libquotient. There are continuing troubles with compatibility with older FreeBSD releases, leading to the KDE-FreeBSD team to declare FreeBSD 12 releases "effectively unsupported". • net-im/ruqola, a Rocket Chat client, was updated to release 1.9.1. • security/keysmith, a two-factor-authentication support application, was updated to release 23.01.0. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ FSX Links: GitHub URL: https://github.com/asomers/fsx-rs FreshPorts URL: https://www.freshports.org/devel/fsx/ Contact: Alan Somers The venerable FSX (File System eXerciser) tool, first written at Apple Computer in the nineties, has been a part of FreeBSD since 5.0. It stress tests file systems with a stream of randomly generated operations, verifying file data after every read. However, it has never been installed as part of the OS; it only exists in the source tree. That makes it difficult to use in CI pipelines. It has some other limitations, too. So this quarter I rewrote the entire tool in Rust. The rewrite is byte-for-byte compatible with the original, given identical seed values. Future versions will break backwards-compatibility, however, in order to add new features like fspacectl and copy_file_range. The new version can be found in the ports tree, and in time I’ll remove the original. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ GCC on FreeBSD Links: GCC Project URL: https://gcc.gnu.org GCC 11 release series URL: https://gcc.gnu.org/gcc-11/ GCC 12 release series URL: https://gcc.gnu.org/gcc-12/ Contact: Lorenzo Salvadore Contact: Gerald Pfeifer The main news this quarter is the cleaning of old GCC versions from the ports tree: this will allow for a more efficient approach to bugs. Deprecation of old GCC ports The ports tree still contains several ports related to old and unsupported GCC versions. They are usually needed as dependencies for a few old ports, that it would be better to either update to use a supported GCC release, or deprecate. Bug reports have been created to track the issue and work has already started towards its resolution. Thanks to all ports contributors who are helping. Deprecation of USE_GCC=X+ Gerald, who maintained the GCC ports for many years until recently, still contributes to the GCC maintenance on FreeBSD by helping simplify the GCC infrastructure in the ports tree, for example by removing special cases that deal with old unsupported GCC versions. This quarter the most significant of his changes is probably the removal of support for the USE_GCC=X+ construct: any port depending on GCC should set USE_GCC=yes if GCC_DEFAULT works; if not, it should require a specific version (e.g. USE_GCC=11); it cannot ask for a minimal version anymore (e.g. USE_GCC= 11+). ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Valgrind - Preparing for Valgrind 3.21 Links: Valgrind Home Page URL: https://www.valgrind.org/ Valgrind News URL: https://www.valgrind.org/docs/manual/dist.news.html Contact: Paul Floyd The devel/valgrind-devel port had an intermediate update which was submitted on 2023-02-20. This contains most of what will be in the official release of Valgrind 3.21 which is due out shortly after this status report. There is a nice improvement to the vgdb interface. It’s now much easier to see which bits of memory are initialized or not. There are a couple of fixes to the thread checks done by Helgrind. For FreeBSD specifically, the address space limit has been raised to be the same as Linux and Solaris on amd64. It was 32Gbytes and now it is 128Gbytes. The kern.proc.pathname.PID sysctl(3) has been fixed so that it returns the path of the guest exe and not that of the Valgrind host. At the same time I fixed some _umtx_op false positives and corrected auxv AT_EXECPATH in a way similar to kern.proc.pathname.PID. Syscall wrappers have been added for sctp_generic_sendmsg(2) and sctp_generic_recvmsg(2). Not yet available in the ports versions of Valgrind, there is a workaround for the use of rfork(2). Previously, since it is not supported, it would cause Valgrind to abort. Now it fails gracefully setting either EINVAL or ENOSYS. The main use of this system call is in posix_spawn(3), which will fall back to using vfork(2). The mknodat(2) syscall wrapper was incorrectly implemented on i386 and has now been fixed. There is a reworking of all of the aligned allocation functions so that they behave less like Linux glibc and more like the Valgrind build platform. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Third Party Projects Many projects build upon FreeBSD or incorporate components of FreeBSD into their project. As these projects may be of interest to the broader FreeBSD community, we sometimes include brief updates submitted by these projects in our quarterly report. The FreeBSD project makes no representation as to the accuracy or veracity of any claims in these submissions. PkgBase.live Links: Website (archive.org) URL: https://web.archive.org/web/20221220222828/https://alpha.pkgbase.live/ Website source URL: https://codeberg.org/pkgbase/website Contact: Mina Galić PkgBase.live was an unofficial repository for the FreeBSD PkgBase project. As a service, PkgBase.live was inspired by https://up.bsd.lv/, which provides freebsd-update(8) for STABLE and CURRENT branches. Hardware for PkgBase was kindly sponsored by a member of the FreeBSD community. However, as life and projects moved on, they had to decommission the hardware, giving me three months' notice. In that time, my own life was rather turbulent after a recent move to a different country so I haven’t been able to find a replacement. For the time being, PkgBase.live is dead. The website, and with it the How Did She Do it?! are still available in Git. I highly encourage copy-cats. I will also happily accept a new hardware sponsor! Please note that I have contacted the FreeBSD Project, and they are working on integrating PkgBase into release engineering. However, they are not yet ready, they also cannot "simply" take over PkgBase.live because it uses a completely different process. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Containers and FreeBSD: Pot, Potluck and Potman Links: Pot organization on GitHub URL: https://github.com/bsdpot Contact: Luca Pizzamiglio (Pot) Contact: Bretton Vine (Potluck) Contact: Michael Gmelin (Potman) Pot is a jail management tool that also supports orchestration through Nomad. During the last quarter, pot received a number of minor fixes but no new version has been released yet. Potluck aims to be to FreeBSD and pot what Dockerhub is to Linux and Docker: a repository of pot flavours and complete container images for usage with pot and in many cases Nomad. All Potluck images have been rebuilt to include the latest FreeBSD security advisories, a new Smokeping network latency monitoring image has been added, again a lot of work went into the Jitsi image, which unfortunately still seems to have some reliability issues. Also, two new blog posts are available showing how easy it is to use Potluck images, one explaining how to set up Nextcloud with Minio as object storage and Prometheus for monitoring, one showing how to run your own Matrix Synapse server using OpenLDAP for access management. As always, feedback and patches are welcome. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Last modified on: April 19, 2023 by Lorenzo Salvadore Legal Notices | © 1995-2023 The FreeBSD Project All rights reserved. The mark FreeBSD is a registered trademark of The FreeBSD Foundation and is used by The FreeBSD Project with the permission of The FreeBSD Foundation. Contact From nobody Wed Apr 19 14:35:32 2023 X-Original-To: freebsd-hackers@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 4Q1jy96TpVz462yj for ; Wed, 19 Apr 2023 14:35:45 +0000 (UTC) (envelope-from developer@lorenzosalvadore.it) Received: from mail-4018.proton.ch (mail-4018.proton.ch [185.70.40.18]) (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 "protonmail.com", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Q1jy84c1Yz3yvT for ; Wed, 19 Apr 2023 14:35:44 +0000 (UTC) (envelope-from developer@lorenzosalvadore.it) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=lorenzosalvadore.it header.s=protonmail2 header.b=IGqsQI9F; spf=pass (mx1.freebsd.org: domain of developer@lorenzosalvadore.it designates 185.70.40.18 as permitted sender) smtp.mailfrom=developer@lorenzosalvadore.it; dmarc=pass (policy=quarantine) header.from=lorenzosalvadore.it Date: Wed, 19 Apr 2023 14:35:32 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=lorenzosalvadore.it; s=protonmail2; t=1681914941; x=1682174141; bh=hTG1LBaFj0Aj3OcnAcCleHHMouY+aKDBblrpqoxhf50=; h=Date:To:From:Cc:Subject:Message-ID:In-Reply-To:References: Feedback-ID:From:To:Cc:Date:Subject:Reply-To:Feedback-ID: Message-ID:BIMI-Selector; b=IGqsQI9FRu2IlhSxWUlpZBHNnACYhB4MdAB23LwNPu4H+4dZIHuy57NkFf1OIH6Ym X3z1anAO+aggn5g/MqnYV4tPjmHWq9LerfxNU+yI5l93OgdFlEuHE/8TchBWJDdngx yqb1FVcDrzTDvKD2ZUF2ULNN3RyCTtc1afIC4OwzKWz3ZKpLawqYVML1FeNwkWUNno TYlsD1xwbjlYCmskBnRjPNIXJAzoZGftIsDFHr7uIFATPueSxQ6u9gCKQ4PbqB8hKl JPEzbi6o5CHcrSi9xCdKwfPAbO1a+5HinpautT/XOwL49+a8p7Bm7QLmuCywghscFe cho/S2kJ3J4LQ== To: freebsd-hackers@freebsd.org From: Lorenzo Salvadore Cc: freebsd-current@freebsd.org, freebsd-stable@freebsd.org Subject: Re: FreeBSD Status Report - First Quarter 2023 Message-ID: <3I6mKfXCcePfrAqIhoVuCxBJ5jvu6SlTCpavwH9J5ylbifaO7sFdlxCb9Co9ANCRftFaHxEt_mt6MP9C1sa1FlI_l1c92mo-vwHtaQKj9N0=@lorenzosalvadore.it> In-Reply-To: References: Feedback-ID: 53711648:user:proton List-Id: Technical discussions relating to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-hackers List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-hackers@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Spamd-Result: default: False [-4.00 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-0.997]; DMARC_POLICY_ALLOW(-0.50)[lorenzosalvadore.it,quarantine]; R_SPF_ALLOW(-0.20)[+ip4:185.70.40.0/24:c]; R_DKIM_ALLOW(-0.20)[lorenzosalvadore.it:s=protonmail2]; MIME_GOOD(-0.10)[text/plain]; MIME_TRACE(0.00)[0:+]; MLMMJ_DEST(0.00)[freebsd-hackers@freebsd.org]; RCVD_COUNT_ZERO(0.00)[0]; FROM_EQ_ENVFROM(0.00)[]; ARC_NA(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; ASN(0.00)[asn:62371, ipnet:185.70.40.0/24, country:CH]; FROM_HAS_DN(0.00)[]; DKIM_TRACE(0.00)[lorenzosalvadore.it:+]; RCPT_COUNT_THREE(0.00)[3]; TO_DN_NONE(0.00)[]; MID_RHS_MATCH_FROM(0.00)[] X-Rspamd-Queue-Id: 4Q1jy84c1Yz3yvT X-Spamd-Bar: --- X-ThisMailContainsUnwantedMimeParts: N ------- Original Message ------- On Wednesday, April 19th, 2023 at 4:26 PM, Lorenzo Salvadore wrote: > Last modified on: April 19, 2023 by Lorenzo Salvadore >=20 > Legal Notices | =C2=A9 1995-2023 The FreeBSD Project All rights reserved.= The mark > FreeBSD is a registered trademark of The FreeBSD Foundation and is used b= y The > FreeBSD Project with the permission of The FreeBSD Foundation. Contact I am sorry for the footer: this should not have been included in the mail v= ersion of the status report, indeed it is the footer of the web page where the rep= ort is rendered: https://www.freebsd.org/status/report-2023-01-2023-03/ . Lorenzo Salvadore From nobody Wed Apr 19 20:40:06 2023 X-Original-To: freebsd-hackers@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 4Q1t2f1BGZz46Qv2 for ; Wed, 19 Apr 2023 20:40:10 +0000 (UTC) (envelope-from grahamperrin@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 4Q1t2d66sMz3Pt3 for ; Wed, 19 Apr 2023 20:40:09 +0000 (UTC) (envelope-from grahamperrin@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1681936809; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=wGlSLGruoqTNCkghKxTIPrliEIs4to53BX7lO3SohZ0=; b=qOpxrpKAFFJoXd4/2OzSibRIBJ8C+3vs5YPLMNUib8GCifTFopLfNiXbc9v09ci9J32/Cu 1axHgTEA6toS/FE0TLxVcExWZhvvM9/DCmiqm7UNM3AAkH2z8vxQv9Q4A6PEOfNqqxKFyX UWjsU0I1mlTmuKChWhoStmXRllRWmr4sBrTLZvCKzOj2pN2Xsrgi2CIV42ymVv+xzOcaym G9VdMlkTEPHPyHIfGJcxCz3HF9/A7Xo4Im3YOc4r7JHh0G/lY2h9OTSR2nv8zV7Rw5Frt+ G+0lJIfmkVoKEPe0KRTUVevSoCUScivcu2u06AwaeMKzIhQK4CG+HPBruZdFgw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1681936809; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=wGlSLGruoqTNCkghKxTIPrliEIs4to53BX7lO3SohZ0=; b=AxGIylOGOsz38Jt1c1cIspaG/lFHYc3HAastqN4Mi6L6zhAXzUb16v5dnTtENPyBG/p5hU UNjG8iiXL2GwNJ55jaNMYFz87ElF6jQnoxRhndDICW8VNItunponldR+opYQDNNj2ZgstZ Jo22LzNHV2HWYZyn4Ih6TmADMAI+dPf2Ce25xGUrhErETGOHiJ5ejrGtd1Uuo7gI9/4wDO COgtgXuySiq/PeRQQTTInR85DVaaLr7YVBW9i7+yXYM4iSsVEaE8u3QZyQJFzScqlzU7oQ /4t4rXWi/8d9C/4L86kowgn8jwg/NakHdWeiGtXLoCWHO4/TLN8x6SX8x2lkRg== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1681936809; a=rsa-sha256; cv=none; b=qcYHajDFYr748aj9JzIZg08QPgDaWw8rnFdhhcDzE2yQcifTvJfr+5VFNszWEF8W4c6MjJ jkIGPol0ufAmQ7xY4oxTStszALoirXJHIqO+/YaqRam0cWZ3l/9bvPIx64a5VNp0rsS3Me Csdu3nbnBTDYP39j1JhIoYvbihYc4mw+KN/5Muv+Dt112AyRpkfS3JGddeSk7k8WwV1pTr hH9XRuhpUcHMrO3ObVeAlVCAgEbTv/4kV2T+Pg9f84ETUlGVc7KBVE+JkPoGYcnOXDNmwE ZIY4rZ8ZwEi++E0/Blvt9H4HKWVg//+qu/dqm3qgCePhF2wxg0eZuaAcIXi4lw== Received: from [192.168.1.10] (host-2-100-161-236.as13285.net [2.100.161.236]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) (Authenticated sender: grahamperrin) by smtp.freebsd.org (Postfix) with ESMTPSA id 4Q1t2d3n1qzQZS for ; Wed, 19 Apr 2023 20:40:09 +0000 (UTC) (envelope-from grahamperrin@freebsd.org) Message-ID: <89493d05-2964-89da-802f-7844fda8ece7@freebsd.org> Date: Wed, 19 Apr 2023 21:40:06 +0100 List-Id: Technical discussions relating to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-hackers List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-hackers@freebsd.org MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:102.0) Gecko/20100101 Thunderbird/102.10.0 Subject: Partition recoverability with APFS in the mix (was: gpart destroy, in depth) To: freebsd-hackers@freebsd.org References: <64e88636-1e03-7ff5-7d3f-e8a36117cdbe@freebsd.org> <29390cd8-56cd-aced-990a-f2b25a00aaed@freebsd.org> <0acc8ae5-b154-dd5f-1d63-fb8c00f260ed@langille.org> Content-Language: en-US From: Graham Perrin Organization: FreeBSD In-Reply-To: <0acc8ae5-b154-dd5f-1d63-fb8c00f260ed@langille.org> Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="------------deyXQwQA8FA4TEQEWunJmVBk" X-ThisMailContainsUnwantedMimeParts: N This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --------------deyXQwQA8FA4TEQEWunJmVBk Content-Type: multipart/mixed; boundary="------------WJCzbGxjdeBSOlIC8kPcUCXZ"; protected-headers="v1" From: Graham Perrin To: freebsd-hackers@freebsd.org Message-ID: <89493d05-2964-89da-802f-7844fda8ece7@freebsd.org> Subject: Partition recoverability with APFS in the mix (was: gpart destroy, in depth) References: <64e88636-1e03-7ff5-7d3f-e8a36117cdbe@freebsd.org> <29390cd8-56cd-aced-990a-f2b25a00aaed@freebsd.org> <0acc8ae5-b154-dd5f-1d63-fb8c00f260ed@langille.org> In-Reply-To: <0acc8ae5-b154-dd5f-1d63-fb8c00f260ed@langille.org> --------------WJCzbGxjdeBSOlIC8kPcUCXZ Content-Type: multipart/alternative; boundary="------------7CXoISfZd16tP8mBn3GCHRTi" --------------7CXoISfZd16tP8mBn3GCHRTi Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: base64 T24gMTgvMDQvMjAyMyAxOToyMiwgRGFuIExhbmdpbGxlIHdyb3RlOg0KPiBHcmFoYW0gUGVy cmluIHdyb3RlIG9uIDQvMTEvMjMgMTo0NiBQTToNCj4+IE9uIDExLzA0LzIwMjMgMTQ6MzIs IERtaXRyeSBNb3Jvem92c2t5IHdyb3RlOg0KPj4+PiDigKYNCj4+PiBJIHN1cHBvc2Ugc3lz dXRpbHMvdGVzdGRpc2sgd2lsbCBiZSB1c2VmdWwgZm9yIHJlY292ZXJpbmcsIGFzIG1vc3Qg b2YgYWN0dWFsDQo+Pj4gZmlsZSBzeXN0ZW1zIGFyZSBsZWZ0IGludGFjdA0KPj4NCj4+DQo+ PiBUaGFua3MsIEkgZm9yZ290IHRoYXQgdGhlIHV0aWxpdHkgaGFzIHRoaXMgY2FwYWJpbGl0 eS4NCj4+DQo+PiBUaGlzIHJlaWduaXRlcyBob3BlIG9mIHJlY292ZXJ5IHdpdGhvdXQgYSB0 aGlyZCBwYXJ0eS4NCj4+DQo+PiDigKYNCj4+DQo+PiBBbHNvLCB0aGFua3MgdG8gdGhlIHBl b3BsZSB3aG8gcmVzcG9uZGVkIHByaXZhdGVseS4NCj4+DQo+IEFueSB1cGRhdGUgb24gdGhp cyBwbGVhc2U/DQoNCg0KVGhhbmtzIGZvciBhc2tpbmcuDQoNCjxodHRwczovL21hcmttYWls Lm9yZy9tZXNzYWdlL3RqYzZvd3dicTM3bm9qYWQ+IHJlY2FsbHMgdGhhdCB0aGUgZHJpdmUg DQppcyBpbiBhbiBpTWFjLiBBdCB0aGUgdGltZSwgSSBkaWRuJ3Qga25vdyB3aGljaCB2ZXJz aW9uIG9mIG1hY09TIHJhbiANCmJlZm9yZSBJIHVzZWQgZ3BhcnQgdG8gZGVzdHJveSB0aGUg cGFydGl0aW9uIHRhYmxlLg0KDQpJIGZvdW5kIGEgMjAyMCByZWNvcmQgb2YgYW4gdXBncmFk ZSB0byBNb2phdmUuIFRoZW4sIGZyb20gDQo8aHR0cHM6Ly9lbi53aWtpcGVkaWEub3JnL3dp a2kvTWFjT1NfTW9qYXZlI0NoYW5nZXM+Og0KDQoi4oCmIFdoZW4gTW9qYXZlIGlzIGluc3Rh bGxlZCwgaXQgd2lsbCBjb252ZXJ0IHNvbGlkLXN0YXRlIGRyaXZlcyAoU1NEcyksIA0KaGFy ZCBkaXNrIGRyaXZlcyAoSEREcyksIGFuZCBGdXNpb24gRHJpdmVzLCBmcm9tIEhGUyBQbHVz IHRvIEFQRlMuIOKApiINCg0KV2l0aCB0aGUgY29udGVudCBvZiB0aGUgb3JpZ2luYWwgZHJp dmUgY2xvbmVkIHRvIGFuIGV4dGVybmFsIEhERCwgSSByYW4gDQpmb3VyIHV0aWxpdGllcyBm b3Igc2hvcnQgcGVyaW9kcyAobm90IGxvbmcgZW5vdWdoIHRvIHNjYW4gZXZlcnkgYmxvY2sp Og0KDQphKSB0aGUgdGVzdGRpc2stNy4xIHBvcnQgb2YgQ0dTZWN1cml0eSBUZXN0RGlzayAN CjxodHRwczovL3d3dy5jZ3NlY3VyaXR5Lm9yZy93aWtpL1Rlc3REaXNrPg0KDQpiKSBEaXNr IERyaWxsIDxodHRwczovL3d3dy5jbGV2ZXJmaWxlcy5jb20vPg0KDQpjKSBTdGVsbGFyIERh dGEgUmVjb3ZlcnkgDQo8aHR0cHM6Ly93d3cuc3RlbGxhcmluZm8uY29tL2ZyZWUtbWFjLWRh dGEtcmVjb3ZlcnkucGhwPg0KDQpkKSBFYXNlVVMgRGF0YSBSZWNvdmVyeSBXaXphcmQgDQo8 aHR0cHM6Ly93d3cuZWFzZXVzLmNvbS9tYWMtZGF0YS1yZWNvdmVyeS1zb2Z0d2FyZS8+IGZv ciBtYWNPUy4NCg0KVGVzdERpc2sgcXVpY2tseSBkZXRlY3RlZCBhbiBIRlMgUGx1cyBwYXJ0 aXRpb24gYWxvbmUuIE5vIHN1cnByaXNlOyBIRlMgDQpQbHVzIGlzIGFtb25nc3QgdGhlIGV4 cGxpY2l0bHkgc3VwcG9ydGVkIGZpbGUgc3lzdGVtcywgQVBGUyBpcyBub3QuIA0KQWxsb3dp bmcgVGVzdERpc2sgdG8gd3JpdGUgdGhlIGRldGVjdGVkIHRhYmxlIHByb2R1Y2VkIGEgcGFy dGl0aW9uIHdpdGggDQpubyB1c2VmdWwgY29udGVudCAoRGlzayBVdGlsaXR5IGRldGVjdGVk IG5vIGZpbGUgc3lzdGVtIGFuZCwgb2YgY291cnNlLCANCnRoZSBNYWMgY291bGQgbm90IGJv b3QgZnJvbSB0aGUgZHJpdmUpLg0KDQpEaXNrIERyaWxsIHZlcnkgcXVpY2tseSBkZXRlY3Rl ZCBhIGZldyB2b2x1bWVzLCB3aGljaCB3YXMgZW5jb3VyYWdpbmcsIA0KaG93ZXZlciBJIHNh dyBub3RoaW5nIHRoYXQgbWlnaHQgZXF1YXRlIHRvIHRoZSBBUEZTIHZvbHVtZS9maWxlc3lz dGVtIA0KdGhhdCBpbmNsdWRlcyAvVXNlcnMuDQoNClN0ZWxsYXIgRGF0YSBSZWNvdmVyeSBz ZWVtZWQgdG8gbGFjayB0aGUgYWJpbGl0eSB0byBxdWlja2x5IGRldGVjdCANCnBhcnRpdGlv bnMvdm9sdW1lcy4NCg0KRWFzZVVTIERhdGEgUmVjb3ZlcnkgV2l6YXJkIChmcmVlIGVkaXRp b24pOiBlYXJseSByZXN1bHRzIHdlcmUgKnZlcnkqIA0KZW5jb3VyYWdpbmcsIHNvIEkgKmRp ZCogYWxsb3cgaXQgdG8gc2NhbiB0aGUgZW50aXJlIGRyaXZlLiBUaGUgZW5kIA0KcmVzdWx0 IGlzIGNvbXBhcmFibGUgdG8gd2hhdCBwaWN0dXJlZCBpbiB0aGUgc2Vjb25kIHNjcmVlbnNo b3Qgb24gcGFnZSA3IA0Kb2YgdGhlIHVzZXIgZ3VpZGUgDQo8aHR0cHM6Ly93d3cuZWFzZXVz LmNvbS9zdXBwb3J0L2Rvd25sb2FkL2RvY3MvcGRmL0RhdGFfUmVjb3ZlcnlfV2l6YXJkX2Zv cl9NYWNfVXNlcl9HdWlkZS5wZGY+LiANCg0KDQpJJ20gdG8gbWVldCB0aGUgZW5kIHVzZXIg b24gTW9uZGF5IGFmdGVybm9vbi4NCg0KSW4gdGhlIG1lYW50aW1lOiB0b21vcnJvdywgSSBt aWdodCBydW4gYW4gb3V0ZGF0ZWQgKGNpcmNhIDIwMjA/KSB2ZXJzaW9uIA0Kb2YgT3V0bG9v aywgb24gYW5vdGhlciBpTWFjLCB0byB0ZWxsIGhvdyBpdCBzdG9yZXMgbG9jYWwtb25seSBl bWFpbC4gDQooSSdsbCBub3QgbmVlZCBoZWxwIHdpdGggdGhpcyDigJMgSSdtIGZhbWlsaWFy IGVub3VnaCB3aXRoIGhpZGRlbiANCmFwcGxpY2F0aW9uIHN1cHBvcnQgZGlyZWN0b3JpZXMs IGdyb3VwIGNvbnRhaW5lcnMgYW5kIHNvIG9uLikgQWxzbywgSSANCm1pZ2h0IHNhdmUgdGhl IHJlc3VsdCBvZiB0aGUgRWFzZVVTIHNjYW4sIHRoZW4gcmVydW4gRGlzayBEcmlsbCBhbmQg DQphbGxvdyBhIGZ1bGwgc2Nhbi4NCg0K --------------7CXoISfZd16tP8mBn3GCHRTi Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
On 18/04/2023 19:22, Dan Langille wrote:
Graham Perrin wrote on 4/11/23 1:46 PM:
On 11/04/2023 14:32, Dmitry Morozovsky wrote:
=E2=80=A6 
I suppose sysutils/testd=
isk will be useful for recovering, as most of actual=20
file systems are left intact


Thanks, I forgot that the utility has this capability.

This reignites hope of recovery without a third party.

=E2=80=A6=C2=A0

Also, thanks to the people who responded privately.

Any update on this please?


Thanks for asking.

<https://markmail.org/message/tjc6owwbq37nojad= > recalls that the drive is in an iMac. At the time, I didn't know which version of macOS ran before I used gpart to destroy the partition table.

I found a 2020 record of an upgrade to Mojave. Then, from <https://en.wikipedia.org/wiki/MacOS_Mojav= e#Changes>:

"=E2=80=A6 When Mojave is installed, it will convert solid-state dr= ives (SSDs), hard disk drives (HDDs), and Fusion Drives, from HFS Plus to APFS. =E2=80=A6"

With the content of the original drive cloned to an external HDD, I ran four utilities for short periods (not long enough to scan every block):

a) the testdisk-7.1 port of CGSecurity TestDisk

b) Disk Drill

c) S= tellar Data Recovery

d) EaseU= S Data Recovery Wizard for macOS.

TestDisk quickly detected an HFS Plus partition alone. No surprise; HFS Plus is amongst the explicitly supported file systems, APFS is not. Allowing TestDisk to write the detected table produced a partition with no useful content (Disk Utility detected no file system and, of course, the Mac could not boot from the drive).

Disk Drill very quickly detected a few volumes, which was encouraging, however I saw nothing that might equate to the APFS volume/filesystem that includes /Users.

Stellar Data Recovery seemed to lack the ability to quickly detect partitions/volumes.

EaseUS Data Recovery Wizard (free edition): early results were = very encouraging, so I did allow it to scan the entire drive. The end result is comparable to what pictured in the second screenshot on page 7 of the user guide.

I'm to meet the end user on Monday afternoon.

In the meantime: tomorrow, I might run an outdated (circa 2020?) version of Outlook, on another iMac, to tell how it stores local-only email. (I'll not need help with this =E2=80=93 I'm famil= iar enough with hidden application support directories, group containers and so on.) Also, I might save the result of the EaseUS scan, then rerun Disk Drill and allow a full scan.

--------------7CXoISfZd16tP8mBn3GCHRTi-- --------------WJCzbGxjdeBSOlIC8kPcUCXZ-- --------------deyXQwQA8FA4TEQEWunJmVBk Content-Type: application/pgp-signature; name="OpenPGP_signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="OpenPGP_signature" -----BEGIN PGP SIGNATURE----- wsF5BAABCAAjFiEEWT/lssMHB+28ly8Kt2dIb0oY1AsFAmRAUacFAwAAAAAACgkQt2dIb0oY1AvP 8hAApPte3r+rBSd4xAy69rM9toPDiyNJrHfUeIg9a4iTEbPYvEsB/8TdCVHg9zCE0RHr/hE4Wwfc a3UMXyv6RS0ZdZb2ybX9aXUny3bL5UEyXM/28fqNdgotec5H9N6oCiTc7XqH/9fFkJipwCOGx6ZW btsy6IeWi7gOBzQWM5mkvw6suzDgZDdYxUQTE7WW6ClV48fz/T2F+q3+dxafaWijJOARkF0Ndp86 2DLGDQn02dJ3tQM2yq/9KneDCpRZ+VULkDIR+fGWIn97NxcAKRfmPSC/e/36jStVJvRdTmp1eY2y n/h2RC0Hyw81jUBqK9KQQZ8/CM50td2OjYwAn0lyUd6HSM13800MvJcqe7FZmUhotJJlanQMQ5lA B6yMp+jmpb+5A4hpQYt3WWiKFBD+FSRdfCZccHvmM25GO6uMKRtdru1lyCj16yQbmq+v6KNfyYo7 gCq/CFDwthIjrtwk8t15hXVh6u3jNjTq2K4wuq8AxSucBTNKm8oKye1RzQ4ezCCjD20Uj6eUjexa 2OzRQ2SdZ96mWmX9Rn6Um3BvqMXzT+auX9nRkQRar8ybmQo10WEjr6QSzxzN36an8tqqZHHO1t7l boR2ALXKxuFG/LZtxwDm+JFuUQTvmVhzhms5BZ6OzVGN1g5MH6UfEtkaeF5+7dOKXsgFc0kCNzU7 HTc= =pnSQ -----END PGP SIGNATURE----- --------------deyXQwQA8FA4TEQEWunJmVBk-- From nobody Wed Apr 19 23:05:18 2023 X-Original-To: freebsd-hackers@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 4Q1xGM6RXJz45MLV; Wed, 19 Apr 2023 23:05:31 +0000 (UTC) (envelope-from aryeh.friedman@gmail.com) Received: from mail-ej1-x636.google.com (mail-ej1-x636.google.com [IPv6:2a00:1450:4864:20::636]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Q1xGM2KsTz4TCs; Wed, 19 Apr 2023 23:05:31 +0000 (UTC) (envelope-from aryeh.friedman@gmail.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20221208 header.b=p37l24d3; spf=pass (mx1.freebsd.org: domain of aryeh.friedman@gmail.com designates 2a00:1450:4864:20::636 as permitted sender) smtp.mailfrom=aryeh.friedman@gmail.com; dmarc=pass (policy=none) header.from=gmail.com Received: by mail-ej1-x636.google.com with SMTP id a640c23a62f3a-94a34a0b9e2so22558366b.1; Wed, 19 Apr 2023 16:05:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1681945530; x=1684537530; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=k+3AyvobWaqiPxaLfi9aLDqMCmKYoU0MZWoIaFpYADg=; b=p37l24d3rhBO4/X+Sqex3YzYUByq6N680lm+hwQRlrxIy/xVWAzqwyOqaPAEB2JsyF /yBBkFV0NqQOSDy9MuMX1NIEiwoDL+YQOOpykF4Gw/tzBXGrzSR1NoTRkMnmCTgXKtQB EovWeF5GDzbQgsNNgjOpEhZpSg8ugl7CfZI/KgRxoQxqKJfKt2Pq1TYDKkyvqvILCvBF N1xKPrB5CF3Y3pLOjh0I77bx+AEMT0zSLpjM9oeQNHL4KMNKzPfIFKJg6gG4Pg1GrYrg Gz7SE9qtkb3JToX55GGi5OlABAgowDDFID1veHytQugdBeHqdWudGKeqZrkygnde63uh 1J8Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1681945530; x=1684537530; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=k+3AyvobWaqiPxaLfi9aLDqMCmKYoU0MZWoIaFpYADg=; b=gopHidGiomFVVlUTMImVv0u/GzuuZ9qHghUiTLYPK7VQVnAQYzCSgmYgdViY9UgaAB grFxsHcmiNknMKxkidYhAaHW4RiR2lXrCLU+JiCZ3BDcqrcDONyMpGBcWp9z1YjA2J+f ZGgyiMCj9geHUeBNBHnubIpTf6S9pd0LJIWy5xslBG+0JWR2wdCG1iwpMkOVUolPXsl/ Luqz42IS4o5osccqxHcFcUI5RqotDDx7/2xGsVIjqiTrLBEsdtkDERxQNLNWTxhjlCrv tR0tWuCcn0vvt63zRnLc6Ni57+fYdg0UXlmMNNWkIdLBhWfA76fL4D9bS63y3VuU+vjF 2hHQ== X-Gm-Message-State: AAQBX9dyT4DXoWfpuTTeO+LM0uDnloEliD8q6R0FO2tDVpnQtnPYUYMz XXrGQ8BkVp+gKdWFXh6lQU9KgWqAJgVvMKJJOPZwWnpB X-Google-Smtp-Source: AKy350aXt2pKOEqwWnF3wLNcFoStNKJNZcIfL0E/rJv5ONFUfSPZEIZvZCdgngsggInokGAhEt6vPAq8JJFK4wfLr+Q= X-Received: by 2002:a50:ee95:0:b0:506:a446:b926 with SMTP id f21-20020a50ee95000000b00506a446b926mr8734308edr.19.1681945529660; Wed, 19 Apr 2023 16:05:29 -0700 (PDT) List-Id: Technical discussions relating to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-hackers List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-hackers@freebsd.org MIME-Version: 1.0 From: Aryeh Friedman Date: Wed, 19 Apr 2023 19:05:18 -0400 Message-ID: Subject: Installing openAI's GPT-2 Ada AI Language Model To: FreeBSD Mailing List , FreeBSD Mailing List Content-Type: text/plain; charset="UTF-8" X-Spamd-Result: default: False [-4.00 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-0.997]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20221208]; MIME_GOOD(-0.10)[text/plain]; RCVD_TLS_LAST(0.00)[]; MLMMJ_DEST(0.00)[freebsd-hackers@freebsd.org,freebsd-questions@freebsd.org]; FROM_EQ_ENVFROM(0.00)[]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; RCVD_IN_DNSWL_NONE(0.00)[2a00:1450:4864:20::636:from]; FREEMAIL_ENVFROM(0.00)[gmail.com]; MIME_TRACE(0.00)[0:+]; RCPT_COUNT_TWO(0.00)[2]; TO_DN_ALL(0.00)[]; TAGGED_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; ARC_NA(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim]; TO_MATCH_ENVRCPT_ALL(0.00)[]; FREEMAIL_FROM(0.00)[gmail.com]; MID_RHS_MATCH_FROMTLD(0.00)[]; RCVD_COUNT_TWO(0.00)[2] X-Rspamd-Queue-Id: 4Q1xGM2KsTz4TCs X-Spamd-Bar: --- X-ThisMailContainsUnwantedMimeParts: N I am attempting get the "Ada language model" that is available via their API to run locally (chatGPT says all the packages needed packages will run but as soon I finish installing pytorch it fails to import torch)... this is a on 13.2 VM designed specifically for this purpose and I have deinstalled all non-base system stuff from it. So what are the right steps? -- Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org From nobody Thu Apr 20 10:13:37 2023 X-Original-To: freebsd-hackers@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 4Q2D5z2V8Vz46cVm; Thu, 20 Apr 2023 10:14:15 +0000 (UTC) (envelope-from marietto2008@gmail.com) Received: from mail-yw1-x1136.google.com (mail-yw1-x1136.google.com [IPv6:2607:f8b0:4864:20::1136]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Q2D5y17b0z3hlF; Thu, 20 Apr 2023 10:14:14 +0000 (UTC) (envelope-from marietto2008@gmail.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20221208 header.b=s1oUhUMr; spf=pass (mx1.freebsd.org: domain of marietto2008@gmail.com designates 2607:f8b0:4864:20::1136 as permitted sender) smtp.mailfrom=marietto2008@gmail.com; dmarc=pass (policy=none) header.from=gmail.com Received: by mail-yw1-x1136.google.com with SMTP id 00721157ae682-54c12009c30so33254107b3.9; Thu, 20 Apr 2023 03:14:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1681985653; x=1684577653; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=j+fjBsCs1EobPTP9NcE3Vd9bOCISRSvxZfER0/eVB2c=; b=s1oUhUMr+7WnY5/tF47MI/kH+S1leuqVRUHhxQrXSveT0fL3/R0li8FJDG2ekKaa/W V2dyh2CVxZPjB0+0Oxepr4OTU/SqmPRe+MMK//8FzvYkyqRxBZDGK1IDE5UEluwxOEo3 TIY5FXV2/V/1SH2CaM2JbNHVSQGf2ImZ2kLqSu1H1JoltJdgcs592YelN3A3VmknFbG6 BsVhrqEK8rjpXJ0Y9avmWsBVlmiBqYJlF8JDR/Flign7xenk/YzxuavmgMqYAImUe0oS xJs/gtJB9Bcp1WQ866ktye7W3tkATt+qRKgcsHHWxEfHv9epodr/N+mUdWVoLsiKa3RK SQKg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1681985653; x=1684577653; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=j+fjBsCs1EobPTP9NcE3Vd9bOCISRSvxZfER0/eVB2c=; b=EHIqVeGP0aeAQkWsiKUCgJmORjZaN60DRpmPhdosi5W+tNEKA26TILNazLc8buVELr ZeWDlMSUMeniHSoHjbn3M6BW0fV28rH0GilBIV08gvxgY/R2jrYT7Eqsi0I9iHq2oIAs 3svmLPtnfvQctgqNm4rk/4WfYWbEiI3wY6W9f7M5p00EkJvC3TsTwtnQ+hYuuTYqHfS/ Adf9zs5OAUgRoFRadBbXDwyou9Xnsv3bLA99uKSjMQr+Bmt9xYWnjpPs0RrxWK+l8CwW oasDctYfVIwC9NSD4Fb8hjYAZtHWcJW3J4ITpRXVQsuj379EQ/0vR70Wbc6+y1UNUnbj lNNQ== X-Gm-Message-State: AAQBX9dorVbtzETLo2WXfjIYKmqbVZem5DlhzuijW/Clxbh7OldPZDr+ AqqGH6UJftV4vp01CYkQoCaC467d5OhUBNkE1bo= X-Google-Smtp-Source: AKy350Y2I9h80kQEt9aQwow3DsZYaGeYiemPueCCn81ygd5mCslAe6/MEWhrQe69pU8QZI/tvqavCYo0KvdrmsbWemA= X-Received: by 2002:a81:91c4:0:b0:54f:b875:4976 with SMTP id i187-20020a8191c4000000b0054fb8754976mr403896ywg.15.1681985653070; Thu, 20 Apr 2023 03:14:13 -0700 (PDT) List-Id: Technical discussions relating to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-hackers List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-hackers@freebsd.org MIME-Version: 1.0 References: In-Reply-To: From: Mario Marietto Date: Thu, 20 Apr 2023 12:13:37 +0200 Message-ID: Subject: Re: Installing openAI's GPT-2 Ada AI Language Model To: Aryeh Friedman Cc: FreeBSD Mailing List , FreeBSD Mailing List Content-Type: multipart/alternative; boundary="0000000000005e618f05f9c1cd85" X-Spamd-Result: default: False [-3.94 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.94)[-0.942]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20221208]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; RCPT_COUNT_THREE(0.00)[3]; FROM_HAS_DN(0.00)[]; FREEMAIL_FROM(0.00)[gmail.com]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TAGGED_RCPT(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::1136:from]; ARC_NA(0.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; MLMMJ_DEST(0.00)[freebsd-hackers@freebsd.org,freebsd-questions@freebsd.org]; DKIM_TRACE(0.00)[gmail.com:+]; TO_DN_ALL(0.00)[]; MID_RHS_MATCH_FROMTLD(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim]; FREEMAIL_TO(0.00)[gmail.com]; RCVD_TLS_LAST(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; MIME_TRACE(0.00)[0:+,1:+,2:~]; RCVD_COUNT_TWO(0.00)[2] X-Rspamd-Queue-Id: 4Q2D5y17b0z3hlF X-Spamd-Bar: --- X-ThisMailContainsUnwantedMimeParts: N --0000000000005e618f05f9c1cd85 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable I'm interested in installing fastGPT / vicuna on FreeBSD. Is the Ada Language model good ? Can you provide the instructions for installing it on Linux ? I need them to try to install it on FreeBSD. On Thu, Apr 20, 2023 at 1:06=E2=80=AFAM Aryeh Friedman wrote: > I am attempting get the "Ada language model" that is available via > their API to run locally (chatGPT says all the packages needed > packages will run but as soon I finish installing pytorch it fails to > import torch)... this is a on 13.2 VM designed specifically for this > purpose and I have deinstalled all non-base system stuff from it. So > what are the right steps? > > -- > Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org > > --=20 Mario. --0000000000005e618f05f9c1cd85 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
I'm interested in installing fastGPT / vicuna on FreeB= SD. Is the Ada Language model good ? Can you provide the instructions for i= nstalling it on Linux ? I need them to try to install it on FreeBSD.=C2=A0 =

On Thu, Apr 20, 2023 at 1:06=E2=80=AFAM Aryeh Friedman <aryeh.friedman@gmail.com> wrote:
=
I am attempting get= the "Ada language model" that is available via
their API to run locally (chatGPT says all the packages needed
packages will run but as soon I finish installing pytorch it fails to
import torch)... this is a on 13.2 VM designed specifically for this
purpose and I have deinstalled all non-base system stuff from it.=C2=A0 So<= br> what are the right steps?

--
Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org



--
Mario.
--0000000000005e618f05f9c1cd85-- From nobody Thu Apr 20 10:23:31 2023 X-Original-To: freebsd-hackers@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 4Q2DJx4lRWz46d60; Thu, 20 Apr 2023 10:23:45 +0000 (UTC) (envelope-from aryeh.friedman@gmail.com) Received: from mail-ej1-x631.google.com (mail-ej1-x631.google.com [IPv6:2a00:1450:4864:20::631]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Q2DJx1TW2z3x3J; Thu, 20 Apr 2023 10:23:45 +0000 (UTC) (envelope-from aryeh.friedman@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-ej1-x631.google.com with SMTP id kt6so5408192ejb.0; Thu, 20 Apr 2023 03:23:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1681986223; x=1684578223; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=4a0JZXApic4/0VW8TVxrjMePjBP1YuFOT1wgNIuqj/k=; b=ZiohfhZ6bLs6pi8vfxDSYAFXb6mIZJC6OB4KWdwGdSCPuO2tmdExHG9E7hGVBJrdG9 jrh44FPeQ4MAY9724vOrM7Fs3VeF+efGlXZN8L3KaYehZzEsApxcndocunD78tBdY0lg NeFkmNRf4B63Xkbe7dUHmTFOGLtqzT5KcU/tk/DVlcdMSrradCUnfV1wTgCdtphNnwW6 MDJDKaGmbDefCHUq5X9jK5Fs8pJQ5dG1N+jSlb7SsjbGxDNTds2OJGse6w3szcHQVUA6 DejuGO19mC0wESxJFSdIlcIX7xXoAEqGC8IR6y9V2ZcBu4qsfZDOVdDmvun97mYqkVpI 6EMw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1681986223; x=1684578223; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=4a0JZXApic4/0VW8TVxrjMePjBP1YuFOT1wgNIuqj/k=; b=NECt0NCoS8K676NQjuP/kUi39ZBxoxbKP+BxiE4Dd2DfQTG93yYeOciL6jmzKzvJ0X FWttUc56pRO5u4pgCly54UxfUZRpPZVfDxpDTDwYBAL4i5r0LTNS2Bf0Jk1F/ozX2fXM FTL+3wr/zBYn93R92ZjOJ6KjQ2keDdPO04mlCYQuUQTtzBGWYHthqv8PV5NpxYYjwDb+ T6Ky+crshTrlf87Hr2+CoR68KOGx6zn/6IMEZPCflc25NGpsnBPynIfUATCGZn8qILL3 POxoHh+6AuVCaxF62xCQk3LjZVSO+WabJypMPc/qNzlY7xEXEnu6XtOv94vHWTUlDraT ctOQ== X-Gm-Message-State: AAQBX9c5G9cryMYML6exSVjdJlJswEX5KF92J/tZNTbyguVx1HCkORwT ktVXYlOwfRCXSaJ8YcweS0WtiCfpn/zZZPRQsl+sTYZL X-Google-Smtp-Source: AKy350Yb3zrgBKq7SBK9dccrsXnMIxO5ZdqdlWmTrtkyRX0+MH7k3ka7KET66pdFfA+i5lsK/kyCK6v33dfYz96uW/4= X-Received: by 2002:a17:906:a990:b0:94f:6ca2:e34 with SMTP id jr16-20020a170906a99000b0094f6ca20e34mr1119833ejb.66.1681986223072; Thu, 20 Apr 2023 03:23:43 -0700 (PDT) List-Id: Technical discussions relating to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-hackers List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-hackers@freebsd.org MIME-Version: 1.0 References: In-Reply-To: From: Aryeh Friedman Date: Thu, 20 Apr 2023 06:23:31 -0400 Message-ID: Subject: Re: Installing openAI's GPT-2 Ada AI Language Model To: Mario Marietto Cc: FreeBSD Mailing List , FreeBSD Mailing List Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Rspamd-Queue-Id: 4Q2DJx1TW2z3x3J X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; TAGGED_FROM(0.00)[]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N On Thu, Apr 20, 2023 at 6:14=E2=80=AFAM Mario Marietto wrote: > > I'm interested in installing fastGPT / vicuna on FreeBSD. Is the Ada Lang= uage model good ? Can you provide the instructions for installing it on Lin= ux ? I need them to try to install it on FreeBSD. I have not been able to try it yet because I am still attempting to get *ANY* model to work in anyway shape or form on FreeBSD. Do you have any pointers on this (I don't care what language it is in).... everything comes to screeching halt when I try to get pytorch to run (doesn't build on freebsd or on alpine linux, ubuntu, centos, all don't work on byhve it seems)... then I tried to get tensor flow to run with no luck... so the question remains how the do I get any ANN model to run?!?!? > > On Thu, Apr 20, 2023 at 1:06=E2=80=AFAM Aryeh Friedman wrote: >> >> I am attempting get the "Ada language model" that is available via >> their API to run locally (chatGPT says all the packages needed >> packages will run but as soon I finish installing pytorch it fails to >> import torch)... this is a on 13.2 VM designed specifically for this >> purpose and I have deinstalled all non-base system stuff from it. So >> what are the right steps? >> >> -- >> Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org >> > > > -- > Mario. --=20 Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org From nobody Thu Apr 20 10:48:10 2023 X-Original-To: freebsd-hackers@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 4Q2Dss3Vbvz46f8g; Thu, 20 Apr 2023 10:48:49 +0000 (UTC) (envelope-from marietto2008@gmail.com) Received: from mail-yw1-x1132.google.com (mail-yw1-x1132.google.com [IPv6:2607:f8b0:4864:20::1132]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Q2Dsq6p1dz4ksc; Thu, 20 Apr 2023 10:48:47 +0000 (UTC) (envelope-from marietto2008@gmail.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20221208 header.b=NOLlJYEw; spf=pass (mx1.freebsd.org: domain of marietto2008@gmail.com designates 2607:f8b0:4864:20::1132 as permitted sender) smtp.mailfrom=marietto2008@gmail.com; dmarc=pass (policy=none) header.from=gmail.com Received: by mail-yw1-x1132.google.com with SMTP id 00721157ae682-54fa9da5e5bso35442087b3.1; Thu, 20 Apr 2023 03:48:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1681987727; x=1684579727; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=xjYTZxVKpXifYUodVCs4kGCQnq7SZlGuaiY3sDQIyw0=; b=NOLlJYEwWH5xlU0XNKMop5Rt/P5CTyUGVMsHet6BByMmh3QLHJdyWO+loPUYzqoTv2 t1mWmgcps6tnnhvSrVtHe8uKAeMo6g0AL9/vggij8W15/3gw1LmWmlQSiM1aBhxFBxTW JdKe0Fa0UWM/r2FEtzZo1Pu0lacOmT0b7ztk35++zXn4MuV+h3x2MuhHOcxptxw1pZXv u+H8ljA5XeBTq6x5dzwpLmx+v5gQIGzdR3MHURAzOAx5bOvtXqqMRp2svypKaoVo8bZw mQRcLOX4m7IJXQgJ2loXCHSbMpH0zCG61t+YnbHwt77+r6Gmv0WSuF6KwbEJf9kXopno Adnw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1681987727; x=1684579727; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=xjYTZxVKpXifYUodVCs4kGCQnq7SZlGuaiY3sDQIyw0=; b=Fl5fxC0V2tiyXb6JdetGVubR6RVIT5dwy0hjhaTU65gEnUKAd+ESl/o8sXcOKN1Tfu Gssn0upWrEEA46FC+9TBXlI9dRj4uvP1dDSRbkwsjd0LsVLa1KcBO7qCUwbHCuzK1N8o pvFK+gxx5sOZpkPufNaHJRAGlINxYMir8lOIi/DnWbAXUxFibLa9uk7YIupPIhE/uRGC oGYI7QR8KPnjw5nR/56ha6jnS+Zi4F5QNu9LbO+9OSS0EZLG9bjW0KCo69UwIC9IUbpY dJ+Ds0UZ+roKCdzpqMxSlDJEByBP+REMIVqKvU6oTqck67wQpGHuLndUiblqIS217khu 1TWQ== X-Gm-Message-State: AAQBX9elbbO8RvTtSDilRxu0qKFGEVekvwv/MDNB3QcWyB61eNwYXLp1 O2jzG1Gi0PR1v4fOG6QuZDAybWfVVQ/wK6OxGI3fL8cX/oDS8w== X-Google-Smtp-Source: AKy350ZjFnGrfKgoVtkxBRimhlIJP1KUj7kmlZZWA87eCr9xvMXQroWKAcjXeZbUl4c4XVkVobsuT5mOXvdSLoXkAgs= X-Received: by 2002:a0d:f245:0:b0:54c:272b:ee42 with SMTP id b66-20020a0df245000000b0054c272bee42mr387878ywf.48.1681987726647; Thu, 20 Apr 2023 03:48:46 -0700 (PDT) List-Id: Technical discussions relating to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-hackers List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-hackers@freebsd.org MIME-Version: 1.0 References: In-Reply-To: From: Mario Marietto Date: Thu, 20 Apr 2023 12:48:10 +0200 Message-ID: Subject: Re: Installing openAI's GPT-2 Ada AI Language Model To: Aryeh Friedman Cc: FreeBSD Mailing List , FreeBSD Mailing List Content-Type: multipart/alternative; boundary="000000000000f6a6df05f9c24884" X-Spamd-Result: default: False [-4.00 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-0.999]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36:c]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20221208]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; RCPT_COUNT_THREE(0.00)[3]; FROM_HAS_DN(0.00)[]; FREEMAIL_FROM(0.00)[gmail.com]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TAGGED_RCPT(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::1132:from]; ARC_NA(0.00)[]; RCVD_TLS_LAST(0.00)[]; MLMMJ_DEST(0.00)[freebsd-hackers@freebsd.org,freebsd-questions@freebsd.org]; DKIM_TRACE(0.00)[gmail.com:+]; TO_DN_ALL(0.00)[]; MID_RHS_MATCH_FROMTLD(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim]; FREEMAIL_TO(0.00)[gmail.com]; MIME_TRACE(0.00)[0:+,1:+,2:~]; FROM_EQ_ENVFROM(0.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; FREEMAIL_ENVFROM(0.00)[gmail.com]; RCVD_COUNT_TWO(0.00)[2] X-Rspamd-Queue-Id: 4Q2Dsq6p1dz4ksc X-Spamd-Bar: --- X-ThisMailContainsUnwantedMimeParts: N --000000000000f6a6df05f9c24884 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable This is a tutorial that I've written some time ago and that can help you to achieve your goal with some tinkering : https://www.reddit.com/r/freebsd/comments/1118eae/how_to_install_the_nvidia= _driver_5257801_cuda_12/ On Thu, Apr 20, 2023 at 12:23=E2=80=AFPM Aryeh Friedman wrote: > On Thu, Apr 20, 2023 at 6:14=E2=80=AFAM Mario Marietto > wrote: > > > > I'm interested in installing fastGPT / vicuna on FreeBSD. Is the Ada > Language model good ? Can you provide the instructions for installing it = on > Linux ? I need them to try to install it on FreeBSD. > > I have not been able to try it yet because I am still attempting to > get *ANY* model to work in anyway shape or form on FreeBSD. Do you > have any pointers on this (I don't care what language it is in).... > everything comes to screeching halt when I try to get pytorch to run > (doesn't build on freebsd or on alpine linux, ubuntu, centos, all > don't work on byhve it seems)... then I tried to get tensor flow to > run with no luck... so the question remains how the do I get > any ANN model to run?!?!? > > > > > On Thu, Apr 20, 2023 at 1:06=E2=80=AFAM Aryeh Friedman > wrote: > >> > >> I am attempting get the "Ada language model" that is available via > >> their API to run locally (chatGPT says all the packages needed > >> packages will run but as soon I finish installing pytorch it fails to > >> import torch)... this is a on 13.2 VM designed specifically for this > >> purpose and I have deinstalled all non-base system stuff from it. So > >> what are the right steps? > >> > >> -- > >> Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org > >> > > > > > > -- > > Mario. > > > > -- > Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org > --=20 Mario. --000000000000f6a6df05f9c24884 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
This is a tutorial that I've written some time ag= o and that can help you to achieve your goal with some tinkering :


On Thu, Apr 20, 2023 at 12:23=E2=80=AFPM Aryeh Friedman <aryeh.friedman@gmail.com> = wrote:
On Thu, A= pr 20, 2023 at 6:14=E2=80=AFAM Mario Marietto <marietto2008@gmail.com> wrote: >
> I'm interested in installing fastGPT / vicuna on FreeBSD. Is the A= da Language model good ? Can you provide the instructions for installing it= on Linux ? I need them to try to install it on FreeBSD.

I have not been able to try it yet because I am still attempting to
get *ANY* model to work in anyway shape or form on FreeBSD.=C2=A0 Do you have any pointers on this (I don't care what language it is in)....
everything comes to screeching halt when I try to get pytorch to run
(doesn't build on freebsd or on alpine linux, ubuntu, centos, all
don't work on byhve it seems)... then I tried to get tensor flow to
run with no luck... so the question remains how the <bleep> do I get<= br> any ANN model to run?!?!?

>
> On Thu, Apr 20, 2023 at 1:06=E2=80=AFAM Aryeh Friedman <aryeh.friedman@gmail.com= > wrote:
>>
>> I am attempting get the "Ada language model" that is ava= ilable via
>> their API to run locally (chatGPT says all the packages needed
>> packages will run but as soon I finish installing pytorch it fails= to
>> import torch)... this is a on 13.2 VM designed specifically for th= is
>> purpose and I have deinstalled all non-base system stuff from it.= =C2=A0 So
>> what are the right steps?
>>
>> --
>> Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org=
>>
>
>
> --
> Mario.



--
Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org


--
Mario.
--000000000000f6a6df05f9c24884-- From nobody Thu Apr 20 10:53:05 2023 X-Original-To: freebsd-hackers@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 4Q2Dz404N8z46fhs; Thu, 20 Apr 2023 10:53:20 +0000 (UTC) (envelope-from aryeh.friedman@gmail.com) Received: from mail-ej1-x62b.google.com (mail-ej1-x62b.google.com [IPv6:2a00:1450:4864:20::62b]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Q2Dz34hrzz3L3M; Thu, 20 Apr 2023 10:53:19 +0000 (UTC) (envelope-from aryeh.friedman@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-ej1-x62b.google.com with SMTP id a640c23a62f3a-94f0dd117dcso52241966b.3; Thu, 20 Apr 2023 03:53:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1681987997; x=1684579997; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=xskAIM7eh3n9BM51TE+9Olrq4fOts46GRTSu63n4G8Q=; b=lgzZ/yx6HAf2BqBASk/fMWMa1mIvNeB97dVyTVtT6CzwJ51C9A8JtpbdHRR+uijU3e KsZ0M8i/PO7C0Ac/LlhIlVXb15S3M5MK47xaLmIRu8ZPSGLD72RKFmIqQmtQXDzp9lQU mEk1TcD87k4tEsmuudW+ljWn0t0xGl4hsMfEJyjz7T4MItG8jrA9Xy5OjrrIDtE9BVzb q2X3WhQsF/xR5SRqIwhfygYbBM8vCAtyvpUd2Ct13bG2yaBHbRLcjqB32f2hSaLxVv0D Av3TIH9pKsSWQf43NAbl15MhMJQoaKXxPM0t5T8QzSLPdoinE6bh3fLEUgmHwum6d6vY C0pg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1681987997; x=1684579997; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=xskAIM7eh3n9BM51TE+9Olrq4fOts46GRTSu63n4G8Q=; b=LlTk+k8rAn9lTj7hGo8zbX2JNTrhlCJxsg1GhiEklgN1aa0C1UMo01HwMgAZM9lcCE OGtqSGwJ/THWpqpJnE7Xbg61I/SW+FrR3uBj11npsaoC4YVEV5FSv6sUV9EXJycNTQ7Y mC0H1d6oEbrr5Lretvs3AKSjfcURT0g6oZMq9KIkne4k+/FDvRJxBVqgOCe0CxRe0f7n jh2gIdVD8jNRJkyFXvlAXbS72vyMHRleRaJFYbp3m/iUXYJgTmfvgq+dhFEDOatzIsxa bhuyGetLt6uA5SOaGp6PA9Z8Lgns46uvYGi+Pf88AaL4Z0/nYQ6YbHgjs9gvgf+f3Xk/ KWJQ== X-Gm-Message-State: AAQBX9fghU2rlM1/1Ua0PrTz4rYkiTOsoGTVvzN2qnWXcICaqEZxHuRW g9a+7pHMIqxRQJ7pyzhyd4KXz2gMDHsBykXRc/AZpYh2 X-Google-Smtp-Source: AKy350YPIhLlEa14ptCwLES0qJmTPCX7gokdZTktu+aCbljo5X60J+D2kjkti5hLWfdKNYwc0rOmVkRYX9fIU/VmfS0= X-Received: by 2002:aa7:d94d:0:b0:504:80a4:d019 with SMTP id l13-20020aa7d94d000000b0050480a4d019mr1510322eds.12.1681987997274; Thu, 20 Apr 2023 03:53:17 -0700 (PDT) List-Id: Technical discussions relating to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-hackers List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-hackers@freebsd.org MIME-Version: 1.0 References: In-Reply-To: From: Aryeh Friedman Date: Thu, 20 Apr 2023 06:53:05 -0400 Message-ID: Subject: Re: Installing openAI's GPT-2 Ada AI Language Model To: Mario Marietto Cc: FreeBSD Mailing List , FreeBSD Mailing List Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Rspamd-Queue-Id: 4Q2Dz34hrzz3L3M X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; TAGGED_FROM(0.00)[] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N On Thu, Apr 20, 2023 at 6:48=E2=80=AFAM Mario Marietto wrote: > > This is a tutorial that I've written some time ago and that can help you = to achieve your goal with some tinkering : > > https://www.reddit.com/r/freebsd/comments/1118eae/how_to_install_the_nvid= ia_driver_5257801_cuda_12/ Running without GPU (for now) on a bhyve vm (3 CPU, 2 GB RAM and 100 GB of disk) which I intend for determining if it is worse going out and getting the hardware to do GPU. The problem I had was getting pytorch to work since it appears I have to build it from source and it blows up in that build. --=20 Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org From nobody Thu Apr 20 11:52:06 2023 X-Original-To: freebsd-hackers@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 4Q2GH62d3kz45yg1; Thu, 20 Apr 2023 11:52:18 +0000 (UTC) (envelope-from thierry@pompo.net) Received: from edna.lautre.net (edna.lautre.net [80.67.160.88]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "lautre.net", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Q2GH30QScz44F2; Thu, 20 Apr 2023 11:52:14 +0000 (UTC) (envelope-from thierry@pompo.net) Authentication-Results: mx1.freebsd.org; dkim=none; spf=pass (mx1.freebsd.org: domain of thierry@pompo.net designates 80.67.160.88 as permitted sender) smtp.mailfrom=thierry@pompo.net; dmarc=none Received: from graf.pompo.net (graf.pompo.net [82.66.0.218]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by edna.lautre.net (Postfix) with ESMTPSA id 0417210B9FF; Thu, 20 Apr 2023 13:52:06 +0200 (CEST) Received: by graf.pompo.net (Postfix, from userid 1001) id 96200E99BA1; Thu, 20 Apr 2023 13:52:06 +0200 (CEST) Date: Thu, 20 Apr 2023 13:52:06 +0200 From: Thierry Thomas To: Aryeh Friedman Cc: FreeBSD Mailing List , FreeBSD Mailing List , Yuri Victorovich Subject: Re: Installing openAI's GPT-2 Ada AI Language Model Message-ID: Mail-Followup-To: Aryeh Friedman , FreeBSD Mailing List , FreeBSD Mailing List , Yuri Victorovich References: List-Id: Technical discussions relating to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-hackers List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-hackers@freebsd.org MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="vDFMPl6w2I4LhuAD" Content-Disposition: inline In-Reply-To: X-Operating-System: FreeBSD 13.2-STABLE amd64 Organization: Kabbale Eros X-Face: (hRbQnK~Pt7$ct`!fupO(`y_WL4^-Iwn4@ly-.,[4xC4xc;y=\ipKMNm<1J>lv@PP~7Z<.tKjAnXLs: X-PGP: 0xF1C516B3C8359753 X-Spamd-Result: default: False [-4.92 / 15.00]; SIGNED_PGP(-2.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.98)[-0.977]; NEURAL_HAM_MEDIUM(-0.84)[-0.842]; FORGED_SENDER(0.30)[thierry@freebsd.org,thierry@pompo.net]; R_SPF_ALLOW(-0.20)[+mx]; MIME_GOOD(-0.20)[multipart/signed,text/plain]; FREEMAIL_TO(0.00)[gmail.com]; RCVD_TLS_LAST(0.00)[]; MLMMJ_DEST(0.00)[freebsd-hackers@freebsd.org,freebsd-questions@freebsd.org]; TO_DN_ALL(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; HAS_ORG_HEADER(0.00)[]; FROM_HAS_DN(0.00)[]; FREEFALL_USER(0.00)[thierry]; RCVD_VIA_SMTP_AUTH(0.00)[]; ASN(0.00)[asn:20766, ipnet:80.67.160.0/19, country:FR]; RCPT_COUNT_THREE(0.00)[4]; ARC_NA(0.00)[]; TAGGED_RCPT(0.00)[]; DMARC_NA(0.00)[freebsd.org]; FROM_NEQ_ENVFROM(0.00)[thierry@freebsd.org,thierry@pompo.net] X-Rspamd-Queue-Id: 4Q2GH30QScz44F2 X-Spamd-Bar: ---- X-ThisMailContainsUnwantedMimeParts: N --vDFMPl6w2I4LhuAD Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Le jeu. 20 avr. 23 =E0 12:53:05 +0200, Aryeh Friedman =E9crivait=A0: > Running without GPU (for now) on a bhyve vm (3 CPU, 2 GB RAM and 100 > GB of disk) which I intend for determining if it is worse going out > and getting the hardware to do GPU. The problem I had was getting > pytorch to work since it appears I have to build it from source and it > blows up in that build. Have you seen ? --=20 Th. Thomas. --vDFMPl6w2I4LhuAD Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQJ8BAEBCgBmBQJkQSdmXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRFNTM2QkU4NTM4NTM5OUQwMEI2RkFBNzZG MUM1MTZCM0M4MzU5NzUzAAoJEPHFFrPINZdT8akQAMUzOPcLvP7QPeNFEu8a5f8m bvRy8x7P1seBpxdip+X9DbhhmmjauyDqUy32AkPiN1lu4ps89kYdgVF5cjwHLUeg q8picFhRaHMw3z4Ogr/lW/+7sy1k9l/QZ2cEtHSPkRV00JTM/08Mgt/0Qd/G7Wpu CpdzP7ZC0Pp5DcmVVy8aunxvOo9xFqc3LfJjv8uewgDF5y9wtHUT7YX55Pr/Ye6b W3FxUiy6ydvNhBOqcS/pBt/Cn2kWpmLbLSbtmHsKiW7zMdXUulMz/ZKvpfMsw0Mi rRkVwsWllXFTq4G4EWtrozkEWrsQjauXvPrN4jWhxZfmdWBE1SBldJAwb5dguccB 6QkmJGMS0v58HNWCQ2Nh7+e3qJSI4f/Tzp2rlNkArA/0Ra7ZydUlCyP/dd/2Jd2s 1BdCD9UNO9oRuhZe2bm5uSqTx01yIPxPCIErUvGWhJVMhm4d6lFVk0p5xQFVnqYf fhNj/giViGgd2nTZODJZiC/o+fjA+9IHtzlwOf97jDVmGEYU4DQdu315uLQPJj8n tXi8pleAjm9tDKNiFqTWpeT3Rh6VpN5dJV+teP/ZnpQoCEnOVsyVT8HRZ2Ny+KuC 7gVQwbgioInnuK5eiNSrSLVVt8mSTXXu/AIIyvGQ4RtL8JC+9K1n0MtQTceg8w3h ZxOvKHP54S/chF/AVc5F =6HSl -----END PGP SIGNATURE----- --vDFMPl6w2I4LhuAD-- From nobody Thu Apr 20 15:50:13 2023 X-Original-To: freebsd-hackers@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 4Q2MYw3yhKz46Cnt; Thu, 20 Apr 2023 15:50:28 +0000 (UTC) (envelope-from aryeh.friedman@gmail.com) Received: from mail-ed1-x52a.google.com (mail-ed1-x52a.google.com [IPv6:2a00:1450:4864:20::52a]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Q2MYt4l4rz427k; Thu, 20 Apr 2023 15:50:26 +0000 (UTC) (envelope-from aryeh.friedman@gmail.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20221208 header.b=AqhGDKLH; spf=pass (mx1.freebsd.org: domain of aryeh.friedman@gmail.com designates 2a00:1450:4864:20::52a as permitted sender) smtp.mailfrom=aryeh.friedman@gmail.com; dmarc=pass (policy=none) header.from=gmail.com Received: by mail-ed1-x52a.google.com with SMTP id 4fb4d7f45d1cf-5066ce4f490so948056a12.2; Thu, 20 Apr 2023 08:50:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1682005825; x=1684597825; h=content-transfer-encoding:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=KK6QyY4brrjv5+QU457g5v+o8mcZpFMwd0NF3fGZn30=; b=AqhGDKLHdR0Xa591l8IAj3AkBqDX7nom0JhPfRahmSD8CfMl5cIe2R85Yk83r0EQA9 WVB+z1kuXFgb+sGcpLYlVVHFjhjtgjtnPAAJhjl5V/aCEn1SLgxiQTZTi0sIMFkILIId pZuLDBHFokCDJ4fVu2QmBBm4H9STBbiUHQ0vZv4jjO/PVxeWrtvy6c9OdpcxaNHlosa1 V083SWiifBTyKDLmgaesuV0Mp1YsWCizbS8Zn5w9xHy1OmOtID5gEbZuEcJd/2TnMyve FohJAiAXUtrpSjzErroRNdNHK5JurGGD42Hjg7/fdvWR1PP5Z5q4nSJs46CyDFrFOLGM nQTQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1682005825; x=1684597825; h=content-transfer-encoding:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=KK6QyY4brrjv5+QU457g5v+o8mcZpFMwd0NF3fGZn30=; b=U962YSNW7rlS38PFMxrdBkf/7M8UEn5Del3N/pJ6AIYpK+T5oTPqPaOrTA8gCwWfow 30vc6UaNRmvS2LS62meWUc2YyMxTZgWXogIudq8/1/gMyHKJfumAeso93X6l7tY16DP7 +D2hTXkiYHmdY7HQMRJVYXxl+XYCjs+bacot9+714cvpBC3Nlmsq9UGNcHow8FLig/7L G4wWtRJz4ztK/xr1lgPnqon0Q7FF9uszBhEpJpcDJiBGmv0B9KDc2lcHh/2Z8TbcHXen z7A8NZeueg8GhGK9HQssNmtBYsTLJRTiHNOno8nzmr9yVyO+R7cfSUxiBoNjE96IPsjD wsIw== X-Gm-Message-State: AAQBX9enhDffnBIeiyiBlGFfQrYtLPZIGff3/vGusQk/HX2jPc7LmgiC 9Y7U/MHjiQZUKyjfNGnnifCaQaw9GqAtBKQheXZScsPX X-Google-Smtp-Source: AKy350aAdy3/DVp6PDVEtlk2f+htdCBtwBvZM6tIBauNcF6l5tkbxxW73SqvhqLAQhh0HM48wz+6Vv0jWvUl3iTClJk= X-Received: by 2002:aa7:d686:0:b0:506:a44c:47e3 with SMTP id d6-20020aa7d686000000b00506a44c47e3mr2019659edr.16.1682005824821; Thu, 20 Apr 2023 08:50:24 -0700 (PDT) List-Id: Technical discussions relating to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-hackers List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-hackers@freebsd.org MIME-Version: 1.0 References: In-Reply-To: From: Aryeh Friedman Date: Thu, 20 Apr 2023 11:50:13 -0400 Message-ID: Subject: Re: Installing openAI's GPT-2 Ada AI Language Model To: Aryeh Friedman , FreeBSD Mailing List , FreeBSD Mailing List , Yuri Victorovich Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Spamd-Result: default: False [-4.00 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-0.998]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20221208]; MIME_GOOD(-0.10)[text/plain]; FROM_HAS_DN(0.00)[]; FREEMAIL_FROM(0.00)[gmail.com]; RCPT_COUNT_THREE(0.00)[4]; TAGGED_RCPT(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; ARC_NA(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[2a00:1450:4864:20::52a:from]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim]; TAGGED_FROM(0.00)[]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; DKIM_TRACE(0.00)[gmail.com:+]; TO_DN_ALL(0.00)[]; MID_RHS_MATCH_FROMTLD(0.00)[]; MLMMJ_DEST(0.00)[freebsd-hackers@freebsd.org,freebsd-questions@freebsd.org]; FREEMAIL_TO(0.00)[gmail.com,freebsd.org]; RCVD_TLS_LAST(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; MIME_TRACE(0.00)[0:+]; RCVD_COUNT_TWO(0.00)[2] X-Rspamd-Queue-Id: 4Q2MYt4l4rz427k X-Spamd-Bar: --- X-ThisMailContainsUnwantedMimeParts: N On Thu, Apr 20, 2023 at 7:52=E2=80=AFAM Thierry Thomas wrote: > > Le jeu. 20 avr. 23 =C3=A0 12:53:05 +0200, Aryeh Friedman > =C3=A9crivait : > > > Running without GPU (for now) on a bhyve vm (3 CPU, 2 GB RAM and 100 > > GB of disk) which I intend for determining if it is worse going out > > and getting the hardware to do GPU. The problem I had was getting > > pytorch to work since it appears I have to build it from source and it > > blows up in that build. > > Have you seen > ? This seems to be true for all OS's I guess I will have to find an intel machine... this is as bad as the motivation that led me to do petitecloud in the first place (openstack not running on AMD period). Is there just no way to run a ANN in pytorch data format in any other way that is not python (like Java?!!?) note the tensorflow port required pytorch --=20 Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org From nobody Thu Apr 20 16:24:35 2023 X-Original-To: freebsd-hackers@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 4Q2NKZ4V6yz46Gq2; Thu, 20 Apr 2023 16:24:50 +0000 (UTC) (envelope-from marietto2008@gmail.com) Received: from mail-yb1-xb2b.google.com (mail-yb1-xb2b.google.com [IPv6:2607:f8b0:4864:20::b2b]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Q2NKY0cr2z3tZc; Thu, 20 Apr 2023 16:24:49 +0000 (UTC) (envelope-from marietto2008@gmail.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20221208 header.b=Ka1Tlsgg; spf=pass (mx1.freebsd.org: domain of marietto2008@gmail.com designates 2607:f8b0:4864:20::b2b as permitted sender) smtp.mailfrom=marietto2008@gmail.com; dmarc=pass (policy=none) header.from=gmail.com Received: by mail-yb1-xb2b.google.com with SMTP id v9so2664589ybm.0; Thu, 20 Apr 2023 09:24:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1682007888; x=1684599888; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=YX74yrEuiAfM1x1vj73gVEYBGTuPM+8pfog+tiWNqOg=; b=Ka1TlsggPed/qMD+EjuhLUvVwqVwNbEdwCyAxdxoAJIqjMyyff+zgOoXLm938K6dWU HXgXxdduSHKJJJHKBLd/XFWeRDWoweTp/LZqDvniT6DPO/aP3OSdjWcJyg7yL73HV2Wy x56p8OI3mfEOFvHISPXNsJzxoN5l41WVpqUGqEtE3+IEwpuNm4Wfgn0mbgNa6Ah8hDN1 oqH/GEA/78h59EgIjq1w02HhCLW5+2BQ5pfUwC8tsZq6j+1WQQrtzVR4Q/WBHE5kb9mO p7gfXSSpLGuwiqmSaAZgCFSq+5Gjr45CF2TnVHNF2K3HyBpvM8IHUvW+mtDIZTiHbIx5 fSUA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1682007888; x=1684599888; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=YX74yrEuiAfM1x1vj73gVEYBGTuPM+8pfog+tiWNqOg=; b=XwyXex8TygNJf2j07Lcw3wijzTdhD+plIeofYX6pHtEMoL6cE3CGVhoj0C/+xDb94l i7Y2j9L3b4ljRSzQ/G/d3zrhpGSx+8MhShZms6u/U4Uyap838nsVyjG0wKuOYYpM38hU NAqBAPf0fzbj+5lcW1Cv0VNSwV+9qBnG6I0zI/dXnyiuT5+ZpM3xSPM15P3NLH6mJUw1 DaBKBaA1Qxp7Tz77xvj8znrDadiCyFRkR9FDVopLA/nt/0Oy0vV5oo40oeKb+xocGZZa hDWJ23fsu/DxiZ45n9CU4BNV4JVuLok+m3PEEKyRW84L1Ytkqd3rJ7cdq7klptAGYXyk FE0w== X-Gm-Message-State: AAQBX9cnaNkuWlDM6ylXGMc/rRIyBhugx9rtM0AW2vmxfZ+gtxIy00pf bBO4jR7ycf7MOsgL7bYmB/b7Kd+RNacfdqOyHl4= X-Google-Smtp-Source: AKy350ZpA82wAvOykSs549+9AFNVShvfR/kvt0mWBUXVrpMeRocj/VC1NjNl4X/1QPJV2rkW8eG2dpcxoVbu61K20rc= X-Received: by 2002:a25:4f0b:0:b0:b92:f80:96ec with SMTP id d11-20020a254f0b000000b00b920f8096ecmr1697785ybb.27.1682007887876; Thu, 20 Apr 2023 09:24:47 -0700 (PDT) List-Id: Technical discussions relating to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-hackers List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-hackers@freebsd.org MIME-Version: 1.0 References: In-Reply-To: From: Mario Marietto Date: Thu, 20 Apr 2023 18:24:35 +0200 Message-ID: Subject: Re: Installing openAI's GPT-2 Ada AI Language Model To: Aryeh Friedman Cc: FreeBSD Mailing List , FreeBSD Mailing List , Yuri Victorovich Content-Type: multipart/alternative; boundary="000000000000aa995005f9c6fae9" X-Spamd-Result: default: False [-4.00 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-1.000]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20221208]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; RCPT_COUNT_THREE(0.00)[4]; FROM_HAS_DN(0.00)[]; FREEMAIL_FROM(0.00)[gmail.com]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TAGGED_RCPT(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::b2b:from]; ARC_NA(0.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; MLMMJ_DEST(0.00)[freebsd-hackers@freebsd.org,freebsd-questions@freebsd.org]; DKIM_TRACE(0.00)[gmail.com:+]; TO_DN_ALL(0.00)[]; MID_RHS_MATCH_FROMTLD(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim]; FREEMAIL_TO(0.00)[gmail.com]; RCVD_TLS_LAST(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; MIME_TRACE(0.00)[0:+,1:+,2:~]; RCVD_COUNT_TWO(0.00)[2] X-Rspamd-Queue-Id: 4Q2NKY0cr2z3tZc X-Spamd-Bar: --- X-ThisMailContainsUnwantedMimeParts: N --000000000000aa995005f9c6fae9 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable try to copy and paste the commands that you have issued on pastebin...i need to understand the scenario Il gio 20 apr 2023, 17:51 Aryeh Friedman ha scritto: > On Thu, Apr 20, 2023 at 7:52=E2=80=AFAM Thierry Thomas > wrote: > > > > Le jeu. 20 avr. 23 =C3=A0 12:53:05 +0200, Aryeh Friedman < > aryeh.friedman@gmail.com> > > =C3=A9crivait : > > > > > Running without GPU (for now) on a bhyve vm (3 CPU, 2 GB RAM and 100 > > > GB of disk) which I intend for determining if it is worse going out > > > and getting the hardware to do GPU. The problem I had was getting > > > pytorch to work since it appears I have to build it from source and i= t > > > blows up in that build. > > > > Have you seen > > ? > > This seems to be true for all OS's I guess I will have to find an > intel machine... this is as bad as the motivation that led me to do > petitecloud in the first place (openstack not running on AMD period). > Is there just no way to run a ANN in pytorch data format in any other > way that is not python (like Java?!!?) note the tensorflow port > required pytorch > > > -- > Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org > > --000000000000aa995005f9c6fae9 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
try to copy and paste the commands that you have issued o= n pastebin...i need to understand the scenario

Il gio 20 apr 2023, 17:51 Ary= eh Friedman <aryeh.friedman@= gmail.com> ha scritto:
On Th= u, Apr 20, 2023 at 7:52=E2=80=AFAM Thierry Thomas <thierry@freebsd.org<= /a>> wrote:
>
> Le jeu. 20 avr. 23 =C3=A0 12:53:05 +0200, Aryeh Friedman <a= ryeh.friedman@gmail.com>
>=C2=A0 =C3=A9crivait :
>
> > Running without GPU (for now) on a bhyve vm (3 CPU, 2 GB RAM and = 100
> > GB of disk) which I intend for determining if it is worse going o= ut
> > and getting the hardware to do GPU.=C2=A0 =C2=A0The problem I had= was getting
> > pytorch to work since it appears I have to build it from source a= nd it
> > blows up in that build.
>
> Have you seen
> <https://bugs.freebsd.o= rg/bugzilla/show_bug.cgi?id=3D269739> ?

This seems to be true for all OS's I guess I will have to find an
intel machine... this is as bad as the motivation that led me to do
petitecloud in the first place (openstack not running on AMD period).
=C2=A0Is there just no way to run a ANN in pytorch data format in any other=
way that is not python (like Java?!!?) note the tensorflow port
required pytorch


--
Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org

--000000000000aa995005f9c6fae9-- From nobody Thu Apr 20 21:34:22 2023 X-Original-To: freebsd-hackers@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 4Q2WBn6846z46cwb for ; Thu, 20 Apr 2023 21:34:25 +0000 (UTC) (envelope-from mjguzik@gmail.com) Received: from mail-oo1-xc29.google.com (mail-oo1-xc29.google.com [IPv6:2607:f8b0:4864:20::c29]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Q2WBm4kJsz3mHx for ; Thu, 20 Apr 2023 21:34:24 +0000 (UTC) (envelope-from mjguzik@gmail.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20221208 header.b=XL6uz+Y5; spf=pass (mx1.freebsd.org: domain of mjguzik@gmail.com designates 2607:f8b0:4864:20::c29 as permitted sender) smtp.mailfrom=mjguzik@gmail.com; dmarc=pass (policy=none) header.from=gmail.com Received: by mail-oo1-xc29.google.com with SMTP id 006d021491bc7-54506afdf60so694256eaf.3 for ; Thu, 20 Apr 2023 14:34:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1682026463; x=1684618463; h=cc:to:subject:message-id:date:from:references:in-reply-to :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=wTgQwIwsP1zLOTiplI6aiAH+DBLqlrd4kp1PcHBybNQ=; b=XL6uz+Y53AArRWRnQAO44cSaaagPflfYBn4Dhfs4SW2OqtdhJ1ML4d/XrM5zJaG/7w /S+tG+tfg3PvkgD1+m7rz719iIT9XwT/n8moH4zQ87pGugapjqjJDpyyVtEn0AX/BFg+ G7tEPsKgy/bScD8qc32ftwk2jALJxB41fjzSuN/Rp6xKz8wrk3XKARkn0Yx66Vo7ttom iv1FhZ8bDoTjL9chrx+Nu3I67jxqSLuHZZXktQJ2nFIBqQEdtfQPrskhIftOmvCO8YI9 Oo0Ztl6xooQ0iabN7LeeC6wjoJ7x9zvW1P3qMdQD39x47v2ydsqvEavPOTOXcMIjDykh 0IMQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1682026463; x=1684618463; h=cc:to:subject:message-id:date:from:references:in-reply-to :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=wTgQwIwsP1zLOTiplI6aiAH+DBLqlrd4kp1PcHBybNQ=; b=KKsLScIn1o02KopXQwHsxh+4ZZ5Rk7n2dSQwdBQ3+nF8fDgqWOSPx6xCOWPx3DFoMQ DEW9nUXLEE2EyaCoBwgTeXMQQ9qhRnav3fe5yL/x00SnL+H4VTtbMPVfJN+Y3rkjH5zL dKP7K4eEDB3mf5GnHpVaMP/WRaptZoZ9VbCk5hYogKFheHr8ZS8AgpB7sJ2F+B3gD1tB fE/v3IJvk2qDBBt7Eiwmv7RgwkBB9/ZaYLUdE4iF58paFmvXjPaVp85cfdEZo6odo26e MQbFFLmwkgGluzWaowVBC/OHf/F1RzzDgyDwSU9Z1EFmpRIioJ/DSLkmxG13zcwhq2yV 5STw== X-Gm-Message-State: AAQBX9elHv67WAtHyayZ9kzODAWH+LO60o2/3eTN1hiMBV8ASci/AE0x qQTxlaIOkjBfbrVTOQ7J51iZ48gy5+xHMbEhgmb1E0Iq X-Google-Smtp-Source: AKy350YF9trIK2iHkfatw2Ic1Vs3bRRT8F5EhPDWfqwotgcutaZP4nI2y0kBHmsC5zslvGfHeGYUCMdYHTAFXVp6xIA= X-Received: by 2002:a4a:b1c4:0:b0:546:da24:333d with SMTP id j4-20020a4ab1c4000000b00546da24333dmr247093ooo.0.1682026463144; Thu, 20 Apr 2023 14:34:23 -0700 (PDT) List-Id: Technical discussions relating to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-hackers List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-hackers@freebsd.org MIME-Version: 1.0 Received: by 2002:ac9:5897:0:b0:49c:b071:b1e3 with HTTP; Thu, 20 Apr 2023 14:34:22 -0700 (PDT) In-Reply-To: References: From: Mateusz Guzik Date: Thu, 20 Apr 2023 23:34:22 +0200 Message-ID: Subject: Re: ULE process to resolution To: Jeff Roberson Cc: freebsd-hackers@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Spamd-Result: default: False [-1.62 / 15.00]; URI_HIDDEN_PATH(1.00)[https://people.freebsd.org/~mjg/.junk/cpuburner2.c]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; NEURAL_SPAM_SHORT(0.38)[0.377]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20221208]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36]; MIME_GOOD(-0.10)[text/plain]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-hackers@freebsd.org]; ARC_NA(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; MID_RHS_MATCH_FROMTLD(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; FREEMAIL_FROM(0.00)[gmail.com]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::c29:from]; DKIM_TRACE(0.00)[gmail.com:+]; FROM_EQ_ENVFROM(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; FREEMAIL_ENVFROM(0.00)[gmail.com]; MIME_TRACE(0.00)[0:+]; MLMMJ_DEST(0.00)[freebsd-hackers@freebsd.org] X-Rspamd-Queue-Id: 4Q2WBm4kJsz3mHx X-Spamd-Bar: - X-ThisMailContainsUnwantedMimeParts: N On 4/4/23, Mateusz Guzik wrote: > Hello, > > On 3/31/23, Jeff Roberson wrote: >> As I read these threads I can state with a high degree of confidence that >> many of these tests worked with superior results with ULE at one time. >> It may be that tradeoffs have changed or exposed weaknesses, it may also >> be that it's simply been broken over time. I see a large number of >> commits intended to address point issues and wonder whether we adequately >> explored the consquences. Indeed I see solutions involving tunables >> proposed here that will definitively break other cases. >> > > One of the reporters claims the bug they complain about was there > since early days. This made me curious how many problems reproduce on > something like 7.1 (dated 2009), to that end I created an 8 core vm > which I ran of bunch of tests on in addition to main. All 3 problems > reported below reproduced there, no X testing though :) > > Bugs (one not reported in the other thread): > 1. threads walking around the machine when spending little time off > cpu, all while the machine is otherwise idle > > The problem with this on bare metal is that the victim cpu may be > partially powered off, so now there is latency stemming from poking it > back up, whatever other migration cost aside. > > I noticed this few years back when looking at postgres -- both the > server and pgbench would walk around everywhere, reducing perf. I > checked this reproduces on fresh main. The box at hand as 2 sockets * > 10 cores * 2 threads. > > I *suspect* this is adequately modeled with a microbenchmark > https://github.com/antonblanchard/will-it-scale/ named > context_switch1_processes -- it too experiences all-machine walk > unless explicitly bound (pass -n to *not* bind it). I verified they > walk all around on 7.1 as well, but I don't know if postgres also > would. > > how to bench: > su - postgres > /usr/local/bin/pg_ctl -D /var/db/postgres/data15 -l logfile start > pgbench -i -s 10 > pgbench -M prepared -S -T 800000 -c 1 -j 1 -P1 postgres > > ... and you are in. > > 2. unfairness when oversubscribing with cpu hogs > > Steve Kargl claims he reported this one numerous times since the early > days of ULE, I confirmed it was a problem on 7.1 and is a problem > today. > > Say an 8 core vm (with making sure these are cores pinned on the host) > > I'm going to copy paste my other message here: > I wrote a cpu burning program (memset 1 MB in a loop, with enough > iterations to take ~20 seconds on its own). > > I booted an 8 core bhyve vm, where I made sure to cpuset is to 8 distinct > cores. > > The test runs *9* workers, here is a sample run: > [copy] > 4bsd: > 23.18 real 20.81 user 0.00 sys > 23.26 real 20.81 user 0.00 sys > 23.30 real 20.81 user 0.00 sys > 23.34 real 20.82 user 0.00 sys > 23.41 real 20.81 user 0.00 sys > 23.41 real 20.80 user 0.00 sys > 23.42 real 20.80 user 0.00 sys > 23.53 real 20.81 user 0.00 sys > 23.60 real 20.80 user 0.00 sys > 187.31s user 0.02s system 793% cpu 23.606 total > > ule: > 20.67 real 20.04 user 0.00 sys > 20.97 real 20.00 user 0.00 sys > 21.45 real 20.29 user 0.00 sys > 21.51 real 20.22 user 0.00 sys > 22.77 real 20.04 user 0.00 sys > 22.78 real 20.26 user 0.00 sys > 23.42 real 20.04 user 0.00 sys > 24.07 real 20.30 user 0.00 sys > 24.46 real 20.16 user 0.00 sys > 181.41s user 0.07s system 741% cpu 24.465 total > [/paste] > > While ule spends fewer *cycles*, it spends more real time and it is > *probably* bad. > > you can repro with: > https://people.freebsd.org/~mjg/.junk/cpuburner1.c > cc -O0 -o cpuburner1 cpuburner1.c > > and a magic script: > #!/bin/sh > > ins=$1 > > shift > > while [ $ins -ne 0 ]; do > time ./cpuburner1 $1 $2 & > ins=$((ins-1)) > done > > wait > > run like this, pick the second number to take 20-ish seconds on your cpu: > sh burn.sh 1048576 500000 > > 3. threads struggling to get back on cpu against nice -n 20 higs > > This acutely affects buildkernel. > > I once more played around, the bug was already there in 7.1, extending > total time from ~4 minutes to 30. > > The problem is introduced with the machinery to attempt to provide > fairness for pri <= PRI_MAX_BATCH. I verified that with straight up > removing all of it. Then buildikernel managed to finish in sensible > time, but the cpu hogs were overly negatively affected -- little cpu > time and very unfairly distributed between them. Key point though that > this *can* stick to close to base time. > > I had seen the patch from https://reviews.freebsd.org/D15985 , it does > not fix the problem but it does alleviate it to some extent. It is > weirdly hacky and seems to be targeting just the testcase you had > instead of the more general problem. > > I applied it to a 2018-ish tree so that there are no woes from rebasing. > stock: 290.95 real 2048.22 user 247.967 sys > stock+hogs: 883.81 real 2111.34 user 189.42 sys > patched+hogs: 460.84 real 2055.63 user 232.00 sys > > Interestingly stock kernel from that period is less affected by the > general problem, but it is still pretty bad. With the patch things > improve markedly, but there is still ~50% increase in real time which > is way too much for being paired against -n 20. > > https://people.freebsd.org/~mjg/.junk/cpuburner2.c > > magic script: > #!/bin/sh > > workers=$1 > n=$2 > size=$3 > bkw=$4 > > echo workers $workers nice $n buildkernel $bkw > > shift > > while [ $workers -ne 0 ]; do > time nice -n $n ./cpuburner $size & > workers=$((workers-1)) > done > > time make -C /usr/src -ssss -j $bkw buildkernel > /dev/null > > # XXX webdev-style > pkill cpuburner > > wait > > sample use: time sh burn+bk.sh 8 20 1048576 8 > > I figured there would be a regression test suite available, with tests > checking what happens for known cases with possibly contradictory > requirements. Got nothing, instead I found people use hackbench (:S) > or just a workload. > > All that said, I'm buggering off the subject. My interest in it was > limited to the nice problem, since I have pretty good reasons to > suspect this is what is causing pathological total real time instances > for package builds. > Do you still plan to do anything here? 14.0 schedule has been posted and it starts with this: head slush/KBI freeze: April 25, 2023 [... ALPHA builds ...]: TBD (as-needed) stable/14 branch: May 12, 2023 releng/14.0 branch: May 26, 2023 BETA1 build starts: May 26, 2023 iow there is not much time to make any fixes for the release. That said, I had another look at your patch. It aged out of simple forward porting: commit 686bcb5c14aba6e67524be84e125bfdd3514db9e Author: Jeff Roberson Date: Sun Dec 15 21:26:50 2019 +0000 schedlock 4/4 and a follow up fixup: commit 6d3f74a14a83b867c273c6be2599da182a9b9ec7 Author: Mark Johnston Date: Thu Jul 14 10:21:28 2022 -0400 sched_ule: Fix racy loads of pc_curthread which whacked access to data your patch relies on. Not saying this can't be augmented, just that it is extra churn. I also looked into why there is still tons of cpu time for the niced stuff and found the mechanism mostly does not work. Here are some results from FreeBSD 7.1 (2009 vintage) running full time cpu hogs with various nice levels: prio 10 ops 12863 prio 0 ops 12846 prio 20 ops 12794 prio 0 ops 24949 prio 20 ops 13551 prio 0 ops 11327 prio -20 ops 19474 prio 20 ops 7575 As you can see that release had about 33/66 split for the 0 vs 20 case which is alreadyp retty bad and funnily enough it had equal treatment for 0 vs 10 vs 20. Things further changed down the road and on fresh main it looks like this: prio 10 ops 4390 prio 0 ops 4963 prio 20 ops 3941 prio 0 ops 7235 prio 20 ops 6059 prio -20 ops 7225 prio 0 ops 3763 prio 20 ops 2547 as in nice 20 is penalized even less vs 0. tl;dr things were already bad on 7.1. to repro: fetch https://people.freebsd.org/~mjg/.junk/cpuburner-prio.c fetch https://people.freebsd.org/~mjg/.junk/script3.sh cpuset -l 2 sh script3.sh -- Mateusz Guzik From nobody Fri Apr 21 00:38:44 2023 X-Original-To: freebsd-hackers@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 4Q2bHm24klz46qQ9; Fri, 21 Apr 2023 00:39:00 +0000 (UTC) (envelope-from aryeh.friedman@gmail.com) Received: from mail-ed1-x534.google.com (mail-ed1-x534.google.com [IPv6:2a00:1450:4864:20::534]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Q2bHm0LzPz3CqB; Fri, 21 Apr 2023 00:39:00 +0000 (UTC) (envelope-from aryeh.friedman@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-ed1-x534.google.com with SMTP id 4fb4d7f45d1cf-504fce3d7fbso1530647a12.2; Thu, 20 Apr 2023 17:39:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1682037537; x=1684629537; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=NRiPPvPmcDu4oa7SMi8Y5zvyhMXMDjrJOXOlsL5m+Gg=; b=oq4OGWsaSfs0aABBvJnsol2KS5ttNHY25KHElDyL4QFLSRCF0JHR+SRkO3RW5najzM g0DBgMT9oA8gTA0aweq9dt092PpZGs9Z3N2QAkf892xCKjw6R5nttm9ZJgPvF55NNik6 koZWyX0qm7f7qtSCJbVjUxRqgkzBeDzHTgHJsf+jHYoJ2ZaTp7FPljFNTosFKtGoUfYo 3avNkm5i4bUMoPQrgm/NRNgWjiBMT32d+JtxK+AxB1pAOCNxOT9pgIXmiyL3XgFKPGpt 00riEy69sNVqnu23kBqyBIhgJS7BDDuau0EewxHM0i2dn40p6xAb8c7bWCFWOLe5y4Pt N9Rg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1682037537; x=1684629537; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=NRiPPvPmcDu4oa7SMi8Y5zvyhMXMDjrJOXOlsL5m+Gg=; b=Jipl9DoNrEsT0+SMYclHz/AKuBh7aaMVrHnyInmJJ6yhONTyWXgL5DgY0NX3xG6HvB nRt8Aol5Dg6fDMdH/rP4NNw1esmjBn50tz/Y6OlRfi0Od0czyK8UHxIT8dxULbc9F0ct fE1jAJhCruXVN5coG20Bk3DjHT3nibBnG4pLBkqn+X0c80nPLs/lRYDi6obXkgNKY9L0 5P7ufv3nVCkI2ELG8JcNg6dH5E8GJ6Gjp/jR4D5yUxcOb8DIhLgzzC3BTIIVdhBK4rM6 DhjQeucGUry2RyqhUX2Ck+3/5Xhq25nCgoNc9/BwPVm6Iy/r6V+T0Wx1CnBs64LmuZbS nhow== X-Gm-Message-State: AAQBX9depsgBlc/aRfTKVzTcktMMRcBzYZmpBAGgFpC4Yghbr05Z7LX/ mFWiSKjnNmY84ZZCEjjCdryl7QaZyFffPigU8hGCPxLC05U= X-Google-Smtp-Source: AKy350bA3R9WC8Jk0wlLwi84GaYFQeBLBdEgPzHtyB0pDwA4bcHpmy12w1ENNYU3O97X01lxdMKV9C+Lvs+pXEaUaYA= X-Received: by 2002:a05:6402:1395:b0:508:39e3:58b with SMTP id b21-20020a056402139500b0050839e3058bmr3247087edv.35.1682037536478; Thu, 20 Apr 2023 17:38:56 -0700 (PDT) List-Id: Technical discussions relating to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-hackers List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-hackers@freebsd.org MIME-Version: 1.0 References: In-Reply-To: From: Aryeh Friedman Date: Thu, 20 Apr 2023 20:38:44 -0400 Message-ID: Subject: Re: Installing openAI's GPT-2 Ada AI Language Model To: Mario Marietto Cc: FreeBSD Mailing List , FreeBSD Mailing List , Yuri Victorovich Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Rspamd-Queue-Id: 4Q2bHm0LzPz3CqB X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; TAGGED_FROM(0.00)[] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N On Thu, Apr 20, 2023 at 12:24=E2=80=AFPM Mario Marietto wrote: > > try to copy and paste the commands that you have issued on pastebin...i n= eed to understand the scenario After saving the patch from the bug report to PORT/files and running portmaster -P misc/pytourch (brand new machine except for installing portmaster): c/ATen/UfuncCPUKernel_add.cpp.AVX2.cpp.o -c /usr/ports/misc/pytorch/work/.build/aten/src/ATen/UfuncCPUKernel_add.cpp.AV= X2.cpp In file included from /usr/ports/misc/pytorch/work/.build/aten/src/ATen/UfuncCPUKernel_add.cpp.AV= X2.cpp:1: In file included from /usr/ports/misc/pytorch/work/.build/aten/src/ATen/UfuncCPUKernel_add.cpp:3: In file included from /usr/ports/misc/pytorch/work/pytorch-v1.13.1/aten/src/ATen/native/ufunc/add= .h:6: In file included from /usr/ports/misc/pytorch/work/pytorch-v1.13.1/aten/src/ATen/cpu/vec/function= al.h:3: In file included from /usr/ports/misc/pytorch/work/pytorch-v1.13.1/aten/src/ATen/cpu/vec/function= al_base.h:6: In file included from /usr/ports/misc/pytorch/work/pytorch-v1.13.1/aten/src/ATen/cpu/vec/vec.h:6: In file included from /usr/ports/misc/pytorch/work/pytorch-v1.13.1/aten/src/ATen/cpu/vec/vec256/v= ec256.h:12: /usr/ports/misc/pytorch/work/pytorch-v1.13.1/aten/src/ATen/cpu/vec/vec256/v= ec256_bfloat16.h:253:16: error: cannot initialize a parameter of type 'const __m256 (*)(__m256)' with an lvalue of type '__m256 (__m256)': different return type ('const __m256' (vector of 8 'float' values) vs '__m256' (vector of 8 'float' values)) return map(Sleef_acosf8_u10); ^~~~~~~~~~~~~~~~ /usr/ports/misc/pytorch/work/pytorch-v1.13.1/aten/src/ATen/cpu/vec/vec256/v= ec256_bfloat16.h:209:49: note: passing argument to parameter 'vop' here Vectorized map(const __m256 (*const vop)(__m256)) const { ^ /usr/ports/misc/pytorch/work/pytorch-v1.13.1/aten/src/ATen/cpu/vec/vec256/v= ec256_bfloat16.h:256:16: error: cannot initialize a parameter of type 'const __m256 (*)(__m256)' with an lvalue of type '__m256 (__m256)': different return type ('const __m256' (vector of 8 'float' values) vs '__m256' (vector of 8 'float' values)) return map(Sleef_asinf8_u10); ^~~~~~~~~~~~~~~~ /usr/ports/misc/pytorch/work/pytorch-v1.13.1/aten/src/ATen/cpu/vec/vec256/v= ec256_bfloat16.h:209:49: note: passing argument to parameter 'vop' here Vectorized map(const __m256 (*const vop)(__m256)) const { ^ /usr/ports/misc/pytorch/work/pytorch-v1.13.1/aten/src/ATen/cpu/vec/vec256/v= ec256_bfloat16.h:259:16: error: cannot initialize a parameter of type 'const __m256 (*)(__m256)' with an lvalue of type '__m256 (__m256)': different return type ('const __m256' (vector of 8 'float' values) vs '__m256' (vector of 8 'float' values)) return map(Sleef_atanf8_u10); ^~~~~~~~~~~~~~~~ /usr/ports/misc/pytorch/work/pytorch-v1.13.1/aten/src/ATen/cpu/vec/vec256/v= ec256_bfloat16.h:209:49: note: passing argument to parameter 'vop' here Vectorized map(const __m256 (*const vop)(__m256)) const { ^ /usr/ports/misc/pytorch/work/pytorch-v1.13.1/aten/src/ATen/cpu/vec/vec256/v= ec256_bfloat16.h:280:16: error: cannot initialize a parameter of type 'const __m256 (*)(__m256)' with an lvalue of type '__m256 (__m256)': different return type ('const __m256' (vector of 8 'float' values) vs '__m256' (vector of 8 'float' values)) return map(Sleef_erff8_u10); ^~~~~~~~~~~~~~~ /usr/ports/misc/pytorch/work/pytorch-v1.13.1/aten/src/ATen/cpu/vec/vec256/v= ec256_bfloat16.h:209:49: note: passing argument to parameter 'vop' here Vectorized map(const __m256 (*const vop)(__m256)) const { ^ /usr/ports/misc/pytorch/work/pytorch-v1.13.1/aten/src/ATen/cpu/vec/vec256/v= ec256_bfloat16.h:283:16: error: cannot initialize a parameter of type 'const __m256 (*)(__m256)' with an lvalue of type '__m256 (__m256)': different return type ('const __m256' (vector of 8 'float' values) vs '__m256' (vector of 8 'float' values)) return map(Sleef_erfcf8_u15); ^~~~~~~~~~~~~~~~ /usr/ports/misc/pytorch/work/pytorch-v1.13.1/aten/src/ATen/cpu/vec/vec256/v= ec256_bfloat16.h:209:49: note: passing argument to parameter 'vop' here Vectorized map(const __m256 (*const vop)(__m256)) const { ^ /usr/ports/misc/pytorch/work/pytorch-v1.13.1/aten/src/ATen/cpu/vec/vec256/v= ec256_bfloat16.h:300:16: error: cannot initialize a parameter of type 'const __m256 (*)(__m256)' with an lvalue of type '__m256 (__m256)': different return type ('const __m256' (vector of 8 'float' values) vs '__m256' (vector of 8 'float' values)) return map(Sleef_expf8_u10); ^~~~~~~~~~~~~~~ /usr/ports/misc/pytorch/work/pytorch-v1.13.1/aten/src/ATen/cpu/vec/vec256/v= ec256_bfloat16.h:209:49: note: passing argument to parameter 'vop' here Vectorized map(const __m256 (*const vop)(__m256)) const { ^ /usr/ports/misc/pytorch/work/pytorch-v1.13.1/aten/src/ATen/cpu/vec/vec256/v= ec256_bfloat16.h:303:16: error: cannot initialize a parameter of type 'const __m256 (*)(__m256)' with an lvalue of type '__m256 (__m256)': different return type ('const __m256' (vector of 8 'float' values) vs '__m256' (vector of 8 'float' values)) return map(Sleef_expm1f8_u10); ^~~~~~~~~~~~~~~~~ /usr/ports/misc/pytorch/work/pytorch-v1.13.1/aten/src/ATen/cpu/vec/vec256/v= ec256_bfloat16.h:209:49: note: passing argument to parameter 'vop' here Vectorized map(const __m256 (*const vop)(__m256)) const { ^ /usr/ports/misc/pytorch/work/pytorch-v1.13.1/aten/src/ATen/cpu/vec/vec256/v= ec256_bfloat16.h:393:16: error: cannot initialize a parameter of type 'const __m256 (*)(__m256)' with an lvalue of type '__m256 (__m256)': different return type ('const __m256' (vector of 8 'float' values) vs '__m256' (vector of 8 'float' values)) return map(Sleef_logf8_u10); ^~~~~~~~~~~~~~~ /usr/ports/misc/pytorch/work/pytorch-v1.13.1/aten/src/ATen/cpu/vec/vec256/v= ec256_bfloat16.h:209:49: note: passing argument to parameter 'vop' here Vectorized map(const __m256 (*const vop)(__m256)) const { ^ /usr/ports/misc/pytorch/work/pytorch-v1.13.1/aten/src/ATen/cpu/vec/vec256/v= ec256_bfloat16.h:396:16: error: cannot initialize a parameter of type 'const __m256 (*)(__m256)' with an lvalue of type '__m256 (__m256)': different return type ('const __m256' (vector of 8 'float' values) vs '__m256' (vector of 8 'float' values)) return map(Sleef_log2f8_u10); ^~~~~~~~~~~~~~~~ /usr/ports/misc/pytorch/work/pytorch-v1.13.1/aten/src/ATen/cpu/vec/vec256/v= ec256_bfloat16.h:209:49: note: passing argument to parameter 'vop' here Vectorized map(const __m256 (*const vop)(__m256)) const { ^ /usr/ports/misc/pytorch/work/pytorch-v1.13.1/aten/src/ATen/cpu/vec/vec256/v= ec256_bfloat16.h:399:16: error: cannot initialize a parameter of type 'const __m256 (*)(__m256)' with an lvalue of type '__m256 (__m256)': different return type ('const __m256' (vector of 8 'float' values) vs '__m256' (vector of 8 'float' values)) return map(Sleef_log10f8_u10); ^~~~~~~~~~~~~~~~~ /usr/ports/misc/pytorch/work/pytorch-v1.13.1/aten/src/ATen/cpu/vec/vec256/v= ec256_bfloat16.h:209:49: note: passing argument to parameter 'vop' here Vectorized map(const __m256 (*const vop)(__m256)) const { ^ /usr/ports/misc/pytorch/work/pytorch-v1.13.1/aten/src/ATen/cpu/vec/vec256/v= ec256_bfloat16.h:402:16: error: cannot initialize a parameter of type 'const __m256 (*)(__m256)' with an lvalue of type '__m256 (__m256)': different return type ('const __m256' (vector of 8 'float' values) vs '__m256' (vector of 8 'float' values)) return map(Sleef_log1pf8_u10); ^~~~~~~~~~~~~~~~~ /usr/ports/misc/pytorch/work/pytorch-v1.13.1/aten/src/ATen/cpu/vec/vec256/v= ec256_bfloat16.h:209:49: note: passing argument to parameter 'vop' here Vectorized map(const __m256 (*const vop)(__m256)) const { ^ /usr/ports/misc/pytorch/work/pytorch-v1.13.1/aten/src/ATen/cpu/vec/vec256/v= ec256_bfloat16.h:406:16: error: cannot initialize a parameter of type 'const __m256 (*)(__m256)' with an lvalue of type '__m256 (__m256)': different return type ('const __m256' (vector of 8 'float' values) vs '__m256' (vector of 8 'float' values)) return map(Sleef_sinf8_u10); ^~~~~~~~~~~~~~~ /usr/ports/misc/pytorch/work/pytorch-v1.13.1/aten/src/ATen/cpu/vec/vec256/v= ec256_bfloat16.h:209:49: note: passing argument to parameter 'vop' here Vectorized map(const __m256 (*const vop)(__m256)) const { ^ /usr/ports/misc/pytorch/work/pytorch-v1.13.1/aten/src/ATen/cpu/vec/vec256/v= ec256_bfloat16.h:409:16: error: cannot initialize a parameter of type 'const __m256 (*)(__m256)' with an lvalue of type '__m256 (__m256)': different return type ('const __m256' (vector of 8 'float' values) vs '__m256' (vector of 8 'float' values)) return map(Sleef_sinhf8_u10); ^~~~~~~~~~~~~~~~ /usr/ports/misc/pytorch/work/pytorch-v1.13.1/aten/src/ATen/cpu/vec/vec256/v= ec256_bfloat16.h:209:49: note: passing argument to parameter 'vop' here Vectorized map(const __m256 (*const vop)(__m256)) const { ^ /usr/ports/misc/pytorch/work/pytorch-v1.13.1/aten/src/ATen/cpu/vec/vec256/v= ec256_bfloat16.h:412:16: error: cannot initialize a parameter of type 'const __m256 (*)(__m256)' with an lvalue of type '__m256 (__m256)': different return type ('const __m256' (vector of 8 'float' values) vs '__m256' (vector of 8 'float' values)) return map(Sleef_cosf8_u10); ^~~~~~~~~~~~~~~ /usr/ports/misc/pytorch/work/pytorch-v1.13.1/aten/src/ATen/cpu/vec/vec256/v= ec256_bfloat16.h:209:49: note: passing argument to parameter 'vop' here Vectorized map(const __m256 (*const vop)(__m256)) const { ^ /usr/ports/misc/pytorch/work/pytorch-v1.13.1/aten/src/ATen/cpu/vec/vec256/v= ec256_bfloat16.h:415:16: error: cannot initialize a parameter of type 'const __m256 (*)(__m256)' with an lvalue of type '__m256 (__m256)': different return type ('const __m256' (vector of 8 'float' values) vs '__m256' (vector of 8 'float' values)) return map(Sleef_coshf8_u10); ^~~~~~~~~~~~~~~~ /usr/ports/misc/pytorch/work/pytorch-v1.13.1/aten/src/ATen/cpu/vec/vec256/v= ec256_bfloat16.h:209:49: note: passing argument to parameter 'vop' here Vectorized map(const __m256 (*const vop)(__m256)) const { ^ /usr/ports/misc/pytorch/work/pytorch-v1.13.1/aten/src/ATen/cpu/vec/vec256/v= ec256_bfloat16.h:447:16: error: cannot initialize a parameter of type 'const __m256 (*)(__m256)' with an lvalue of type '__m256 (__m256)': different return type ('const __m256' (vector of 8 'float' values) vs '__m256' (vector of 8 'float' values)) return map(Sleef_tanf8_u10); ^~~~~~~~~~~~~~~ /usr/ports/misc/pytorch/work/pytorch-v1.13.1/aten/src/ATen/cpu/vec/vec256/v= ec256_bfloat16.h:209:49: note: passing argument to parameter 'vop' here Vectorized map(const __m256 (*const vop)(__m256)) const { ^ /usr/ports/misc/pytorch/work/pytorch-v1.13.1/aten/src/ATen/cpu/vec/vec256/v= ec256_bfloat16.h:450:16: error: cannot initialize a parameter of type 'const __m256 (*)(__m256)' with an lvalue of type '__m256 (__m256)': different return type ('const __m256' (vector of 8 'float' values) vs '__m256' (vector of 8 'float' values)) return map(Sleef_tanhf8_u10); ^~~~~~~~~~~~~~~~ /usr/ports/misc/pytorch/work/pytorch-v1.13.1/aten/src/ATen/cpu/vec/vec256/v= ec256_bfloat16.h:209:49: note: passing argument to parameter 'vop' here Vectorized map(const __m256 (*const vop)(__m256)) const { ^ /usr/ports/misc/pytorch/work/pytorch-v1.13.1/aten/src/ATen/cpu/vec/vec256/v= ec256_bfloat16.h:460:16: error: cannot initialize a parameter of type 'const __m256 (*)(__m256)' with an lvalue of type '__m256 (__m256)': different return type ('const __m256' (vector of 8 'float' values) vs '__m256' (vector of 8 'float' values)) return map(Sleef_lgammaf8_u10); ^~~~~~~~~~~~~~~~~~ /usr/ports/misc/pytorch/work/pytorch-v1.13.1/aten/src/ATen/cpu/vec/vec256/v= ec256_bfloat16.h:209:49: note: passing argument to parameter 'vop' here Vectorized map(const __m256 (*const vop)(__m256)) const { ^ 18 errors generated. [ 80% 1035/1283] /usr/bin/c++ -DAT_PER_OPERATOR_HEADERS -DCPUINFO_SUPPORTED_PLATFORM=3D0 -DFMT_HEADER_ONLY=3D1 -DHAVE_MALLOC_USABLE_SIZE=3D1 -DHAVE_MMAP=3D1 -DHAVE_SHM_OPEN=3D1 -DHAVE_SHM_UNLINK=3D1 -DMINIZ_DISABLE_ZIP_READER_CRC32_CHECKS -DONNXIFI_ENABLE_EXT=3D1 -DONNX_ML=3D1 -DONNX_NAMESPACE=3Donnx -DUSE_EXTERNAL_MZCRC -D_FILE_OFFSET_BITS=3D64 -Dtorch_cpu_EXPORTS -I/usr/ports/misc/pytorch/work/.build/aten/src -I/usr/ports/misc/pytorch/work/pytorch-v1.13.1/aten/src -I/usr/ports/misc/pytorch/work/.build -I/usr/ports/misc/pytorch/work/pytorch-v1.13.1 -I/usr/ports/misc/pytorch/work/pytorch-v1.13.1/third_party/foxi -I/usr/ports/misc/pytorch/work/.build/third_party/foxi -I/usr/ports/misc/pytorch/work/pytorch-v1.13.1/torch/csrc/api -I/usr/ports/misc/pytorch/work/pytorch-v1.13.1/torch/csrc/api/include -I/usr/ports/misc/pytorch/work/pytorch-v1.13.1/caffe2/aten/src/TH -I/usr/ports/misc/pytorch/work/.build/caffe2/aten/src/TH -I/usr/ports/misc/pytorch/work/.build/caffe2/aten/src -I/usr/ports/misc/pytorch/work/.build/caffe2/../aten/src -I/usr/ports/misc/pytorch/work/pytorch-v1.13.1/torch/csrc -I/usr/ports/misc/pytorch/work/pytorch-v1.13.1/third_party/miniz-2.1.0 -I/usr/ports/misc/pytorch/work/pytorch-v1.13.1/third_party/kineto/libkineto= /include -I/usr/ports/misc/pytorch/work/pytorch-v1.13.1/third_party/kineto/libkineto= /src -I/usr/ports/misc/pytorch/work/pytorch-v1.13.1/aten/../third_party/catch/si= ngle_include -I/usr/ports/misc/pytorch/work/pytorch-v1.13.1/aten/src/ATen/.. -I/usr/ports/misc/pytorch/work/pytorch-v1.13.1/c10/.. -I/usr/ports/misc/pytorch/work/pytorch-v1.13.1/third_party/cpuinfo/include -I/usr/ports/misc/pytorch/work/pytorch-v1.13.1/third_party/FP16/include -I/usr/ports/misc/pytorch/work/pytorch-v1.13.1/third_party/fmt/include -I/usr/ports/misc/pytorch/work/pytorch-v1.13.1/third_party/flatbuffers/incl= ude -isystem /usr/ports/misc/pytorch/work/pytorch-v1.13.1/cmake/../third_party/= eigen -isystem /usr/ports/misc/pytorch/work/pytorch-v1.13.1/caffe2 -O2 -pipe -fstack-protector-strong -isystem /usr/local/include -fno-strict-aliasing -isystem /usr/local/include -Wno-deprecated -fvisibility-inlines-hidden -fopenmp=3Dlibomp -DNDEBUG -DUSE_KINETO -DLIBKINETO_NOCUPTI -DSYMBOLICATE_MOBILE_DEBUG_HANDLE -DEDGE_PROFILER_USE_KINETO -O2 -fPIC -Wno-narrowing -Wall -Wextra -Werror=3Dreturn-type -Werror=3Dnon-virtual-dtor -Wno-missing-field-initializers -Wno-type-limits -Wno-array-bounds -Wno-unknown-pragmas -Wunused-local-typedefs -Wno-unused-parameter -Wno-unused-function -Wno-unused-result -Wno-strict-overflow -Wno-strict-aliasing -Wno-error=3Ddeprecated-declarations -Wvla-extension -Wno-range-loop-analysis -Wno-pass-failed -Wno-error=3Dpedantic -Wno-error=3Dredundant-decls -Wno-error=3Dold-style-cast -Wconstant-conversion -Wno-invalid-partial-specialization -Wno-typedef-redefinition -Wno-unused-private-field -Wno-inconsistent-missing-override -Wno-c++14-extensions -Wno-constexpr-not-const -Wno-missing-braces -Wunused-lambda-capture -Wunused-local-typedef -Qunused-arguments -fcolor-diagnostics -fdiagnostics-color=3Dalways -Wno-unused-but-set-variable -fno-math-errno -fno-trapping-math -Werror=3Dformat -Werror=3Dcast-function-type -DHAVE_AVX512_CPU_DEFINITION -DHAVE_AVX2_CPU_DEFINITION -O2 -pipe -fstack-protector-strong -isystem /usr/local/include -fno-strict-aliasing -isystem /usr/local/include -DNDEBUG -DNDEBUG -std=3Dgnu++14 -fPIC -DTH_HAVE_THREAD -Wall -Wextra -Wno-unused-parameter -Wno-unused-function -Wno-unused-result -Wno-missing-field-initializers -Wno-write-strings -Wno-unknown-pragmas -Wno-type-limits -Wno-array-bounds -Wno-sign-compare -Wno-strict-overflow -Wno-strict-aliasing -Wno-error=3Ddeprecated-declarations -Wno-missing-braces -Wno-range-loop-analysis -fvisibility=3Dhidden -O2 -fopenmp=3Dlibomp -DCAFFE2_BUILD_MAIN_LIB -pthread -MD -MT caffe2/CMakeFiles/torch_cpu.dir/__/torch/csrc/api/src/serialize/input-archi= ve.cpp.o -MF caffe2/CMakeFiles/torch_cpu.dir/__/torch/csrc/api/src/serialize/input-a= rchive.cpp.o.d -o caffe2/CMakeFiles/torch_cpu.dir/__/torch/csrc/api/src/serialize/input-ar= chive.cpp.o -c /usr/ports/misc/pytorch/work/pytorch-v1.13.1/torch/csrc/api/src/serializ= e/input-archive.cpp [ 80% 1035/1283] /usr/bin/c++ -DAT_PER_OPERATOR_HEADERS -DCPUINFO_SUPPORTED_PLATFORM=3D0 -DFMT_HEADER_ONLY=3D1 -DHAVE_MALLOC_USABLE_SIZE=3D1 -DHAVE_MMAP=3D1 -DHAVE_SHM_OPEN=3D1 -DHAVE_SHM_UNLINK=3D1 -DMINIZ_DISABLE_ZIP_READER_CRC32_CHECKS -DONNXIFI_ENABLE_EXT=3D1 -DONNX_ML=3D1 -DONNX_NAMESPACE=3Donnx -DUSE_EXTERNAL_MZCRC -D_FILE_OFFSET_BITS=3D64 -Dtorch_cpu_EXPORTS -I/usr/ports/misc/pytorch/work/.build/aten/src -I/usr/ports/misc/pytorch/work/pytorch-v1.13.1/aten/src -I/usr/ports/misc/pytorch/work/.build -I/usr/ports/misc/pytorch/work/pytorch-v1.13.1 -I/usr/ports/misc/pytorch/work/pytorch-v1.13.1/third_party/foxi -I/usr/ports/misc/pytorch/work/.build/third_party/foxi -I/usr/ports/misc/pytorch/work/pytorch-v1.13.1/torch/csrc/api -I/usr/ports/misc/pytorch/work/pytorch-v1.13.1/torch/csrc/api/include -I/usr/ports/misc/pytorch/work/pytorch-v1.13.1/caffe2/aten/src/TH -I/usr/ports/misc/pytorch/work/.build/caffe2/aten/src/TH -I/usr/ports/misc/pytorch/work/.build/caffe2/aten/src -I/usr/ports/misc/pytorch/work/.build/caffe2/../aten/src -I/usr/ports/misc/pytorch/work/pytorch-v1.13.1/torch/csrc -I/usr/ports/misc/pytorch/work/pytorch-v1.13.1/third_party/miniz-2.1.0 -I/usr/ports/misc/pytorch/work/pytorch-v1.13.1/third_party/kineto/libkineto= /include -I/usr/ports/misc/pytorch/work/pytorch-v1.13.1/third_party/kineto/libkineto= /src -I/usr/ports/misc/pytorch/work/pytorch-v1.13.1/aten/../third_party/catch/si= ngle_include -I/usr/ports/misc/pytorch/work/pytorch-v1.13.1/aten/src/ATen/.. -I/usr/ports/misc/pytorch/work/pytorch-v1.13.1/c10/.. -I/usr/ports/misc/pytorch/work/pytorch-v1.13.1/third_party/cpuinfo/include -I/usr/ports/misc/pytorch/work/pytorch-v1.13.1/third_party/FP16/include -I/usr/ports/misc/pytorch/work/pytorch-v1.13.1/third_party/fmt/include -I/usr/ports/misc/pytorch/work/pytorch-v1.13.1/third_party/flatbuffers/incl= ude -isystem /usr/ports/misc/pytorch/work/pytorch-v1.13.1/cmake/../third_party/= eigen -isystem /usr/ports/misc/pytorch/work/pytorch-v1.13.1/caffe2 -O2 -pipe -fstack-protector-strong -isystem /usr/local/include -fno-strict-aliasing -isystem /usr/local/include -Wno-deprecated -fvisibility-inlines-hidden -fopenmp=3Dlibomp -DNDEBUG -DUSE_KINETO -DLIBKINETO_NOCUPTI -DSYMBOLICATE_MOBILE_DEBUG_HANDLE -DEDGE_PROFILER_USE_KINETO -O2 -fPIC -Wno-narrowing -Wall -Wextra -Werror=3Dreturn-type -Werror=3Dnon-virtual-dtor -Wno-missing-field-initializers -Wno-type-limits -Wno-array-bounds -Wno-unknown-pragmas -Wunused-local-typedefs -Wno-unused-parameter -Wno-unused-function -Wno-unused-result -Wno-strict-overflow -Wno-strict-aliasing -Wno-error=3Ddeprecated-declarations -Wvla-extension -Wno-range-loop-analysis -Wno-pass-failed -Wno-error=3Dpedantic -Wno-error=3Dredundant-decls -Wno-error=3Dold-style-cast -Wconstant-conversion -Wno-invalid-partial-specialization -Wno-typedef-redefinition -Wno-unused-private-field -Wno-inconsistent-missing-override -Wno-c++14-extensions -Wno-constexpr-not-const -Wno-missing-braces -Wunused-lambda-capture -Wunused-local-typedef -Qunused-arguments -fcolor-diagnostics -fdiagnostics-color=3Dalways -Wno-unused-but-set-variable -fno-math-errno -fno-trapping-math -Werror=3Dformat -Werror=3Dcast-function-type -DHAVE_AVX512_CPU_DEFINITION -DHAVE_AVX2_CPU_DEFINITION -O2 -pipe -fstack-protector-strong -isystem /usr/local/include -fno-strict-aliasing -isystem /usr/local/include -DNDEBUG -DNDEBUG -std=3Dgnu++14 -fPIC -DTH_HAVE_THREAD -Wall -Wextra -Wno-unused-parameter -Wno-unused-function -Wno-unused-result -Wno-missing-field-initializers -Wno-write-strings -Wno-unknown-pragmas -Wno-type-limits -Wno-array-bounds -Wno-sign-compare -Wno-strict-overflow -Wno-strict-aliasing -Wno-error=3Ddeprecated-declarations -Wno-missing-braces -Wno-range-loop-analysis -fvisibility=3Dhidden -O2 -fopenmp=3Dlibomp -DCAFFE2_BUILD_MAIN_LIB -pthread -MD -MT caffe2/CMakeFiles/torch_cpu.dir/__/torch/csrc/api/src/serialize/output-arch= ive.cpp.o -MF caffe2/CMakeFiles/torch_cpu.dir/__/torch/csrc/api/src/serialize/output-= archive.cpp.o.d -o caffe2/CMakeFiles/torch_cpu.dir/__/torch/csrc/api/src/serialize/output-a= rchive.cpp.o -c /usr/ports/misc/pytorch/work/pytorch-v1.13.1/torch/csrc/api/src/serializ= e/output-archive.cpp ninja: build stopped: subcommand failed. =3D=3D=3D> Compilation failed unexpectedly. Try to set MAKE_JOBS_UNSAFE=3Dyes and rebuild before reporting the failure = to the maintainer. *** Error code 1 Stop. make: stopped in /usr/ports/misc/pytorch > > Il gio 20 apr 2023, 17:51 Aryeh Friedman ha sc= ritto: >> >> On Thu, Apr 20, 2023 at 7:52=E2=80=AFAM Thierry Thomas wrote: >> > >> > Le jeu. 20 avr. 23 =C3=A0 12:53:05 +0200, Aryeh Friedman >> > =C3=A9crivait : >> > >> > > Running without GPU (for now) on a bhyve vm (3 CPU, 2 GB RAM and 100 >> > > GB of disk) which I intend for determining if it is worse going out >> > > and getting the hardware to do GPU. The problem I had was getting >> > > pytorch to work since it appears I have to build it from source and = it >> > > blows up in that build. >> > >> > Have you seen >> > ? >> >> This seems to be true for all OS's I guess I will have to find an >> intel machine... this is as bad as the motivation that led me to do >> petitecloud in the first place (openstack not running on AMD period). >> Is there just no way to run a ANN in pytorch data format in any other >> way that is not python (like Java?!!?) note the tensorflow port >> required pytorch >> >> >> -- >> Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org >> --=20 Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org From nobody Fri Apr 21 10:18:45 2023 X-Original-To: freebsd-hackers@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 4Q2r9S392xz46D44; Fri, 21 Apr 2023 10:19:24 +0000 (UTC) (envelope-from marietto2008@gmail.com) Received: from mail-yw1-x1129.google.com (mail-yw1-x1129.google.com [IPv6:2607:f8b0:4864:20::1129]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Q2r9R2DlLz3R2Q; Fri, 21 Apr 2023 10:19:23 +0000 (UTC) (envelope-from marietto2008@gmail.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20221208 header.b=kC6TNbbV; spf=pass (mx1.freebsd.org: domain of marietto2008@gmail.com designates 2607:f8b0:4864:20::1129 as permitted sender) smtp.mailfrom=marietto2008@gmail.com; dmarc=pass (policy=none) header.from=gmail.com Received: by mail-yw1-x1129.google.com with SMTP id 00721157ae682-54fb8a8a597so16820707b3.0; Fri, 21 Apr 2023 03:19:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1682072362; x=1684664362; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=b1apWy1xDfp8aISm7dYP4tpfNaXVO/iFXq72a5ysgZQ=; b=kC6TNbbVQkaat7N0BLZVh1mTVww1/Yd0sSd970HTdns9lU5j+OweIgKWgyEbuWbOnC 775+PhjWfgb2FXC8RxksL+wIRXWlykJ9yCLWxzszbX0zCv1sfgftx0FNj+mx6oW9IaYq LitVVrACZJbJ5WjMi8Uk+ivfooKVGz56JAPrgfgj0YKauA5zufiDIKsO0lCGuOmiAi6c c38p9xNqoXC3bAi9t2i8t3VaS9N1XUrSMyKK+rSTl8925rHjQeTl0rgdKznHDDT2UK6p twLlPulQMmydGfi46Cux1HqlUwp6HYLnzF9/RFcr+3odGW7TBUXvctlFxE45iJKwgNjQ 6Xnw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1682072362; x=1684664362; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=b1apWy1xDfp8aISm7dYP4tpfNaXVO/iFXq72a5ysgZQ=; b=f5QLb2bXd+rQD32GZZ2QCrp2rabJOisOM5XMR/EY9PAPlrsC7sOdM/XY1HQveXyRbA gwaIa/Ch3Zn3x62xqlBIH/4T4oA9qPBwyyxmlQV5Eogar2PUlTaul6LrPkcvulKbl/xh qIJZhQj4truB6kXbOM7G7reIknWm6BtZTPc0bKAZAbeGp1FP1a31OF8fxDkBooHLtCNF PP20doaaJ34y/hA15kRVyeJA5ag+dUvPey9M9GLwkGJANYOU2/MZToZQaqsq7//FU5J9 rFNTcLlspeUSY6HN7A6NjoN2MjKf5eDoIMDF0SZgcnaG0FjVdrz183qlb9f8deqSoVcf 5+TA== X-Gm-Message-State: AAQBX9fYViD4xZ4ZLqO1/3YpNjQm+QVsIglVOfplTfpeKp0Fb2ZtNL3M OsHwT3c+qhHvU8dcXaxuUl1RgsTnrUDiPX3MGS2dLvnfz1YvsA== X-Google-Smtp-Source: AKy350ZjEK4o1y1lkt/gU3KzI4x/vOyoJu2wX2aVOTQ7jw2ZpUe3SNOTya4GCaNJxU2a4UrXW5vI3wqpcluHTlgj0HA= X-Received: by 2002:a81:ab46:0:b0:54f:b6b3:b5e5 with SMTP id d6-20020a81ab46000000b0054fb6b3b5e5mr1571335ywk.18.1682072361893; Fri, 21 Apr 2023 03:19:21 -0700 (PDT) List-Id: Technical discussions relating to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-hackers List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-hackers@freebsd.org MIME-Version: 1.0 References: In-Reply-To: From: Mario Marietto Date: Fri, 21 Apr 2023 12:18:45 +0200 Message-ID: Subject: Re: Installing openAI's GPT-2 Ada AI Language Model To: Aryeh Friedman Cc: FreeBSD Mailing List , FreeBSD Mailing List , Yuri Victorovich Content-Type: multipart/alternative; boundary="0000000000009e07eb05f9d5fdf2" X-Spamd-Result: default: False [-2.76 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-0.999]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; NEURAL_SPAM_SHORT(0.24)[0.243]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20221208]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; FREEMAIL_FROM(0.00)[gmail.com]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[4]; TAGGED_RCPT(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::1129:from]; TO_MATCH_ENVRCPT_SOME(0.00)[]; ARC_NA(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; DKIM_TRACE(0.00)[gmail.com:+]; TO_DN_ALL(0.00)[]; MID_RHS_MATCH_FROMTLD(0.00)[]; MLMMJ_DEST(0.00)[freebsd-hackers@freebsd.org,freebsd-questions@freebsd.org]; FREEMAIL_TO(0.00)[gmail.com]; RCVD_TLS_LAST(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; MIME_TRACE(0.00)[0:+,1:+,2:~]; RCVD_COUNT_TWO(0.00)[2] X-Rspamd-Queue-Id: 4Q2r9R2DlLz3R2Q X-Spamd-Bar: -- X-ThisMailContainsUnwantedMimeParts: N --0000000000009e07eb05f9d5fdf2 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Can't you install pytorch using the linux miniconda installer like below ? # fetch https://gist.githubusercontent.com/shkhln/40ef290463e78fb2b0000c60f= 4ad797e/raw/f640983249607e38af405c95c457ce4afc85c608/uvm_ioctl_override.c # /compat/ubuntu/bin/gcc --sysroot=3D/compat/ubuntu -m64 -std=3Dc99 -Wall -ldl -fPIC -shared -o dummy-uvm.so uvm_ioctl_override.c # pkg install linux-miniconda-installer # miniconda-installer # bash # source /home/marietto/miniconda3/etc/profile.d/conda.sh # conda activate (base) # conda activate pytorch On Fri, Apr 21, 2023 at 2:38=E2=80=AFAM Aryeh Friedman wrote: > On Thu, Apr 20, 2023 at 12:24=E2=80=AFPM Mario Marietto > wrote: > > > > try to copy and paste the commands that you have issued on pastebin...i > need to understand the scenario > > After saving the patch from the bug report to PORT/files and running > portmaster -P misc/pytourch (brand new machine except for installing > portmaster): > > c/ATen/UfuncCPUKernel_add.cpp.AVX2.cpp.o -c > > /usr/ports/misc/pytorch/work/.build/aten/src/ATen/UfuncCPUKernel_add.cpp.= AVX2.cpp > In file included from > > /usr/ports/misc/pytorch/work/.build/aten/src/ATen/UfuncCPUKernel_add.cpp.= AVX2.cpp:1: > In file included from > /usr/ports/misc/pytorch/work/.build/aten/src/ATen/UfuncCPUKernel_add.cpp:= 3: > In file included from > > /usr/ports/misc/pytorch/work/pytorch-v1.13.1/aten/src/ATen/native/ufunc/a= dd.h:6: > In file included from > > /usr/ports/misc/pytorch/work/pytorch-v1.13.1/aten/src/ATen/cpu/vec/functi= onal.h:3: > In file included from > > /usr/ports/misc/pytorch/work/pytorch-v1.13.1/aten/src/ATen/cpu/vec/functi= onal_base.h:6: > In file included from > /usr/ports/misc/pytorch/work/pytorch-v1.13.1/aten/src/ATen/cpu/vec/vec.h:= 6: > In file included from > > /usr/ports/misc/pytorch/work/pytorch-v1.13.1/aten/src/ATen/cpu/vec/vec256= /vec256.h:12: > > /usr/ports/misc/pytorch/work/pytorch-v1.13.1/aten/src/ATen/cpu/vec/vec256= /vec256_bfloat16.h:253:16: > error: cannot initialize a parameter of type 'const __m256 > (*)(__m256)' with an lvalue of type '__m256 (__m256)': different > return type ('const __m256' (vector of 8 'float' values) vs '__m256' > (vector of 8 'float' values)) > return map(Sleef_acosf8_u10); > ^~~~~~~~~~~~~~~~ > > /usr/ports/misc/pytorch/work/pytorch-v1.13.1/aten/src/ATen/cpu/vec/vec256= /vec256_bfloat16.h:209:49: > note: passing argument to parameter 'vop' here > Vectorized map(const __m256 (*const vop)(__m256)) const { > ^ > > /usr/ports/misc/pytorch/work/pytorch-v1.13.1/aten/src/ATen/cpu/vec/vec256= /vec256_bfloat16.h:256:16: > error: cannot initialize a parameter of type 'const __m256 > (*)(__m256)' with an lvalue of type '__m256 (__m256)': different > return type ('const __m256' (vector of 8 'float' values) vs '__m256' > (vector of 8 'float' values)) > return map(Sleef_asinf8_u10); > ^~~~~~~~~~~~~~~~ > > /usr/ports/misc/pytorch/work/pytorch-v1.13.1/aten/src/ATen/cpu/vec/vec256= /vec256_bfloat16.h:209:49: > note: passing argument to parameter 'vop' here > Vectorized map(const __m256 (*const vop)(__m256)) const { > ^ > > /usr/ports/misc/pytorch/work/pytorch-v1.13.1/aten/src/ATen/cpu/vec/vec256= /vec256_bfloat16.h:259:16: > error: cannot initialize a parameter of type 'const __m256 > (*)(__m256)' with an lvalue of type '__m256 (__m256)': different > return type ('const __m256' (vector of 8 'float' values) vs '__m256' > (vector of 8 'float' values)) > return map(Sleef_atanf8_u10); > ^~~~~~~~~~~~~~~~ > > /usr/ports/misc/pytorch/work/pytorch-v1.13.1/aten/src/ATen/cpu/vec/vec256= /vec256_bfloat16.h:209:49: > note: passing argument to parameter 'vop' here > Vectorized map(const __m256 (*const vop)(__m256)) const { > ^ > > /usr/ports/misc/pytorch/work/pytorch-v1.13.1/aten/src/ATen/cpu/vec/vec256= /vec256_bfloat16.h:280:16: > error: cannot initialize a parameter of type 'const __m256 > (*)(__m256)' with an lvalue of type '__m256 (__m256)': different > return type ('const __m256' (vector of 8 'float' values) vs '__m256' > (vector of 8 'float' values)) > return map(Sleef_erff8_u10); > ^~~~~~~~~~~~~~~ > > /usr/ports/misc/pytorch/work/pytorch-v1.13.1/aten/src/ATen/cpu/vec/vec256= /vec256_bfloat16.h:209:49: > note: passing argument to parameter 'vop' here > Vectorized map(const __m256 (*const vop)(__m256)) const { > ^ > > /usr/ports/misc/pytorch/work/pytorch-v1.13.1/aten/src/ATen/cpu/vec/vec256= /vec256_bfloat16.h:283:16: > error: cannot initialize a parameter of type 'const __m256 > (*)(__m256)' with an lvalue of type '__m256 (__m256)': different > return type ('const __m256' (vector of 8 'float' values) vs '__m256' > (vector of 8 'float' values)) > return map(Sleef_erfcf8_u15); > ^~~~~~~~~~~~~~~~ > > /usr/ports/misc/pytorch/work/pytorch-v1.13.1/aten/src/ATen/cpu/vec/vec256= /vec256_bfloat16.h:209:49: > note: passing argument to parameter 'vop' here > Vectorized map(const __m256 (*const vop)(__m256)) const { > ^ > > /usr/ports/misc/pytorch/work/pytorch-v1.13.1/aten/src/ATen/cpu/vec/vec256= /vec256_bfloat16.h:300:16: > error: cannot initialize a parameter of type 'const __m256 > (*)(__m256)' with an lvalue of type '__m256 (__m256)': different > return type ('const __m256' (vector of 8 'float' values) vs '__m256' > (vector of 8 'float' values)) > return map(Sleef_expf8_u10); > ^~~~~~~~~~~~~~~ > > /usr/ports/misc/pytorch/work/pytorch-v1.13.1/aten/src/ATen/cpu/vec/vec256= /vec256_bfloat16.h:209:49: > note: passing argument to parameter 'vop' here > Vectorized map(const __m256 (*const vop)(__m256)) const { > ^ > > /usr/ports/misc/pytorch/work/pytorch-v1.13.1/aten/src/ATen/cpu/vec/vec256= /vec256_bfloat16.h:303:16: > error: cannot initialize a parameter of type 'const __m256 > (*)(__m256)' with an lvalue of type '__m256 (__m256)': different > return type ('const __m256' (vector of 8 'float' values) vs '__m256' > (vector of 8 'float' values)) > return map(Sleef_expm1f8_u10); > ^~~~~~~~~~~~~~~~~ > > /usr/ports/misc/pytorch/work/pytorch-v1.13.1/aten/src/ATen/cpu/vec/vec256= /vec256_bfloat16.h:209:49: > note: passing argument to parameter 'vop' here > Vectorized map(const __m256 (*const vop)(__m256)) const { > ^ > > /usr/ports/misc/pytorch/work/pytorch-v1.13.1/aten/src/ATen/cpu/vec/vec256= /vec256_bfloat16.h:393:16: > error: cannot initialize a parameter of type 'const __m256 > (*)(__m256)' with an lvalue of type '__m256 (__m256)': different > return type ('const __m256' (vector of 8 'float' values) vs '__m256' > (vector of 8 'float' values)) > return map(Sleef_logf8_u10); > ^~~~~~~~~~~~~~~ > > /usr/ports/misc/pytorch/work/pytorch-v1.13.1/aten/src/ATen/cpu/vec/vec256= /vec256_bfloat16.h:209:49: > note: passing argument to parameter 'vop' here > Vectorized map(const __m256 (*const vop)(__m256)) const { > ^ > > /usr/ports/misc/pytorch/work/pytorch-v1.13.1/aten/src/ATen/cpu/vec/vec256= /vec256_bfloat16.h:396:16: > error: cannot initialize a parameter of type 'const __m256 > (*)(__m256)' with an lvalue of type '__m256 (__m256)': different > return type ('const __m256' (vector of 8 'float' values) vs '__m256' > (vector of 8 'float' values)) > return map(Sleef_log2f8_u10); > ^~~~~~~~~~~~~~~~ > > /usr/ports/misc/pytorch/work/pytorch-v1.13.1/aten/src/ATen/cpu/vec/vec256= /vec256_bfloat16.h:209:49: > note: passing argument to parameter 'vop' here > Vectorized map(const __m256 (*const vop)(__m256)) const { > ^ > > /usr/ports/misc/pytorch/work/pytorch-v1.13.1/aten/src/ATen/cpu/vec/vec256= /vec256_bfloat16.h:399:16: > error: cannot initialize a parameter of type 'const __m256 > (*)(__m256)' with an lvalue of type '__m256 (__m256)': different > return type ('const __m256' (vector of 8 'float' values) vs '__m256' > (vector of 8 'float' values)) > return map(Sleef_log10f8_u10); > ^~~~~~~~~~~~~~~~~ > > /usr/ports/misc/pytorch/work/pytorch-v1.13.1/aten/src/ATen/cpu/vec/vec256= /vec256_bfloat16.h:209:49: > note: passing argument to parameter 'vop' here > Vectorized map(const __m256 (*const vop)(__m256)) const { > ^ > > /usr/ports/misc/pytorch/work/pytorch-v1.13.1/aten/src/ATen/cpu/vec/vec256= /vec256_bfloat16.h:402:16: > error: cannot initialize a parameter of type 'const __m256 > (*)(__m256)' with an lvalue of type '__m256 (__m256)': different > return type ('const __m256' (vector of 8 'float' values) vs '__m256' > (vector of 8 'float' values)) > return map(Sleef_log1pf8_u10); > ^~~~~~~~~~~~~~~~~ > > /usr/ports/misc/pytorch/work/pytorch-v1.13.1/aten/src/ATen/cpu/vec/vec256= /vec256_bfloat16.h:209:49: > note: passing argument to parameter 'vop' here > Vectorized map(const __m256 (*const vop)(__m256)) const { > ^ > > /usr/ports/misc/pytorch/work/pytorch-v1.13.1/aten/src/ATen/cpu/vec/vec256= /vec256_bfloat16.h:406:16: > error: cannot initialize a parameter of type 'const __m256 > (*)(__m256)' with an lvalue of type '__m256 (__m256)': different > return type ('const __m256' (vector of 8 'float' values) vs '__m256' > (vector of 8 'float' values)) > return map(Sleef_sinf8_u10); > ^~~~~~~~~~~~~~~ > > /usr/ports/misc/pytorch/work/pytorch-v1.13.1/aten/src/ATen/cpu/vec/vec256= /vec256_bfloat16.h:209:49: > note: passing argument to parameter 'vop' here > Vectorized map(const __m256 (*const vop)(__m256)) const { > ^ > > /usr/ports/misc/pytorch/work/pytorch-v1.13.1/aten/src/ATen/cpu/vec/vec256= /vec256_bfloat16.h:409:16: > error: cannot initialize a parameter of type 'const __m256 > (*)(__m256)' with an lvalue of type '__m256 (__m256)': different > return type ('const __m256' (vector of 8 'float' values) vs '__m256' > (vector of 8 'float' values)) > return map(Sleef_sinhf8_u10); > ^~~~~~~~~~~~~~~~ > > /usr/ports/misc/pytorch/work/pytorch-v1.13.1/aten/src/ATen/cpu/vec/vec256= /vec256_bfloat16.h:209:49: > note: passing argument to parameter 'vop' here > Vectorized map(const __m256 (*const vop)(__m256)) const { > ^ > > /usr/ports/misc/pytorch/work/pytorch-v1.13.1/aten/src/ATen/cpu/vec/vec256= /vec256_bfloat16.h:412:16: > error: cannot initialize a parameter of type 'const __m256 > (*)(__m256)' with an lvalue of type '__m256 (__m256)': different > return type ('const __m256' (vector of 8 'float' values) vs '__m256' > (vector of 8 'float' values)) > return map(Sleef_cosf8_u10); > ^~~~~~~~~~~~~~~ > > /usr/ports/misc/pytorch/work/pytorch-v1.13.1/aten/src/ATen/cpu/vec/vec256= /vec256_bfloat16.h:209:49: > note: passing argument to parameter 'vop' here > Vectorized map(const __m256 (*const vop)(__m256)) const { > ^ > > /usr/ports/misc/pytorch/work/pytorch-v1.13.1/aten/src/ATen/cpu/vec/vec256= /vec256_bfloat16.h:415:16: > error: cannot initialize a parameter of type 'const __m256 > (*)(__m256)' with an lvalue of type '__m256 (__m256)': different > return type ('const __m256' (vector of 8 'float' values) vs '__m256' > (vector of 8 'float' values)) > return map(Sleef_coshf8_u10); > ^~~~~~~~~~~~~~~~ > > /usr/ports/misc/pytorch/work/pytorch-v1.13.1/aten/src/ATen/cpu/vec/vec256= /vec256_bfloat16.h:209:49: > note: passing argument to parameter 'vop' here > Vectorized map(const __m256 (*const vop)(__m256)) const { > ^ > > /usr/ports/misc/pytorch/work/pytorch-v1.13.1/aten/src/ATen/cpu/vec/vec256= /vec256_bfloat16.h:447:16: > error: cannot initialize a parameter of type 'const __m256 > (*)(__m256)' with an lvalue of type '__m256 (__m256)': different > return type ('const __m256' (vector of 8 'float' values) vs '__m256' > (vector of 8 'float' values)) > return map(Sleef_tanf8_u10); > ^~~~~~~~~~~~~~~ > > /usr/ports/misc/pytorch/work/pytorch-v1.13.1/aten/src/ATen/cpu/vec/vec256= /vec256_bfloat16.h:209:49: > note: passing argument to parameter 'vop' here > Vectorized map(const __m256 (*const vop)(__m256)) const { > ^ > > /usr/ports/misc/pytorch/work/pytorch-v1.13.1/aten/src/ATen/cpu/vec/vec256= /vec256_bfloat16.h:450:16: > error: cannot initialize a parameter of type 'const __m256 > (*)(__m256)' with an lvalue of type '__m256 (__m256)': different > return type ('const __m256' (vector of 8 'float' values) vs '__m256' > (vector of 8 'float' values)) > return map(Sleef_tanhf8_u10); > ^~~~~~~~~~~~~~~~ > > /usr/ports/misc/pytorch/work/pytorch-v1.13.1/aten/src/ATen/cpu/vec/vec256= /vec256_bfloat16.h:209:49: > note: passing argument to parameter 'vop' here > Vectorized map(const __m256 (*const vop)(__m256)) const { > ^ > > /usr/ports/misc/pytorch/work/pytorch-v1.13.1/aten/src/ATen/cpu/vec/vec256= /vec256_bfloat16.h:460:16: > error: cannot initialize a parameter of type 'const __m256 > (*)(__m256)' with an lvalue of type '__m256 (__m256)': different > return type ('const __m256' (vector of 8 'float' values) vs '__m256' > (vector of 8 'float' values)) > return map(Sleef_lgammaf8_u10); > ^~~~~~~~~~~~~~~~~~ > > /usr/ports/misc/pytorch/work/pytorch-v1.13.1/aten/src/ATen/cpu/vec/vec256= /vec256_bfloat16.h:209:49: > note: passing argument to parameter 'vop' here > Vectorized map(const __m256 (*const vop)(__m256)) const { > ^ > 18 errors generated. > [ 80% 1035/1283] /usr/bin/c++ -DAT_PER_OPERATOR_HEADERS > -DCPUINFO_SUPPORTED_PLATFORM=3D0 -DFMT_HEADER_ONLY=3D1 > -DHAVE_MALLOC_USABLE_SIZE=3D1 -DHAVE_MMAP=3D1 -DHAVE_SHM_OPEN=3D1 > -DHAVE_SHM_UNLINK=3D1 -DMINIZ_DISABLE_ZIP_READER_CRC32_CHECKS > -DONNXIFI_ENABLE_EXT=3D1 -DONNX_ML=3D1 -DONNX_NAMESPACE=3Donnx > -DUSE_EXTERNAL_MZCRC -D_FILE_OFFSET_BITS=3D64 -Dtorch_cpu_EXPORTS > -I/usr/ports/misc/pytorch/work/.build/aten/src > -I/usr/ports/misc/pytorch/work/pytorch-v1.13.1/aten/src > -I/usr/ports/misc/pytorch/work/.build > -I/usr/ports/misc/pytorch/work/pytorch-v1.13.1 > -I/usr/ports/misc/pytorch/work/pytorch-v1.13.1/third_party/foxi > -I/usr/ports/misc/pytorch/work/.build/third_party/foxi > -I/usr/ports/misc/pytorch/work/pytorch-v1.13.1/torch/csrc/api > -I/usr/ports/misc/pytorch/work/pytorch-v1.13.1/torch/csrc/api/include > -I/usr/ports/misc/pytorch/work/pytorch-v1.13.1/caffe2/aten/src/TH > -I/usr/ports/misc/pytorch/work/.build/caffe2/aten/src/TH > -I/usr/ports/misc/pytorch/work/.build/caffe2/aten/src > -I/usr/ports/misc/pytorch/work/.build/caffe2/../aten/src > -I/usr/ports/misc/pytorch/work/pytorch-v1.13.1/torch/csrc > -I/usr/ports/misc/pytorch/work/pytorch-v1.13.1/third_party/miniz-2.1.0 > > -I/usr/ports/misc/pytorch/work/pytorch-v1.13.1/third_party/kineto/libkine= to/include > > -I/usr/ports/misc/pytorch/work/pytorch-v1.13.1/third_party/kineto/libkine= to/src > > -I/usr/ports/misc/pytorch/work/pytorch-v1.13.1/aten/../third_party/catch/= single_include > -I/usr/ports/misc/pytorch/work/pytorch-v1.13.1/aten/src/ATen/.. > -I/usr/ports/misc/pytorch/work/pytorch-v1.13.1/c10/.. > -I/usr/ports/misc/pytorch/work/pytorch-v1.13.1/third_party/cpuinfo/includ= e > -I/usr/ports/misc/pytorch/work/pytorch-v1.13.1/third_party/FP16/include > -I/usr/ports/misc/pytorch/work/pytorch-v1.13.1/third_party/fmt/include > > -I/usr/ports/misc/pytorch/work/pytorch-v1.13.1/third_party/flatbuffers/in= clude > -isystem > /usr/ports/misc/pytorch/work/pytorch-v1.13.1/cmake/../third_party/eigen > -isystem /usr/ports/misc/pytorch/work/pytorch-v1.13.1/caffe2 -O2 -pipe > -fstack-protector-strong -isystem /usr/local/include > -fno-strict-aliasing -isystem /usr/local/include -Wno-deprecated > -fvisibility-inlines-hidden -fopenmp=3Dlibomp -DNDEBUG -DUSE_KINETO > -DLIBKINETO_NOCUPTI -DSYMBOLICATE_MOBILE_DEBUG_HANDLE > -DEDGE_PROFILER_USE_KINETO -O2 -fPIC -Wno-narrowing -Wall -Wextra > -Werror=3Dreturn-type -Werror=3Dnon-virtual-dtor > -Wno-missing-field-initializers -Wno-type-limits -Wno-array-bounds > -Wno-unknown-pragmas -Wunused-local-typedefs -Wno-unused-parameter > -Wno-unused-function -Wno-unused-result -Wno-strict-overflow > -Wno-strict-aliasing -Wno-error=3Ddeprecated-declarations > -Wvla-extension -Wno-range-loop-analysis -Wno-pass-failed > -Wno-error=3Dpedantic -Wno-error=3Dredundant-decls > -Wno-error=3Dold-style-cast -Wconstant-conversion > -Wno-invalid-partial-specialization -Wno-typedef-redefinition > -Wno-unused-private-field -Wno-inconsistent-missing-override > -Wno-c++14-extensions -Wno-constexpr-not-const -Wno-missing-braces > -Wunused-lambda-capture -Wunused-local-typedef -Qunused-arguments > -fcolor-diagnostics -fdiagnostics-color=3Dalways > -Wno-unused-but-set-variable -fno-math-errno -fno-trapping-math > -Werror=3Dformat -Werror=3Dcast-function-type -DHAVE_AVX512_CPU_DEFINITIO= N > -DHAVE_AVX2_CPU_DEFINITION -O2 -pipe -fstack-protector-strong -isystem > /usr/local/include -fno-strict-aliasing -isystem /usr/local/include > -DNDEBUG -DNDEBUG -std=3Dgnu++14 -fPIC -DTH_HAVE_THREAD -Wall -Wextra > -Wno-unused-parameter -Wno-unused-function -Wno-unused-result > -Wno-missing-field-initializers -Wno-write-strings > -Wno-unknown-pragmas -Wno-type-limits -Wno-array-bounds > -Wno-sign-compare -Wno-strict-overflow -Wno-strict-aliasing > -Wno-error=3Ddeprecated-declarations -Wno-missing-braces > -Wno-range-loop-analysis -fvisibility=3Dhidden -O2 -fopenmp=3Dlibomp > -DCAFFE2_BUILD_MAIN_LIB -pthread -MD -MT > > caffe2/CMakeFiles/torch_cpu.dir/__/torch/csrc/api/src/serialize/input-arc= hive.cpp.o > -MF > caffe2/CMakeFiles/torch_cpu.dir/__/torch/csrc/api/src/serialize/input-arc= hive.cpp.o.d > -o > caffe2/CMakeFiles/torch_cpu.dir/__/torch/csrc/api/src/serialize/input-arc= hive.cpp.o > -c > /usr/ports/misc/pytorch/work/pytorch-v1.13.1/torch/csrc/api/src/serialize= /input-archive.cpp > [ 80% 1035/1283] /usr/bin/c++ -DAT_PER_OPERATOR_HEADERS > -DCPUINFO_SUPPORTED_PLATFORM=3D0 -DFMT_HEADER_ONLY=3D1 > -DHAVE_MALLOC_USABLE_SIZE=3D1 -DHAVE_MMAP=3D1 -DHAVE_SHM_OPEN=3D1 > -DHAVE_SHM_UNLINK=3D1 -DMINIZ_DISABLE_ZIP_READER_CRC32_CHECKS > -DONNXIFI_ENABLE_EXT=3D1 -DONNX_ML=3D1 -DONNX_NAMESPACE=3Donnx > -DUSE_EXTERNAL_MZCRC -D_FILE_OFFSET_BITS=3D64 -Dtorch_cpu_EXPORTS > -I/usr/ports/misc/pytorch/work/.build/aten/src > -I/usr/ports/misc/pytorch/work/pytorch-v1.13.1/aten/src > -I/usr/ports/misc/pytorch/work/.build > -I/usr/ports/misc/pytorch/work/pytorch-v1.13.1 > -I/usr/ports/misc/pytorch/work/pytorch-v1.13.1/third_party/foxi > -I/usr/ports/misc/pytorch/work/.build/third_party/foxi > -I/usr/ports/misc/pytorch/work/pytorch-v1.13.1/torch/csrc/api > -I/usr/ports/misc/pytorch/work/pytorch-v1.13.1/torch/csrc/api/include > -I/usr/ports/misc/pytorch/work/pytorch-v1.13.1/caffe2/aten/src/TH > -I/usr/ports/misc/pytorch/work/.build/caffe2/aten/src/TH > -I/usr/ports/misc/pytorch/work/.build/caffe2/aten/src > -I/usr/ports/misc/pytorch/work/.build/caffe2/../aten/src > -I/usr/ports/misc/pytorch/work/pytorch-v1.13.1/torch/csrc > -I/usr/ports/misc/pytorch/work/pytorch-v1.13.1/third_party/miniz-2.1.0 > > -I/usr/ports/misc/pytorch/work/pytorch-v1.13.1/third_party/kineto/libkine= to/include > > -I/usr/ports/misc/pytorch/work/pytorch-v1.13.1/third_party/kineto/libkine= to/src > > -I/usr/ports/misc/pytorch/work/pytorch-v1.13.1/aten/../third_party/catch/= single_include > -I/usr/ports/misc/pytorch/work/pytorch-v1.13.1/aten/src/ATen/.. > -I/usr/ports/misc/pytorch/work/pytorch-v1.13.1/c10/.. > -I/usr/ports/misc/pytorch/work/pytorch-v1.13.1/third_party/cpuinfo/includ= e > -I/usr/ports/misc/pytorch/work/pytorch-v1.13.1/third_party/FP16/include > -I/usr/ports/misc/pytorch/work/pytorch-v1.13.1/third_party/fmt/include > > -I/usr/ports/misc/pytorch/work/pytorch-v1.13.1/third_party/flatbuffers/in= clude > -isystem > /usr/ports/misc/pytorch/work/pytorch-v1.13.1/cmake/../third_party/eigen > -isystem /usr/ports/misc/pytorch/work/pytorch-v1.13.1/caffe2 -O2 -pipe > -fstack-protector-strong -isystem /usr/local/include > -fno-strict-aliasing -isystem /usr/local/include -Wno-deprecated > -fvisibility-inlines-hidden -fopenmp=3Dlibomp -DNDEBUG -DUSE_KINETO > -DLIBKINETO_NOCUPTI -DSYMBOLICATE_MOBILE_DEBUG_HANDLE > -DEDGE_PROFILER_USE_KINETO -O2 -fPIC -Wno-narrowing -Wall -Wextra > -Werror=3Dreturn-type -Werror=3Dnon-virtual-dtor > -Wno-missing-field-initializers -Wno-type-limits -Wno-array-bounds > -Wno-unknown-pragmas -Wunused-local-typedefs -Wno-unused-parameter > -Wno-unused-function -Wno-unused-result -Wno-strict-overflow > -Wno-strict-aliasing -Wno-error=3Ddeprecated-declarations > -Wvla-extension -Wno-range-loop-analysis -Wno-pass-failed > -Wno-error=3Dpedantic -Wno-error=3Dredundant-decls > -Wno-error=3Dold-style-cast -Wconstant-conversion > -Wno-invalid-partial-specialization -Wno-typedef-redefinition > -Wno-unused-private-field -Wno-inconsistent-missing-override > -Wno-c++14-extensions -Wno-constexpr-not-const -Wno-missing-braces > -Wunused-lambda-capture -Wunused-local-typedef -Qunused-arguments > -fcolor-diagnostics -fdiagnostics-color=3Dalways > -Wno-unused-but-set-variable -fno-math-errno -fno-trapping-math > -Werror=3Dformat -Werror=3Dcast-function-type -DHAVE_AVX512_CPU_DEFINITIO= N > -DHAVE_AVX2_CPU_DEFINITION -O2 -pipe -fstack-protector-strong -isystem > /usr/local/include -fno-strict-aliasing -isystem /usr/local/include > -DNDEBUG -DNDEBUG -std=3Dgnu++14 -fPIC -DTH_HAVE_THREAD -Wall -Wextra > -Wno-unused-parameter -Wno-unused-function -Wno-unused-result > -Wno-missing-field-initializers -Wno-write-strings > -Wno-unknown-pragmas -Wno-type-limits -Wno-array-bounds > -Wno-sign-compare -Wno-strict-overflow -Wno-strict-aliasing > -Wno-error=3Ddeprecated-declarations -Wno-missing-braces > -Wno-range-loop-analysis -fvisibility=3Dhidden -O2 -fopenmp=3Dlibomp > -DCAFFE2_BUILD_MAIN_LIB -pthread -MD -MT > > caffe2/CMakeFiles/torch_cpu.dir/__/torch/csrc/api/src/serialize/output-ar= chive.cpp.o > -MF > caffe2/CMakeFiles/torch_cpu.dir/__/torch/csrc/api/src/serialize/output-ar= chive.cpp.o.d > -o > caffe2/CMakeFiles/torch_cpu.dir/__/torch/csrc/api/src/serialize/output-ar= chive.cpp.o > -c > /usr/ports/misc/pytorch/work/pytorch-v1.13.1/torch/csrc/api/src/serialize= /output-archive.cpp > ninja: build stopped: subcommand failed. > =3D=3D=3D> Compilation failed unexpectedly. > Try to set MAKE_JOBS_UNSAFE=3Dyes and rebuild before reporting the failur= e to > the maintainer. > *** Error code 1 > > Stop. > make: stopped in /usr/ports/misc/pytorch > > > > > Il gio 20 apr 2023, 17:51 Aryeh Friedman ha > scritto: > >> > >> On Thu, Apr 20, 2023 at 7:52=E2=80=AFAM Thierry Thomas > wrote: > >> > > >> > Le jeu. 20 avr. 23 =C3=A0 12:53:05 +0200, Aryeh Friedman < > aryeh.friedman@gmail.com> > >> > =C3=A9crivait : > >> > > >> > > Running without GPU (for now) on a bhyve vm (3 CPU, 2 GB RAM and 1= 00 > >> > > GB of disk) which I intend for determining if it is worse going ou= t > >> > > and getting the hardware to do GPU. The problem I had was gettin= g > >> > > pytorch to work since it appears I have to build it from source an= d > it > >> > > blows up in that build. > >> > > >> > Have you seen > >> > ? > >> > >> This seems to be true for all OS's I guess I will have to find an > >> intel machine... this is as bad as the motivation that led me to do > >> petitecloud in the first place (openstack not running on AMD period). > >> Is there just no way to run a ANN in pytorch data format in any other > >> way that is not python (like Java?!!?) note the tensorflow port > >> required pytorch > >> > >> > >> -- > >> Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org > >> > > > -- > Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org > --=20 Mario. --0000000000009e07eb05f9d5fdf2 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 
Can't you install pytorch using the =
linux miniconda installer like below ? 

# fetch https://gist.gith=
ubusercontent.com/shkhln/40ef290463e78fb2b0000c60f4ad797e/raw/f640983249607=
e38af405c95c457ce4afc85c608/uvm_ioctl_override.c

# /compat/ubuntu/bin/gcc --sysroot=3D/compat/ubuntu -m64 -std=3Dc99 -Wall -=
ldl -fPIC -shared -o dummy-uvm.so uvm_ioctl_override.c

# pkg install linux-miniconda-installer
# miniconda-installer
# bash
# source /home/marietto/miniconda3/etc/profile.d/conda.sh
# conda activate

(base) # conda activate pytorch

On Fri, Apr 21, 2023 at 2:38=E2=80=AFAM Aryeh Friedman <aryeh.friedman@gmail.com> w= rote:
On Thu, Ap= r 20, 2023 at 12:24=E2=80=AFPM Mario Marietto <marietto2008@gmail.com> wrote: >
> try to copy and paste the commands that you have issued on pastebin...= i need to understand the scenario

After saving the patch from the bug report to PORT/files and running
portmaster -P misc/pytourch (brand new machine except for=C2=A0 installing<= br> portmaster):

c/ATen/UfuncCPUKernel_add.cpp.AVX2.cpp.o -c
/usr/ports/misc/pytorch/work/.build/aten/src/ATen/UfuncCPUKernel_add.cpp.AV= X2.cpp
In file included from
/usr/ports/misc/pytorch/work/.build/aten/src/ATen/UfuncCPUKernel_add.cpp.AV= X2.cpp:1:
In file included from
/usr/ports/misc/pytorch/work/.build/aten/src/ATen/UfuncCPUKernel_add.cpp:3:=
In file included from
/usr/ports/misc/pytorch/work/pytorch-v1.13.1/aten/src/ATen/native/ufunc/add= .h:6:
In file included from
/usr/ports/misc/pytorch/work/pytorch-v1.13.1/aten/src/ATen/cpu/vec/function= al.h:3:
In file included from
/usr/ports/misc/pytorch/work/pytorch-v1.13.1/aten/src/ATen/cpu/vec/function= al_base.h:6:
In file included from
/usr/ports/misc/pytorch/work/pytorch-v1.13.1/aten/src/ATen/cpu/vec/vec.h:6:=
In file included from
/usr/ports/misc/pytorch/work/pytorch-v1.13.1/aten/src/ATen/cpu/vec/vec256/v= ec256.h:12:
/usr/ports/misc/pytorch/work/pytorch-v1.13.1/aten/src/ATen/cpu/vec/vec256/v= ec256_bfloat16.h:253:16:
error: cannot initialize a parameter of type 'const __m256
(*)(__m256)' with an lvalue of type '__m256 (__m256)': differen= t
return type ('const __m256' (vector of 8 'float' values) vs= '__m256'
(vector of 8 'float' values))
=C2=A0 =C2=A0 return map(Sleef_acosf8_u10);
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0^~~~~~~~~~~~~~~~
/usr/ports/misc/pytorch/work/pytorch-v1.13.1/aten/src/ATen/cpu/vec/vec256/v= ec256_bfloat16.h:209:49:
note: passing argument to parameter 'vop' here
=C2=A0 Vectorized<BFloat16> map(const __m256 (*const vop)(__m256)) co= nst {
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 ^
/usr/ports/misc/pytorch/work/pytorch-v1.13.1/aten/src/ATen/cpu/vec/vec256/v= ec256_bfloat16.h:256:16:
error: cannot initialize a parameter of type 'const __m256
(*)(__m256)' with an lvalue of type '__m256 (__m256)': differen= t
return type ('const __m256' (vector of 8 'float' values) vs= '__m256'
(vector of 8 'float' values))
=C2=A0 =C2=A0 return map(Sleef_asinf8_u10);
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0^~~~~~~~~~~~~~~~
/usr/ports/misc/pytorch/work/pytorch-v1.13.1/aten/src/ATen/cpu/vec/vec256/v= ec256_bfloat16.h:209:49:
note: passing argument to parameter 'vop' here
=C2=A0 Vectorized<BFloat16> map(const __m256 (*const vop)(__m256)) co= nst {
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 ^
/usr/ports/misc/pytorch/work/pytorch-v1.13.1/aten/src/ATen/cpu/vec/vec256/v= ec256_bfloat16.h:259:16:
error: cannot initialize a parameter of type 'const __m256
(*)(__m256)' with an lvalue of type '__m256 (__m256)': differen= t
return type ('const __m256' (vector of 8 'float' values) vs= '__m256'
(vector of 8 'float' values))
=C2=A0 =C2=A0 return map(Sleef_atanf8_u10);
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0^~~~~~~~~~~~~~~~
/usr/ports/misc/pytorch/work/pytorch-v1.13.1/aten/src/ATen/cpu/vec/vec256/v= ec256_bfloat16.h:209:49:
note: passing argument to parameter 'vop' here
=C2=A0 Vectorized<BFloat16> map(const __m256 (*const vop)(__m256)) co= nst {
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 ^
/usr/ports/misc/pytorch/work/pytorch-v1.13.1/aten/src/ATen/cpu/vec/vec256/v= ec256_bfloat16.h:280:16:
error: cannot initialize a parameter of type 'const __m256
(*)(__m256)' with an lvalue of type '__m256 (__m256)': differen= t
return type ('const __m256' (vector of 8 'float' values) vs= '__m256'
(vector of 8 'float' values))
=C2=A0 =C2=A0 return map(Sleef_erff8_u10);
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0^~~~~~~~~~~~~~~
/usr/ports/misc/pytorch/work/pytorch-v1.13.1/aten/src/ATen/cpu/vec/vec256/v= ec256_bfloat16.h:209:49:
note: passing argument to parameter 'vop' here
=C2=A0 Vectorized<BFloat16> map(const __m256 (*const vop)(__m256)) co= nst {
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 ^
/usr/ports/misc/pytorch/work/pytorch-v1.13.1/aten/src/ATen/cpu/vec/vec256/v= ec256_bfloat16.h:283:16:
error: cannot initialize a parameter of type 'const __m256
(*)(__m256)' with an lvalue of type '__m256 (__m256)': differen= t
return type ('const __m256' (vector of 8 'float' values) vs= '__m256'
(vector of 8 'float' values))
=C2=A0 =C2=A0 return map(Sleef_erfcf8_u15);
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0^~~~~~~~~~~~~~~~
/usr/ports/misc/pytorch/work/pytorch-v1.13.1/aten/src/ATen/cpu/vec/vec256/v= ec256_bfloat16.h:209:49:
note: passing argument to parameter 'vop' here
=C2=A0 Vectorized<BFloat16> map(const __m256 (*const vop)(__m256)) co= nst {
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 ^
/usr/ports/misc/pytorch/work/pytorch-v1.13.1/aten/src/ATen/cpu/vec/vec256/v= ec256_bfloat16.h:300:16:
error: cannot initialize a parameter of type 'const __m256
(*)(__m256)' with an lvalue of type '__m256 (__m256)': differen= t
return type ('const __m256' (vector of 8 'float' values) vs= '__m256'
(vector of 8 'float' values))
=C2=A0 =C2=A0 return map(Sleef_expf8_u10);
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0^~~~~~~~~~~~~~~
/usr/ports/misc/pytorch/work/pytorch-v1.13.1/aten/src/ATen/cpu/vec/vec256/v= ec256_bfloat16.h:209:49:
note: passing argument to parameter 'vop' here
=C2=A0 Vectorized<BFloat16> map(const __m256 (*const vop)(__m256)) co= nst {
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 ^
/usr/ports/misc/pytorch/work/pytorch-v1.13.1/aten/src/ATen/cpu/vec/vec256/v= ec256_bfloat16.h:303:16:
error: cannot initialize a parameter of type 'const __m256
(*)(__m256)' with an lvalue of type '__m256 (__m256)': differen= t
return type ('const __m256' (vector of 8 'float' values) vs= '__m256'
(vector of 8 'float' values))
=C2=A0 =C2=A0 return map(Sleef_expm1f8_u10);
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0^~~~~~~~~~~~~~~~~ /usr/ports/misc/pytorch/work/pytorch-v1.13.1/aten/src/ATen/cpu/vec/vec256/v= ec256_bfloat16.h:209:49:
note: passing argument to parameter 'vop' here
=C2=A0 Vectorized<BFloat16> map(const __m256 (*const vop)(__m256)) co= nst {
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 ^
/usr/ports/misc/pytorch/work/pytorch-v1.13.1/aten/src/ATen/cpu/vec/vec256/v= ec256_bfloat16.h:393:16:
error: cannot initialize a parameter of type 'const __m256
(*)(__m256)' with an lvalue of type '__m256 (__m256)': differen= t
return type ('const __m256' (vector of 8 'float' values) vs= '__m256'
(vector of 8 'float' values))
=C2=A0 =C2=A0 return map(Sleef_logf8_u10);
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0^~~~~~~~~~~~~~~
/usr/ports/misc/pytorch/work/pytorch-v1.13.1/aten/src/ATen/cpu/vec/vec256/v= ec256_bfloat16.h:209:49:
note: passing argument to parameter 'vop' here
=C2=A0 Vectorized<BFloat16> map(const __m256 (*const vop)(__m256)) co= nst {
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 ^
/usr/ports/misc/pytorch/work/pytorch-v1.13.1/aten/src/ATen/cpu/vec/vec256/v= ec256_bfloat16.h:396:16:
error: cannot initialize a parameter of type 'const __m256
(*)(__m256)' with an lvalue of type '__m256 (__m256)': differen= t
return type ('const __m256' (vector of 8 'float' values) vs= '__m256'
(vector of 8 'float' values))
=C2=A0 =C2=A0 return map(Sleef_log2f8_u10);
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0^~~~~~~~~~~~~~~~
/usr/ports/misc/pytorch/work/pytorch-v1.13.1/aten/src/ATen/cpu/vec/vec256/v= ec256_bfloat16.h:209:49:
note: passing argument to parameter 'vop' here
=C2=A0 Vectorized<BFloat16> map(const __m256 (*const vop)(__m256)) co= nst {
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 ^
/usr/ports/misc/pytorch/work/pytorch-v1.13.1/aten/src/ATen/cpu/vec/vec256/v= ec256_bfloat16.h:399:16:
error: cannot initialize a parameter of type 'const __m256
(*)(__m256)' with an lvalue of type '__m256 (__m256)': differen= t
return type ('const __m256' (vector of 8 'float' values) vs= '__m256'
(vector of 8 'float' values))
=C2=A0 =C2=A0 return map(Sleef_log10f8_u10);
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0^~~~~~~~~~~~~~~~~ /usr/ports/misc/pytorch/work/pytorch-v1.13.1/aten/src/ATen/cpu/vec/vec256/v= ec256_bfloat16.h:209:49:
note: passing argument to parameter 'vop' here
=C2=A0 Vectorized<BFloat16> map(const __m256 (*const vop)(__m256)) co= nst {
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 ^
/usr/ports/misc/pytorch/work/pytorch-v1.13.1/aten/src/ATen/cpu/vec/vec256/v= ec256_bfloat16.h:402:16:
error: cannot initialize a parameter of type 'const __m256
(*)(__m256)' with an lvalue of type '__m256 (__m256)': differen= t
return type ('const __m256' (vector of 8 'float' values) vs= '__m256'
(vector of 8 'float' values))
=C2=A0 =C2=A0 return map(Sleef_log1pf8_u10);
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0^~~~~~~~~~~~~~~~~ /usr/ports/misc/pytorch/work/pytorch-v1.13.1/aten/src/ATen/cpu/vec/vec256/v= ec256_bfloat16.h:209:49:
note: passing argument to parameter 'vop' here
=C2=A0 Vectorized<BFloat16> map(const __m256 (*const vop)(__m256)) co= nst {
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 ^
/usr/ports/misc/pytorch/work/pytorch-v1.13.1/aten/src/ATen/cpu/vec/vec256/v= ec256_bfloat16.h:406:16:
error: cannot initialize a parameter of type 'const __m256
(*)(__m256)' with an lvalue of type '__m256 (__m256)': differen= t
return type ('const __m256' (vector of 8 'float' values) vs= '__m256'
(vector of 8 'float' values))
=C2=A0 =C2=A0 return map(Sleef_sinf8_u10);
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0^~~~~~~~~~~~~~~
/usr/ports/misc/pytorch/work/pytorch-v1.13.1/aten/src/ATen/cpu/vec/vec256/v= ec256_bfloat16.h:209:49:
note: passing argument to parameter 'vop' here
=C2=A0 Vectorized<BFloat16> map(const __m256 (*const vop)(__m256)) co= nst {
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 ^
/usr/ports/misc/pytorch/work/pytorch-v1.13.1/aten/src/ATen/cpu/vec/vec256/v= ec256_bfloat16.h:409:16:
error: cannot initialize a parameter of type 'const __m256
(*)(__m256)' with an lvalue of type '__m256 (__m256)': differen= t
return type ('const __m256' (vector of 8 'float' values) vs= '__m256'
(vector of 8 'float' values))
=C2=A0 =C2=A0 return map(Sleef_sinhf8_u10);
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0^~~~~~~~~~~~~~~~
/usr/ports/misc/pytorch/work/pytorch-v1.13.1/aten/src/ATen/cpu/vec/vec256/v= ec256_bfloat16.h:209:49:
note: passing argument to parameter 'vop' here
=C2=A0 Vectorized<BFloat16> map(const __m256 (*const vop)(__m256)) co= nst {
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 ^
/usr/ports/misc/pytorch/work/pytorch-v1.13.1/aten/src/ATen/cpu/vec/vec256/v= ec256_bfloat16.h:412:16:
error: cannot initialize a parameter of type 'const __m256
(*)(__m256)' with an lvalue of type '__m256 (__m256)': differen= t
return type ('const __m256' (vector of 8 'float' values) vs= '__m256'
(vector of 8 'float' values))
=C2=A0 =C2=A0 return map(Sleef_cosf8_u10);
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0^~~~~~~~~~~~~~~
/usr/ports/misc/pytorch/work/pytorch-v1.13.1/aten/src/ATen/cpu/vec/vec256/v= ec256_bfloat16.h:209:49:
note: passing argument to parameter 'vop' here
=C2=A0 Vectorized<BFloat16> map(const __m256 (*const vop)(__m256)) co= nst {
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 ^
/usr/ports/misc/pytorch/work/pytorch-v1.13.1/aten/src/ATen/cpu/vec/vec256/v= ec256_bfloat16.h:415:16:
error: cannot initialize a parameter of type 'const __m256
(*)(__m256)' with an lvalue of type '__m256 (__m256)': differen= t
return type ('const __m256' (vector of 8 'float' values) vs= '__m256'
(vector of 8 'float' values))
=C2=A0 =C2=A0 return map(Sleef_coshf8_u10);
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0^~~~~~~~~~~~~~~~
/usr/ports/misc/pytorch/work/pytorch-v1.13.1/aten/src/ATen/cpu/vec/vec256/v= ec256_bfloat16.h:209:49:
note: passing argument to parameter 'vop' here
=C2=A0 Vectorized<BFloat16> map(const __m256 (*const vop)(__m256)) co= nst {
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 ^
/usr/ports/misc/pytorch/work/pytorch-v1.13.1/aten/src/ATen/cpu/vec/vec256/v= ec256_bfloat16.h:447:16:
error: cannot initialize a parameter of type 'const __m256
(*)(__m256)' with an lvalue of type '__m256 (__m256)': differen= t
return type ('const __m256' (vector of 8 'float' values) vs= '__m256'
(vector of 8 'float' values))
=C2=A0 =C2=A0 return map(Sleef_tanf8_u10);
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0^~~~~~~~~~~~~~~
/usr/ports/misc/pytorch/work/pytorch-v1.13.1/aten/src/ATen/cpu/vec/vec256/v= ec256_bfloat16.h:209:49:
note: passing argument to parameter 'vop' here
=C2=A0 Vectorized<BFloat16> map(const __m256 (*const vop)(__m256)) co= nst {
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 ^
/usr/ports/misc/pytorch/work/pytorch-v1.13.1/aten/src/ATen/cpu/vec/vec256/v= ec256_bfloat16.h:450:16:
error: cannot initialize a parameter of type 'const __m256
(*)(__m256)' with an lvalue of type '__m256 (__m256)': differen= t
return type ('const __m256' (vector of 8 'float' values) vs= '__m256'
(vector of 8 'float' values))
=C2=A0 =C2=A0 return map(Sleef_tanhf8_u10);
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0^~~~~~~~~~~~~~~~
/usr/ports/misc/pytorch/work/pytorch-v1.13.1/aten/src/ATen/cpu/vec/vec256/v= ec256_bfloat16.h:209:49:
note: passing argument to parameter 'vop' here
=C2=A0 Vectorized<BFloat16> map(const __m256 (*const vop)(__m256)) co= nst {
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 ^
/usr/ports/misc/pytorch/work/pytorch-v1.13.1/aten/src/ATen/cpu/vec/vec256/v= ec256_bfloat16.h:460:16:
error: cannot initialize a parameter of type 'const __m256
(*)(__m256)' with an lvalue of type '__m256 (__m256)': differen= t
return type ('const __m256' (vector of 8 'float' values) vs= '__m256'
(vector of 8 'float' values))
=C2=A0 =C2=A0 return map(Sleef_lgammaf8_u10);
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0^~~~~~~~~~~~~~~~~~ /usr/ports/misc/pytorch/work/pytorch-v1.13.1/aten/src/ATen/cpu/vec/vec256/v= ec256_bfloat16.h:209:49:
note: passing argument to parameter 'vop' here
=C2=A0 Vectorized<BFloat16> map(const __m256 (*const vop)(__m256)) co= nst {
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 ^
18 errors generated.
[ 80% 1035/1283] /usr/bin/c++ -DAT_PER_OPERATOR_HEADERS
-DCPUINFO_SUPPORTED_PLATFORM=3D0 -DFMT_HEADER_ONLY=3D1
-DHAVE_MALLOC_USABLE_SIZE=3D1 -DHAVE_MMAP=3D1 -DHAVE_SHM_OPEN=3D1
-DHAVE_SHM_UNLINK=3D1 -DMINIZ_DISABLE_ZIP_READER_CRC32_CHECKS
-DONNXIFI_ENABLE_EXT=3D1 -DONNX_ML=3D1 -DONNX_NAMESPACE=3Donnx
-DUSE_EXTERNAL_MZCRC -D_FILE_OFFSET_BITS=3D64 -Dtorch_cpu_EXPORTS
-I/usr/ports/misc/pytorch/work/.build/aten/src
-I/usr/ports/misc/pytorch/work/pytorch-v1.13.1/aten/src
-I/usr/ports/misc/pytorch/work/.build
-I/usr/ports/misc/pytorch/work/pytorch-v1.13.1
-I/usr/ports/misc/pytorch/work/pytorch-v1.13.1/third_party/foxi
-I/usr/ports/misc/pytorch/work/.build/third_party/foxi
-I/usr/ports/misc/pytorch/work/pytorch-v1.13.1/torch/csrc/api
-I/usr/ports/misc/pytorch/work/pytorch-v1.13.1/torch/csrc/api/include
-I/usr/ports/misc/pytorch/work/pytorch-v1.13.1/caffe2/aten/src/TH
-I/usr/ports/misc/pytorch/work/.build/caffe2/aten/src/TH
-I/usr/ports/misc/pytorch/work/.build/caffe2/aten/src
-I/usr/ports/misc/pytorch/work/.build/caffe2/../aten/src
-I/usr/ports/misc/pytorch/work/pytorch-v1.13.1/torch/csrc
-I/usr/ports/misc/pytorch/work/pytorch-v1.13.1/third_party/miniz-2.1.0
-I/usr/ports/misc/pytorch/work/pytorch-v1.13.1/third_party/kineto/libkineto= /include
-I/usr/ports/misc/pytorch/work/pytorch-v1.13.1/third_party/kineto/libkineto= /src
-I/usr/ports/misc/pytorch/work/pytorch-v1.13.1/aten/../third_party/catch/si= ngle_include
-I/usr/ports/misc/pytorch/work/pytorch-v1.13.1/aten/src/ATen/..
-I/usr/ports/misc/pytorch/work/pytorch-v1.13.1/c10/..
-I/usr/ports/misc/pytorch/work/pytorch-v1.13.1/third_party/cpuinfo/include<= br> -I/usr/ports/misc/pytorch/work/pytorch-v1.13.1/third_party/FP16/include
-I/usr/ports/misc/pytorch/work/pytorch-v1.13.1/third_party/fmt/include
-I/usr/ports/misc/pytorch/work/pytorch-v1.13.1/third_party/flatbuffers/incl= ude
-isystem /usr/ports/misc/pytorch/work/pytorch-v1.13.1/cmake/../third_party/= eigen
-isystem /usr/ports/misc/pytorch/work/pytorch-v1.13.1/caffe2 -O2 -pipe
-fstack-protector-strong -isystem /usr/local/include
-fno-strict-aliasing=C2=A0 -isystem /usr/local/include -Wno-deprecated
-fvisibility-inlines-hidden -fopenmp=3Dlibomp -DNDEBUG -DUSE_KINETO
-DLIBKINETO_NOCUPTI -DSYMBOLICATE_MOBILE_DEBUG_HANDLE
-DEDGE_PROFILER_USE_KINETO -O2 -fPIC -Wno-narrowing -Wall -Wextra
-Werror=3Dreturn-type -Werror=3Dnon-virtual-dtor
-Wno-missing-field-initializers -Wno-type-limits -Wno-array-bounds
-Wno-unknown-pragmas -Wunused-local-typedefs -Wno-unused-parameter
-Wno-unused-function -Wno-unused-result -Wno-strict-overflow
-Wno-strict-aliasing -Wno-error=3Ddeprecated-declarations
-Wvla-extension -Wno-range-loop-analysis -Wno-pass-failed
-Wno-error=3Dpedantic -Wno-error=3Dredundant-decls
-Wno-error=3Dold-style-cast -Wconstant-conversion
-Wno-invalid-partial-specialization -Wno-typedef-redefinition
-Wno-unused-private-field -Wno-inconsistent-missing-override
-Wno-c++14-extensions -Wno-constexpr-not-const -Wno-missing-braces
-Wunused-lambda-capture -Wunused-local-typedef -Qunused-arguments
-fcolor-diagnostics -fdiagnostics-color=3Dalways
-Wno-unused-but-set-variable -fno-math-errno -fno-trapping-math
-Werror=3Dformat -Werror=3Dcast-function-type -DHAVE_AVX512_CPU_DEFINITION<= br> -DHAVE_AVX2_CPU_DEFINITION -O2 -pipe -fstack-protector-strong -isystem
/usr/local/include -fno-strict-aliasing=C2=A0 -isystem /usr/local/include -DNDEBUG -DNDEBUG -std=3Dgnu++14 -fPIC -DTH_HAVE_THREAD -Wall -Wextra
-Wno-unused-parameter -Wno-unused-function -Wno-unused-result
-Wno-missing-field-initializers -Wno-write-strings
-Wno-unknown-pragmas -Wno-type-limits -Wno-array-bounds
-Wno-sign-compare -Wno-strict-overflow -Wno-strict-aliasing
-Wno-error=3Ddeprecated-declarations -Wno-missing-braces
-Wno-range-loop-analysis -fvisibility=3Dhidden -O2 -fopenmp=3Dlibomp
-DCAFFE2_BUILD_MAIN_LIB -pthread -MD -MT
caffe2/CMakeFiles/torch_cpu.dir/__/torch/csrc/api/src/serialize/input-archi= ve.cpp.o
-MF caffe2/CMakeFiles/torch_cpu.dir/__/torch/csrc/api/src/serialize/input-a= rchive.cpp.o.d
-o caffe2/CMakeFiles/torch_cpu.dir/__/torch/csrc/api/src/serialize/input-ar= chive.cpp.o
-c /usr/ports/misc/pytorch/work/pytorch-v1.13.1/torch/csrc/api/src/serializ= e/input-archive.cpp
[ 80% 1035/1283] /usr/bin/c++ -DAT_PER_OPERATOR_HEADERS
-DCPUINFO_SUPPORTED_PLATFORM=3D0 -DFMT_HEADER_ONLY=3D1
-DHAVE_MALLOC_USABLE_SIZE=3D1 -DHAVE_MMAP=3D1 -DHAVE_SHM_OPEN=3D1
-DHAVE_SHM_UNLINK=3D1 -DMINIZ_DISABLE_ZIP_READER_CRC32_CHECKS
-DONNXIFI_ENABLE_EXT=3D1 -DONNX_ML=3D1 -DONNX_NAMESPACE=3Donnx
-DUSE_EXTERNAL_MZCRC -D_FILE_OFFSET_BITS=3D64 -Dtorch_cpu_EXPORTS
-I/usr/ports/misc/pytorch/work/.build/aten/src
-I/usr/ports/misc/pytorch/work/pytorch-v1.13.1/aten/src
-I/usr/ports/misc/pytorch/work/.build
-I/usr/ports/misc/pytorch/work/pytorch-v1.13.1
-I/usr/ports/misc/pytorch/work/pytorch-v1.13.1/third_party/foxi
-I/usr/ports/misc/pytorch/work/.build/third_party/foxi
-I/usr/ports/misc/pytorch/work/pytorch-v1.13.1/torch/csrc/api
-I/usr/ports/misc/pytorch/work/pytorch-v1.13.1/torch/csrc/api/include
-I/usr/ports/misc/pytorch/work/pytorch-v1.13.1/caffe2/aten/src/TH
-I/usr/ports/misc/pytorch/work/.build/caffe2/aten/src/TH
-I/usr/ports/misc/pytorch/work/.build/caffe2/aten/src
-I/usr/ports/misc/pytorch/work/.build/caffe2/../aten/src
-I/usr/ports/misc/pytorch/work/pytorch-v1.13.1/torch/csrc
-I/usr/ports/misc/pytorch/work/pytorch-v1.13.1/third_party/miniz-2.1.0
-I/usr/ports/misc/pytorch/work/pytorch-v1.13.1/third_party/kineto/libkineto= /include
-I/usr/ports/misc/pytorch/work/pytorch-v1.13.1/third_party/kineto/libkineto= /src
-I/usr/ports/misc/pytorch/work/pytorch-v1.13.1/aten/../third_party/catch/si= ngle_include
-I/usr/ports/misc/pytorch/work/pytorch-v1.13.1/aten/src/ATen/..
-I/usr/ports/misc/pytorch/work/pytorch-v1.13.1/c10/..
-I/usr/ports/misc/pytorch/work/pytorch-v1.13.1/third_party/cpuinfo/include<= br> -I/usr/ports/misc/pytorch/work/pytorch-v1.13.1/third_party/FP16/include
-I/usr/ports/misc/pytorch/work/pytorch-v1.13.1/third_party/fmt/include
-I/usr/ports/misc/pytorch/work/pytorch-v1.13.1/third_party/flatbuffers/incl= ude
-isystem /usr/ports/misc/pytorch/work/pytorch-v1.13.1/cmake/../third_party/= eigen
-isystem /usr/ports/misc/pytorch/work/pytorch-v1.13.1/caffe2 -O2 -pipe
-fstack-protector-strong -isystem /usr/local/include
-fno-strict-aliasing=C2=A0 -isystem /usr/local/include -Wno-deprecated
-fvisibility-inlines-hidden -fopenmp=3Dlibomp -DNDEBUG -DUSE_KINETO
-DLIBKINETO_NOCUPTI -DSYMBOLICATE_MOBILE_DEBUG_HANDLE
-DEDGE_PROFILER_USE_KINETO -O2 -fPIC -Wno-narrowing -Wall -Wextra
-Werror=3Dreturn-type -Werror=3Dnon-virtual-dtor
-Wno-missing-field-initializers -Wno-type-limits -Wno-array-bounds
-Wno-unknown-pragmas -Wunused-local-typedefs -Wno-unused-parameter
-Wno-unused-function -Wno-unused-result -Wno-strict-overflow
-Wno-strict-aliasing -Wno-error=3Ddeprecated-declarations
-Wvla-extension -Wno-range-loop-analysis -Wno-pass-failed
-Wno-error=3Dpedantic -Wno-error=3Dredundant-decls
-Wno-error=3Dold-style-cast -Wconstant-conversion
-Wno-invalid-partial-specialization -Wno-typedef-redefinition
-Wno-unused-private-field -Wno-inconsistent-missing-override
-Wno-c++14-extensions -Wno-constexpr-not-const -Wno-missing-braces
-Wunused-lambda-capture -Wunused-local-typedef -Qunused-arguments
-fcolor-diagnostics -fdiagnostics-color=3Dalways
-Wno-unused-but-set-variable -fno-math-errno -fno-trapping-math
-Werror=3Dformat -Werror=3Dcast-function-type -DHAVE_AVX512_CPU_DEFINITION<= br> -DHAVE_AVX2_CPU_DEFINITION -O2 -pipe -fstack-protector-strong -isystem
/usr/local/include -fno-strict-aliasing=C2=A0 -isystem /usr/local/include -DNDEBUG -DNDEBUG -std=3Dgnu++14 -fPIC -DTH_HAVE_THREAD -Wall -Wextra
-Wno-unused-parameter -Wno-unused-function -Wno-unused-result
-Wno-missing-field-initializers -Wno-write-strings
-Wno-unknown-pragmas -Wno-type-limits -Wno-array-bounds
-Wno-sign-compare -Wno-strict-overflow -Wno-strict-aliasing
-Wno-error=3Ddeprecated-declarations -Wno-missing-braces
-Wno-range-loop-analysis -fvisibility=3Dhidden -O2 -fopenmp=3Dlibomp
-DCAFFE2_BUILD_MAIN_LIB -pthread -MD -MT
caffe2/CMakeFiles/torch_cpu.dir/__/torch/csrc/api/src/serialize/output-arch= ive.cpp.o
-MF caffe2/CMakeFiles/torch_cpu.dir/__/torch/csrc/api/src/serialize/output-= archive.cpp.o.d
-o caffe2/CMakeFiles/torch_cpu.dir/__/torch/csrc/api/src/serialize/output-a= rchive.cpp.o
-c /usr/ports/misc/pytorch/work/pytorch-v1.13.1/torch/csrc/api/src/serializ= e/output-archive.cpp
ninja: build stopped: subcommand failed.
=3D=3D=3D> Compilation failed unexpectedly.
Try to set MAKE_JOBS_UNSAFE=3Dyes and rebuild before reporting the failure = to
the maintainer.
*** Error code 1

Stop.
make: stopped in /usr/ports/misc/pytorch

>
> Il gio 20 apr 2023, 17:51 Aryeh Friedman <aryeh.friedman@gmail.com> ha sc= ritto:
>>
>> On Thu, Apr 20, 2023 at 7:52=E2=80=AFAM Thierry Thomas <thierry@freebsd.org&g= t; wrote:
>> >
>> > Le jeu. 20 avr. 23 =C3=A0 12:53:05 +0200, Aryeh Friedman <= aryeh.friedma= n@gmail.com>
>> >=C2=A0 =C3=A9crivait :
>> >
>> > > Running without GPU (for now) on a bhyve vm (3 CPU, 2 GB= RAM and 100
>> > > GB of disk) which I intend for determining if it is wors= e going out
>> > > and getting the hardware to do GPU.=C2=A0 =C2=A0The prob= lem I had was getting
>> > > pytorch to work since it appears I have to build it from= source and it
>> > > blows up in that build.
>> >
>> > Have you seen
>> > <https://bugs.freebsd.org= /bugzilla/show_bug.cgi?id=3D269739> ?
>>
>> This seems to be true for all OS's I guess I will have to find= an
>> intel machine... this is as bad as the motivation that led me to d= o
>> petitecloud in the first place (openstack not running on AMD perio= d).
>>=C2=A0 Is there just no way to run a ANN in pytorch data format in = any other
>> way that is not python (like Java?!!?) note the tensorflow port >> required pytorch
>>
>>
>> --
>> Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org=
>>


--
Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org


--
Mario.
--0000000000009e07eb05f9d5fdf2-- From nobody Fri Apr 21 10:25:53 2023 X-Original-To: freebsd-hackers@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 4Q2rKB2Cjyz46D62; Fri, 21 Apr 2023 10:26:06 +0000 (UTC) (envelope-from aryeh.friedman@gmail.com) Received: from mail-ed1-x531.google.com (mail-ed1-x531.google.com [IPv6:2a00:1450:4864:20::531]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Q2rKB0ZDlz3k0L; Fri, 21 Apr 2023 10:26:06 +0000 (UTC) (envelope-from aryeh.friedman@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-ed1-x531.google.com with SMTP id 4fb4d7f45d1cf-50847469a7fso2114554a12.0; Fri, 21 Apr 2023 03:26:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1682072765; x=1684664765; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=i0X16cLbEkfY+3F3xIClirxOHeuZPdrcndoSscpUgVk=; b=IX1nVsxAIrM41sXFWyMkCOHeLJSJQzNT7EiMjcSHKNsb5Ei9XaiDpQYvlQB+Hs1uY3 v2LAw0mGkno0+cWxWS3/6l7wytT1kG6v98AFJHWj8mUWe9WshdQSIdg8OaYmaPhCUI7f ZnFHlCMl5nS3OOdNspjFY6M8yugFzhmvvz2JXJJoMxZAmk42LyVess+NociHWW2sdWtZ MSqxnSSh6ZOX6gwgerWuDo7SVvMVq1nAhZN3ju67/gNyhwSLIg8Y30uCDFH/YdM2eNuz gCBLiEXfS6b8N3+NpywEM+80fd7iNsiT9sFGCn3aBtdGqDVJgmLLAb7uFSVermubLdNm A69A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1682072765; x=1684664765; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=i0X16cLbEkfY+3F3xIClirxOHeuZPdrcndoSscpUgVk=; b=Hw8XzjDLKxH9XXBok0RehZvU7MriWYph94eTkVVdRVwhTBxDipyIiXoBugBKvIMPxl 1iaGSSMu2oZtGFPVDeXRwEM4PhqsvSrXbmamgGl4B1Zi0JvfL+2ah4xMIfLj2zy2i+x3 mOw+EI3+2l3HEhfXK1LXDPzFiSNKLFZGfcMeYiRkb0Swy3kFn6sOMoUwUOeKX2BcZ67u obUN4tklr5SRYXHMXUdDHRrGx2RNU5888CHmlWzeHo3t63qQCusjDwdWsOBHYe+CUgxA ZKExDmG94GqoktA3hTIeUAilDywrkbNQUGnBx61FDQHMkb4koqBuf52uLAFHpEjEClj/ qOlA== X-Gm-Message-State: AAQBX9cD8MT+PqzFrqUqtWUXtjPnxBZ9PsYmOyYW/bXe82tbqqHGiorr asLFEiSiqFx2bKU77NEkRmgX5mmlTjJOH/TdjltZRC5P X-Google-Smtp-Source: AKy350ZepyqoqvxjqNoqXxRn4vwZjC4XOReG6IkqvLcKe3zkqAaGFlY5NXjMYVhDH1BFmVgD7A+cCFvKFTGa6ZmeSqI= X-Received: by 2002:aa7:dcc3:0:b0:505:48c:3266 with SMTP id w3-20020aa7dcc3000000b00505048c3266mr4939169edu.20.1682072764513; Fri, 21 Apr 2023 03:26:04 -0700 (PDT) List-Id: Technical discussions relating to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-hackers List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-hackers@freebsd.org MIME-Version: 1.0 References: In-Reply-To: From: Aryeh Friedman Date: Fri, 21 Apr 2023 06:25:53 -0400 Message-ID: Subject: Re: Installing openAI's GPT-2 Ada AI Language Model To: Mario Marietto Cc: FreeBSD Mailing List , FreeBSD Mailing List , Yuri Victorovich Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Rspamd-Queue-Id: 4Q2rKB0ZDlz3k0L X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; TAGGED_FROM(0.00)[] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N The more I am fighting with it in linux (only thing there is docs for) the more obvious it just doesn't work on On Fri, Apr 21, 2023 at 6:19=E2=80=AFAM Mario Marietto wrote: > > Can't you install pytorch using the linux miniconda installer like below = ? > > # fetch https://gist.githubusercontent.com/shkhln/40ef290463e78fb2b0000c6= 0f4ad797e/raw/f640983249607e38af405c95c457ce4afc85c608/uvm_ioctl_override.c > > # /compat/ubuntu/bin/gcc --sysroot=3D/compat/ubuntu -m64 -std=3Dc99 -Wall= -ldl -fPIC -shared -o dummy-uvm.so uvm_ioctl_override.c > > # pkg install linux-miniconda-installer > # miniconda-installer > # bash > # source /home/marietto/miniconda3/etc/profile.d/conda.sh > # conda activate > > (base) # conda activate pytorch > Will this work a bhyve on an AMD Ryzen 5 host? After playing with it in several linux instances I always get stuck when it can't find a compatible version --=20 Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org From nobody Fri Apr 21 10:39:33 2023 X-Original-To: freebsd-hackers@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 4Q2rdQ6cWvz46F2j; Fri, 21 Apr 2023 10:40:10 +0000 (UTC) (envelope-from marietto2008@gmail.com) Received: from mail-yw1-x1131.google.com (mail-yw1-x1131.google.com [IPv6:2607:f8b0:4864:20::1131]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Q2rdQ1LxDz3nR4; Fri, 21 Apr 2023 10:40:10 +0000 (UTC) (envelope-from marietto2008@gmail.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20221208 header.b=KuvfTvxp; spf=pass (mx1.freebsd.org: domain of marietto2008@gmail.com designates 2607:f8b0:4864:20::1131 as permitted sender) smtp.mailfrom=marietto2008@gmail.com; dmarc=pass (policy=none) header.from=gmail.com Received: by mail-yw1-x1131.google.com with SMTP id 00721157ae682-54f8b46d031so16275637b3.3; Fri, 21 Apr 2023 03:40:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1682073609; x=1684665609; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=UOmwPFVI/uv2OqY4r7wB/WRY7PFWKe9qqzxcWh9m0zE=; b=KuvfTvxpiD6/Qnu4uxCSiGpnZdbGIy57LUxlnetGf0RfcPZG20RoF37I/9o20oGzE6 lu3miZrn5vC2AoPwEKkSVn1h/14IvlVjUM6Mwu4A/VWOp+cW2luZKl287KPKOdd5R3JN F5dC8vSNw3b6ZiMvlyTXFs3Nq7xFLtAuT1Z0hn0o5LVcQrqtdQ2O3dG23IZLOmFadT3w mFALtaY/ojstDLbSNMQo3eiTZ6tuNo6BSVkxWDzc7e4/r4CCMMwf8Ne4rMNjEIqrvhSp zRXYwjolVgG7P26f0AkGTaacnA6aH1UbgkKeWtTxXq1lFx9JrARxC6ak84XKCOlKGATj YQkA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1682073609; x=1684665609; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=UOmwPFVI/uv2OqY4r7wB/WRY7PFWKe9qqzxcWh9m0zE=; b=BTpmIm5LKeSKUar4Vd6OnZKRoQgrQr2w2s9g8xg17pBI1oyV7uY2rc/XOADyxcJBf7 tmQxr3Twg4MESfr1MwtTS7ncrNqBagqD+2jGwXrqbh4z+UGSxcqzRV51+p+hZe7utDJm 2g6d+uX021b7MwOEyXfycmpk9OGx8FkoUYUcfUVyaIlIztGGk3WX3A32EDrzQ7LRvSVm DIqJutjAxtYGb23hxQ8J89LpBHoljL8CqmzvcCyQ/5wWEHXZvLgmJx2giHdK1yb0O/Mt r0sOqFa2vae3FifX2UhiqUh7vrAOcRWDfo3cfWEZHgBCRu668qXbYV31N5BnQkxD0SYS zjYw== X-Gm-Message-State: AAQBX9c/O3C2ZaX9+bXLZ6nXGWpnjU4rqXaXOmAE2QBgFN8NaXpzfSDS vwFY0Zs5g6+KxHe1fqVTqYv7kOQhvduq8CuoXenkClBEzRY= X-Google-Smtp-Source: AKy350ZeN1ek1T8jMctPUm44lIyqcZLv6guI4g/L+aeTzR0gOWodK5zxAwonw3QMsc5vSnh8jwoZ+/dnQQOhraSFse0= X-Received: by 2002:a0d:fc86:0:b0:54f:b244:fef9 with SMTP id m128-20020a0dfc86000000b0054fb244fef9mr1932442ywf.0.1682073609333; Fri, 21 Apr 2023 03:40:09 -0700 (PDT) List-Id: Technical discussions relating to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-hackers List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-hackers@freebsd.org MIME-Version: 1.0 References: In-Reply-To: From: Mario Marietto Date: Fri, 21 Apr 2023 12:39:33 +0200 Message-ID: Subject: Re: Installing openAI's GPT-2 Ada AI Language Model To: Aryeh Friedman Cc: FreeBSD Mailing List , FreeBSD Mailing List , Yuri Victorovich Content-Type: multipart/alternative; boundary="000000000000f8718305f9d647bc" X-Spamd-Result: default: False [-2.81 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20221208]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36:c]; NEURAL_SPAM_SHORT(0.19)[0.187]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; FREEMAIL_FROM(0.00)[gmail.com]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[4]; TAGGED_RCPT(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::1131:from]; TO_MATCH_ENVRCPT_SOME(0.00)[]; ARC_NA(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim]; RCVD_TLS_LAST(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; TO_DN_ALL(0.00)[]; MID_RHS_MATCH_FROMTLD(0.00)[]; MLMMJ_DEST(0.00)[freebsd-hackers@freebsd.org,freebsd-questions@freebsd.org]; FREEMAIL_TO(0.00)[gmail.com]; MIME_TRACE(0.00)[0:+,1:+,2:~]; FROM_EQ_ENVFROM(0.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; FREEMAIL_ENVFROM(0.00)[gmail.com]; RCVD_COUNT_TWO(0.00)[2] X-Rspamd-Queue-Id: 4Q2rdQ1LxDz3nR4 X-Spamd-Bar: -- X-ThisMailContainsUnwantedMimeParts: N --000000000000f8718305f9d647bc Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable You don't need bhyve to make that,but only the Linuxulator. I don't think the type of cpu will make any difference. I've used the Intel I9 cpu. I tried FreeBSD 13.1 and I haven't found problems. For sure using python env is tricky,but if you have the thinkering attitude,you will have some fun. On Fri, Apr 21, 2023 at 12:26=E2=80=AFPM Aryeh Friedman wrote: > The more I am fighting with it in linux (only thing there is docs for) > the more obvious it just doesn't work on > > On Fri, Apr 21, 2023 at 6:19=E2=80=AFAM Mario Marietto > wrote: > > > > Can't you install pytorch using the linux miniconda installer like belo= w > ? > > > > # fetch > https://gist.githubusercontent.com/shkhln/40ef290463e78fb2b0000c60f4ad797= e/raw/f640983249607e38af405c95c457ce4afc85c608/uvm_ioctl_override.c > > > > # /compat/ubuntu/bin/gcc --sysroot=3D/compat/ubuntu -m64 -std=3Dc99 -Wa= ll > -ldl -fPIC -shared -o dummy-uvm.so uvm_ioctl_override.c > > > > # pkg install linux-miniconda-installer > > # miniconda-installer > > # bash > > # source /home/marietto/miniconda3/etc/profile.d/conda.sh > > # conda activate > > > > (base) # conda activate pytorch > > > Will this work a bhyve on an AMD Ryzen 5 host? After playing with it > in several linux instances I always get stuck when it can't find a > compatible version > > -- > Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org > --=20 Mario. --000000000000f8718305f9d647bc Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
You don't need bhyve to make that,but only the Linuxul= ator. I don't think the type of cpu will make any difference. I've = used the Intel I9 cpu. I tried FreeBSD 13.1 and I haven't found problem= s. For sure using python env is tricky,but if you have the thinkering attit= ude,you will have some fun.

On Fri, Apr 21, 2023 at 12:26=E2=80=AFPM Ar= yeh Friedman <aryeh.friedman= @gmail.com> wrote:
The more I am fighting with it in linux (only thing there is doc= s for)
the more obvious it just doesn't work on

On Fri, Apr 21, 2023 at 6:19=E2=80=AFAM Mario Marietto <marietto2008@gmail.com> = wrote:
>
> Can't you install pytorch using the linux miniconda installer like= below ?
>
> # fetch https://gist.githubuse= rcontent.com/shkhln/40ef290463e78fb2b0000c60f4ad797e/raw/f640983249607e38af= 405c95c457ce4afc85c608/uvm_ioctl_override.c
>
> # /compat/ubuntu/bin/gcc --sysroot=3D/compat/ubuntu -m64 -std=3Dc99 -W= all -ldl -fPIC -shared -o dummy-uvm.so uvm_ioctl_override.c
>
> # pkg install linux-miniconda-installer
> # miniconda-installer
> # bash
> # source /home/marietto/miniconda3/etc/profile.d/conda.sh
> # conda activate
>
> (base) # conda activate pytorch
>
Will this work a bhyve on an AMD Ryzen 5 host?=C2=A0 =C2=A0After playing wi= th it
in several linux instances I always get stuck when it can't find a
compatible version

--
Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org


--
Mario.
--000000000000f8718305f9d647bc-- From nobody Fri Apr 21 11:34:17 2023 X-Original-To: freebsd-hackers@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 4Q2sr70P6dz46JVD; Fri, 21 Apr 2023 11:34:31 +0000 (UTC) (envelope-from aryeh.friedman@gmail.com) Received: from mail-ed1-x52f.google.com (mail-ed1-x52f.google.com [IPv6:2a00:1450:4864:20::52f]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Q2sr65Xvyz3tGQ; Fri, 21 Apr 2023 11:34:30 +0000 (UTC) (envelope-from aryeh.friedman@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-ed1-x52f.google.com with SMTP id 4fb4d7f45d1cf-506bdf29712so11369604a12.0; Fri, 21 Apr 2023 04:34:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1682076869; x=1684668869; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=7FfYJvMQgH5idukvFw+WBu5k6Q0+VCI5huVUXkgRv7w=; b=IkX0OV6+3QbpDnLeQGMC3iEFPm/wIO0fr2Fj6Q9NLrAsWMUvrnyG1K6SDDTyprscdF 1kKEzU98cq90+1RJc0YCrOq+UebxxdRpaYSVvo581D7kt7c2iFdx5ABSMJnd1imQnGIF pZdAA2DmQk7JewnWvOw8/lMGrfl3CdQxErEuw4u5KbsGr+nDHKqgJ/IC0hUV2ewBK+F8 kaY+HcTUlPnShijZDGQDn6TqFmQvLcHo0M4CTgyDjDa3DWccDH7UmHaVQE4SiVS0F4pg EiNxvOsbG7vbzVGgMskmoSbFjHwaY5iICBBBAGldyx3xTUHgPjyLjktBUCj0797zvE2k DLdw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1682076869; x=1684668869; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=7FfYJvMQgH5idukvFw+WBu5k6Q0+VCI5huVUXkgRv7w=; b=iy/+dJ6ig4VOtIpFYaEgrqNb7LSsZcuTxd4QG0qgTe18Sum27NTT7WyTJ/HBGfhKg2 AGhdcSxtjGunIeyqMxN2L5heZLALeL7OM/MwuxGpC2tUKT8HhBgwfn7ADPsgt7eo+wa3 fw5JXEwXtDkG/v7JY6gYeELKpPX0Nxo4wz7E5/rzQ8Fp+4tbH45JALKs4rhQwauM89Nw zlB9t2w6EvRdGiXSD0EUeUvAqxMhaLDO5kDJ7o7OuDCEQTqfXkZKP9itvqz6GkOK+ARv lZsFQ/PJ+qfMXC6Sej4otXQ+2/cUBE8ObcxgzsyShfvBXOWNcJhsCkab4nuNlGIU46CI vPMQ== X-Gm-Message-State: AAQBX9clWvQGGjnjHKMXwX0JK9Du/7x7f7M/xNX5NQJlW+eY7ZGCH1qA XiGjYoKnI/Mapg9nGAubTmoUUkYfhqtZVgnSGSI= X-Google-Smtp-Source: AKy350Y/ujmwBQCo+6trdSBauMQfc34F4EuSTnxgl/GnY2QZZ8XZFsqD0ya7QRrAayLPObWMngAmydGPD32P8ptl/dQ= X-Received: by 2002:a17:906:8691:b0:953:7e68:7e01 with SMTP id g17-20020a170906869100b009537e687e01mr1759219ejx.36.1682076869195; Fri, 21 Apr 2023 04:34:29 -0700 (PDT) List-Id: Technical discussions relating to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-hackers List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-hackers@freebsd.org MIME-Version: 1.0 References: In-Reply-To: From: Aryeh Friedman Date: Fri, 21 Apr 2023 07:34:17 -0400 Message-ID: Subject: Re: Installing openAI's GPT-2 Ada AI Language Model To: Mario Marietto Cc: FreeBSD Mailing List , FreeBSD Mailing List , Yuri Victorovich Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Rspamd-Queue-Id: 4Q2sr65Xvyz3tGQ X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; TAGGED_FROM(0.00)[] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N On Fri, Apr 21, 2023 at 6:40=E2=80=AFAM Mario Marietto wrote: > > You don't need bhyve to make that,but only the Linuxulator. I don't think= the type of cpu will make any difference. I've used the Intel I9 cpu. I tr= ied FreeBSD 13.1 and I haven't found problems. For sure using python env is= tricky,but if you have the thinkering attitude,you will have some fun. I already have a VM allocated on it (the same host has 3 other VM's on it). I guess that is one thing I missed was the linuxulator (the linsuckslator is more like it) and as far tinkering goes it is fine to a point but not when it has taken *DAYS* away from paying projects (I am a freelancer). BTW I will be trying your specific command lines tomorrow (I must get back to paid work). P.S. The point of this project is to start a new project called babySpock that is a personal assistant for me and my programming partner/wife in all but legal detail. babySpock will hopefully be able to help with pair programming/design brainstorming, general clerical office tasks, be a halfway decent conversation partner (roughly on or near the level of chatGPT which inspired this project in the first place in order to increase the amount of "context" that it could store and to slice and dice context as needed to feed the more expensive models just relevant context as well use multiple models.... basically a DIY hobbyist AM (artificial mind with the final goal being artificial mature minds [AMM] instead of AGI due to the rule making paradox) lab that has to "earn its own way in life" (i.e. if it is not useful it will likely die from misuse). > > On Fri, Apr 21, 2023 at 12:26=E2=80=AFPM Aryeh Friedman wrote: >> >> The more I am fighting with it in linux (only thing there is docs for) >> the more obvious it just doesn't work on >> >> On Fri, Apr 21, 2023 at 6:19=E2=80=AFAM Mario Marietto wrote: >> > >> > Can't you install pytorch using the linux miniconda installer like bel= ow ? >> > >> > # fetch https://gist.githubusercontent.com/shkhln/40ef290463e78fb2b000= 0c60f4ad797e/raw/f640983249607e38af405c95c457ce4afc85c608/uvm_ioctl_overrid= e.c >> > >> > # /compat/ubuntu/bin/gcc --sysroot=3D/compat/ubuntu -m64 -std=3Dc99 -W= all -ldl -fPIC -shared -o dummy-uvm.so uvm_ioctl_override.c >> > >> > # pkg install linux-miniconda-installer >> > # miniconda-installer >> > # bash >> > # source /home/marietto/miniconda3/etc/profile.d/conda.sh >> > # conda activate >> > >> > (base) # conda activate pytorch >> > >> Will this work a bhyve on an AMD Ryzen 5 host? After playing with it >> in several linux instances I always get stuck when it can't find a >> compatible version >> >> -- >> Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org > > > > -- > Mario. --=20 Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org From nobody Fri Apr 21 12:30:30 2023 X-Original-To: freebsd-hackers@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 4Q2v5T0PBKz46MNF; Fri, 21 Apr 2023 12:31:09 +0000 (UTC) (envelope-from marietto2008@gmail.com) Received: from mail-yw1-x1130.google.com (mail-yw1-x1130.google.com [IPv6:2607:f8b0:4864:20::1130]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Q2v5R3xShz421Q; Fri, 21 Apr 2023 12:31:07 +0000 (UTC) (envelope-from marietto2008@gmail.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20221208 header.b="JKF+6v/P"; spf=pass (mx1.freebsd.org: domain of marietto2008@gmail.com designates 2607:f8b0:4864:20::1130 as permitted sender) smtp.mailfrom=marietto2008@gmail.com; dmarc=pass (policy=none) header.from=gmail.com Received: by mail-yw1-x1130.google.com with SMTP id 00721157ae682-54f8d59a8a9so18902807b3.0; Fri, 21 Apr 2023 05:31:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1682080267; x=1684672267; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=p0ULUHHGYhNxFYEUXDyU8Hzzpd++zJK4tB5OuP7DD9U=; b=JKF+6v/PJ+unPoHBL23xLNp/tsuQMpIgCvJSTTrgtKSh0O/nyfnHAXN8vkekRmi2I2 ExMs1mlRU3k1vSS2sWp1adlQ0WB1iwIGsFvHGxqW3SLabAqf4kHw5TXqKR3sKQUaf6By 8Fr+gkKaThk0rMmCyccOFrJ+pcBclzgLxjAymwkY7wPZT5KK2VO/vPai3JMmhQ2C4CtK xo8yOyyyw64ZF1GJbxBLkHvk3skrHLI80HFM0SH94dLxER6KmhbONHwrD3l4mZwRNkPU nxYPyoOGweM4iRLjjf9piDBfcaFCXSQG5brCpXa29vSfS5JB7LSKc8Jxo3iLzraik+QO B/3A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1682080267; x=1684672267; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=p0ULUHHGYhNxFYEUXDyU8Hzzpd++zJK4tB5OuP7DD9U=; b=W6JOh97sS3vQCSwASsnOk8tufDCCA1Dz1BrW3m5n3sPXHYrTh8vKUI5u+SiCpKBsdf LebKZfSwk51Rg+zR0qf0KPq9TiANlvdCGi5jHK2apKI8WxpYs1LlKJ2lN/Z7URJ1bNO7 p+Kpe0UNLauR8nJHZp1cbxLDj3XblfwJlBEyz+Xoee1sVjjWWlqPwOYYhlQbqbKKYrB8 rJqw+nCfxt2VPxoNm79uLLmFBPR3KLkQUZi0gQpCE3XHkQjBW20VMTWKQS8fmSk46H4J Rp7cHTKf3gywsGGlm4PiEgOeZziH0nxT3QpXRTYrNxNj4DF0tjhEdVsA3BtsbI0mMWji /KGQ== X-Gm-Message-State: AAQBX9c8exKqd954wX15xVCE2zyqwz9p2C+DFsJj+lyCgDW8uRla0GHH M+Glc03j3T1XKI/Igt4GQNI9Z/HOiNhqT51yYg/DCRm4vAlDBQ== X-Google-Smtp-Source: AKy350aapNkXU9OnCwAe57qm2A4gYpE53Xd8fr+w4JrbMl/8nz+AR3sP0OyC8O36gq5v4e+tJXCWTtqGgBEwHbWh+Q4= X-Received: by 2002:a0d:fe03:0:b0:54b:fc6c:d220 with SMTP id o3-20020a0dfe03000000b0054bfc6cd220mr1444241ywf.15.1682080266414; Fri, 21 Apr 2023 05:31:06 -0700 (PDT) List-Id: Technical discussions relating to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-hackers List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-hackers@freebsd.org MIME-Version: 1.0 References: In-Reply-To: From: Mario Marietto Date: Fri, 21 Apr 2023 14:30:30 +0200 Message-ID: Subject: Re: Installing openAI's GPT-2 Ada AI Language Model To: Aryeh Friedman Cc: FreeBSD Mailing List , FreeBSD Mailing List , Yuri Victorovich Content-Type: multipart/alternative; boundary="000000000000c36d1205f9d7d421" X-Spamd-Result: default: False [-3.74 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-0.999]; NEURAL_HAM_SHORT(-0.74)[-0.736]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36:c]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20221208]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[4]; FREEMAIL_FROM(0.00)[gmail.com]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TAGGED_RCPT(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::1130:from]; BLOCKLISTDE_FAIL(0.00)[2607:f8b0:4864:20::1130:server fail]; ARC_NA(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim]; RCVD_TLS_LAST(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; TO_DN_ALL(0.00)[]; MID_RHS_MATCH_FROMTLD(0.00)[]; MLMMJ_DEST(0.00)[freebsd-hackers@freebsd.org,freebsd-questions@freebsd.org]; FREEMAIL_TO(0.00)[gmail.com]; MIME_TRACE(0.00)[0:+,1:+,2:~]; FROM_EQ_ENVFROM(0.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; FREEMAIL_ENVFROM(0.00)[gmail.com]; RCVD_COUNT_TWO(0.00)[2] X-Rspamd-Queue-Id: 4Q2v5R3xShz421Q X-Spamd-Bar: --- X-ThisMailContainsUnwantedMimeParts: N --000000000000c36d1205f9d7d421 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable If you don't want to use the GPU,the commands should be more or less the following : sudo touch /usr/local/etc/rc.d/ubuntu && chmod +x /usr/local/etc/rc.d/ubunt= u # Make it have this content: #!/bin/sh # # PROVIDE: ubuntu # REQUIRE: archdep mountlate # KEYWORD: nojail # # This is a modified version of /etc/rc.d/linux # Based on the script by mrclksr: # https://github.com/mrclksr/linux-browser-installer/blob/main/rc.d/ubuntu.= in # . /etc/rc.subr name=3D"ubuntu" desc=3D"Enable Ubuntu chroot, and Linux ABI" rcvar=3D"ubuntu_enable" start_cmd=3D"${name}_start" stop_cmd=3D":" unmounted() { [ `stat -f "%d" "$1"` =3D=3D `stat -f "%d" "$1/.."` -a \ `stat -f "%i" "$1"` !=3D `stat -f "%i" "$1/.."` ] } ubuntu_start() { local _emul_path _tmpdir load_kld -e 'linux(aout|elf)' linux case `sysctl -n hw.machine_arch` in amd64) load_kld -e 'linux64elf' linux64 ;; esac if [ -x /compat/ubuntu/sbin/ldconfigDisabled ]; then _tmpdir=3D`mktemp -d -t linux-ldconfig` /compat/ubuntu/sbin/ldconfig -C ${_tmpdir}/ld.so.cache if ! cmp -s ${_tmpdir}/ld.so.cache /compat/ubuntu/etc/ld.so.cache; = then cat ${_tmpdir}/ld.so.cache > /compat/ubuntu/etc/ld.so.cache fi rm -rf ${_tmpdir} fi # Linux uses the pre-pts(4) tty naming scheme. load_kld pty # Handle unbranded ELF executables by defaulting to ELFOSABI_LINUX. if [ `sysctl -ni kern.elf64.fallback_brand` -eq "-1" ]; then sysctl kern.elf64.fallback_brand=3D3 > /dev/null fi if [ `sysctl -ni kern.elf32.fallback_brand` -eq "-1" ]; then sysctl kern.elf32.fallback_brand=3D3 > /dev/null fi sysctl compat.linux.emul_path=3D/compat/ubuntu _emul_path=3D"/compat/ubuntu" unmounted "${_emul_path}/dev" && (mount -o nocover -t devfs devfs "${_emul_path}/dev" || exit 1) unmounted "${_emul_path}/dev/fd" && (mount -o nocover,linrdlnk -t fdescfs fdescfs "${_emul_path}/dev/fd" || exit 1) unmounted "${_emul_path}/dev/shm" && (mount -o nocover,mode=3D1777 -t tmpfs tmpfs "${_emul_path}/dev/shm" || exit 1) unmounted "${_emul_path}/home" && (mount -t nullfs /home "${_emul_path}/home" || exit 1) unmounted "${_emul_path}/proc" && (mount -o nocover -t linprocfs linprocfs "${_emul_path}/proc" || exit 1) unmounted "${_emul_path}/sys" && (mount -o nocover -t linsysfs linsysfs "${_emul_path}/sys" || exit 1) unmounted "${_emul_path}/tmp" && (mount -t nullfs /tmp "${_emul_path}/tmp" || exit 1) unmounted /dev/fd && (mount -o nocover -t fdescfs fdescfs /dev/fd || ex= it 1) unmounted /proc && (mount -o nocover -t procfs procfs /proc || exit 1) true } load_rc_config $name run_rc_command "$1" sysrc ubuntu_enable=3DYES # Create necessary mount points for a working Linuxulator: mkdir -p {/compat/ubuntu/dev/fd,/compat/ubuntu/dev/shm,/compat/ubuntu/home,= /compat/ubuntu/tmp,/compat/ubuntu/proc,/compat/ubuntu/sys} # Start Ubuntu service: service ubuntu start # Install needed packages: pkg install debootstrap pulseaudio # Install Ubuntu 20.04 into /compat/ubuntu: debootstrap --arch=3Damd64 --no-check-gpg focal /compat/ubuntu # Restart Ubuntu service to make sure everything is properly mounted: service ubuntu restart # Fix broken symlink: cd /compat/ubuntu/lib64/ && rm ./ld-linux-x86-64.so.2 ; ln -s ../lib/x86_64-linux-gnu/ld-2.31.so ld-linux-x86-64.so.2 # Chroot into your Linux environment: chroot /compat/ubuntu /bin/bash # Set correct timezone inside your chroot: printf "%b\n" "0.0 0 0.0\n0\nUTC" > /etc/adjtime sudo dpkg-reconfigure tzdata # For some reason sudo is necessary here, otherwise it fails. # Fix APT package manager: printf "APT::Cache-Start 251658240;" > /etc/apt/apt.conf.d/00aptitude # Enable more repositories: printf "deb http://archive.ubuntu.com/ubuntu/ focal main restricted universe multiverse" > /etc/apt/sources.list # Install required programs: apt update ; apt install -y apt-transport-https curl fonts-symbola gnupg pulseaudio build-essential gcc gfortran # Exit out of chroot exit # Fix x86_64-linux-gnu libraries path between ubuntu and freebsd cp -r /compat/ubuntu/usr/lib/x86_64-linux-gnu /lib --> Installing PyTorch and your chatgpt github fork on FreeBSD # fetch https://gist.githubusercontent.com/shkhln/40ef290463e78fb2b0000c60f= 4ad797e/raw/f640983249607e38af405c95c457ce4afc85c608/uvm_ioctl_override.c # /compat/ubuntu/bin/gcc --sysroot=3D/compat/ubuntu -m64 -std=3Dc99 -Wall -ldl -fPIC -shared -o dummy-uvm.so uvm_ioctl_override.c # pkg install linux-miniconda-installer # miniconda-installer # bash # source /home/marietto/miniconda3/etc/profile.d/conda.sh # conda activate (base) # conda activate pytorch (pytorch) # conda activate (base) # conda activate (base) # git clone your chatgpt github fork On Fri, Apr 21, 2023 at 1:34=E2=80=AFPM Aryeh Friedman wrote: > On Fri, Apr 21, 2023 at 6:40=E2=80=AFAM Mario Marietto > wrote: > > > > You don't need bhyve to make that,but only the Linuxulator. I don't > think the type of cpu will make any difference. I've used the Intel I9 cp= u. > I tried FreeBSD 13.1 and I haven't found problems. For sure using python > env is tricky,but if you have the thinkering attitude,you will have some > fun. > > I already have a VM allocated on it (the same host has 3 other VM's on > it). I guess that is one thing I missed was the linuxulator (the > linsuckslator is more like it) and as far tinkering goes it is fine to > a point but not when it has taken *DAYS* away from paying projects (I > am a freelancer). > > BTW I will be trying your specific command lines tomorrow (I must get > back to paid work). > > P.S. The point of this project is to start a new project called > babySpock that is a personal assistant for me and my programming > partner/wife in all but legal detail. babySpock will hopefully be > able to help with pair programming/design brainstorming, general > clerical office tasks, be a halfway decent conversation partner > (roughly on or near the level of chatGPT which inspired this project > in the first place in order to increase the amount of "context" that > it could store and to slice and dice context as needed to feed the > more expensive models just relevant context as well use multiple > models.... basically a DIY hobbyist AM (artificial mind with the final > goal being artificial mature minds [AMM] instead of AGI due to the > rule making paradox) lab that has to "earn its own way in life" (i.e. > if it is not useful it will likely die from misuse). > > > > > On Fri, Apr 21, 2023 at 12:26=E2=80=AFPM Aryeh Friedman < > aryeh.friedman@gmail.com> wrote: > >> > >> The more I am fighting with it in linux (only thing there is docs for) > >> the more obvious it just doesn't work on > >> > >> On Fri, Apr 21, 2023 at 6:19=E2=80=AFAM Mario Marietto > wrote: > >> > > >> > Can't you install pytorch using the linux miniconda installer like > below ? > >> > > >> > # fetch > https://gist.githubusercontent.com/shkhln/40ef290463e78fb2b0000c60f4ad797= e/raw/f640983249607e38af405c95c457ce4afc85c608/uvm_ioctl_override.c > >> > > >> > # /compat/ubuntu/bin/gcc --sysroot=3D/compat/ubuntu -m64 -std=3Dc99 = -Wall > -ldl -fPIC -shared -o dummy-uvm.so uvm_ioctl_override.c > >> > > >> > # pkg install linux-miniconda-installer > >> > # miniconda-installer > >> > # bash > >> > # source /home/marietto/miniconda3/etc/profile.d/conda.sh > >> > # conda activate > >> > > >> > (base) # conda activate pytorch > >> > > >> Will this work a bhyve on an AMD Ryzen 5 host? After playing with it > >> in several linux instances I always get stuck when it can't find a > >> compatible version > >> > >> -- > >> Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org > > > > > > > > -- > > Mario. > > > > -- > Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org > --=20 Mario. --000000000000c36d1205f9d7d421 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 
If you don't want to use the GPU,the=
 commands should be more or less the following :


sudo touch /usr=
/local/etc/rc.d/ubuntu && chmod +x /usr/local/etc/rc.d/ubuntu

# Make it have this content:

#!/bin/sh
#
# PROVIDE: ubuntu
# REQUIRE: archdep mountlate
# KEYWORD: nojail
#
# This is a modified version of /etc/rc.d/linux
# Based on the script by mrclksr:
# https://github.com/mrclksr/linux-browser-installer/blob/main=
/rc.d/ubuntu.in
#
. /etc/rc.subr

name=3D"ubuntu"
desc=3D"Enable Ubuntu chroot, and Linux ABI"
rcvar=3D"ubuntu_enable"
start_cmd=3D"${name}_start"
stop_cmd=3D":"

unmounted()
{
    [ `stat -f "%d" "$1"` =3D=3D `stat -f "%d"=
; "$1/.."` -a \
      `stat -f "%i" "$1"` !=3D `stat -f "%i" =
"$1/.."` ]
}

ubuntu_start()
{
    local _emul_path _tmpdir

    load_kld -e 'linux(aout|elf)' linux
    case `sysctl -n hw.machine_arch` in
    amd64)
        load_kld -e 'linux64elf' linux64
        ;;
    esac
    if [ -x /compat/ubuntu/sbin/ldconfigDisabled ]; then
        _tmpdir=3D`mktemp -d -t linux-ldconfig`
        /compat/ubuntu/sbin/ldconfig -C ${_tmpdir}/ld.so.cache
        if ! cmp -s ${_tmpdir}/ld.so.cache /compat/ubuntu/etc/ld.so.cache; =
then
            cat ${_tmpdir}/ld.so.cache > /compat/ubuntu/etc/ld.so.cache
        fi
        rm -rf ${_tmpdir}
    fi

    # Linux uses the pre-pts(4) tty naming scheme.
    load_kld pty

    # Handle unbranded ELF executables by defaulting to ELFOSABI_LINUX.
    if [ `sysctl -ni kern.elf64.fallback_brand` -eq "-1" ]; then
        sysctl kern.elf64.fallback_brand=3D3 > /dev/null
    fi

    if [ `sysctl -ni kern.elf32.fallback_brand` -eq "-1" ]; then
        sysctl kern.elf32.fallback_brand=3D3 > /dev/null
    fi
    sysctl compat.linux.emul_path=3D/compat/ubuntu

    _emul_path=3D"/compat/ubuntu"
    unmounted "${_emul_path}/dev" && (mount -o nocover -t=
 devfs devfs "${_emul_path}/dev" || exit 1)
    unmounted "${_emul_path}/dev/fd" && (mount -o nocover=
,linrdlnk -t fdescfs fdescfs "${_emul_path}/dev/fd" || exit 1)
    unmounted "${_emul_path}/dev/shm" && (mount -o nocove=
r,mode=3D1777 -t tmpfs tmpfs "${_emul_path}/dev/shm" || exit 1)
    unmounted "${_emul_path}/home" && (mount -t nullfs /h=
ome "${_emul_path}/home" || exit 1)
    unmounted "${_emul_path}/proc" && (mount -o nocover -=
t linprocfs linprocfs "${_emul_path}/proc" || exit 1)
    unmounted "${_emul_path}/sys" && (mount -o nocover -t=
 linsysfs linsysfs "${_emul_path}/sys" || exit 1)
    unmounted "${_emul_path}/tmp" && (mount -t nullfs /tm=
p "${_emul_path}/tmp" || exit 1)
    unmounted /dev/fd && (mount -o nocover -t fdescfs fdescfs /dev/=
fd || exit 1)
    unmounted /proc && (mount -o nocover -t procfs procfs /proc || =
exit 1)
    true
}

load_rc_config $name
run_rc_command "$1"

sysrc ubuntu_enable=3DYES

# Create necessary mount points for a working Linuxulator:
mkdir -p {/compat/ubuntu/dev/fd,/compat/ubuntu/dev/shm,/compat/ubuntu/home,=
/compat/ubuntu/tmp,/compat/ubuntu/proc,/compat/ubuntu/sys}

# Start Ubuntu service:
service ubuntu start

# Install needed packages:
pkg install debootstrap pulseaudio

# Install Ubuntu 20.04 into /compat/ubuntu:
debootstrap --arch=3Damd64 --no-check-gpg focal /compat/ubuntu

# Restart Ubuntu service to make sure everything is properly mounted:
service ubuntu restart

# Fix broken symlink:
cd /compat/ubuntu/lib64/ && rm ./ld-linux-x86-64.so.2 ; ln -s ../li=
b/x86_64-linux-gnu/ld-2.31.so ld-linux-x8=
6-64.so.2

# Chroot into your Linux environment:
chroot /compat/ubuntu /bin/bash

# Set correct timezone inside your chroot:
printf "%b\n" "0.0 0 0.0\n0\nUTC" > /etc/adjtime
sudo dpkg-reconfigure tzdata # For some reason sudo is necessary here, othe=
rwise it fails.

# Fix APT package manager:
printf "APT::Cache-Start 251658240;" > /etc/apt/apt.conf.d/00a=
ptitude

# Enable more repositories:
printf "deb http://archi=
ve.ubuntu.com/ubuntu/ focal main restricted universe multiverse" &=
gt; /etc/apt/sources.list

# Install required programs:

apt update ; apt install -y apt-transport-https curl fonts-symbola gnup=
g pulseaudio build-essential gcc gfortran

# Exit out of chroot
exit

# Fix x86_64-linux-gnu libraries path between ubuntu and freebsd
cp -r /compat/ubuntu/usr/lib/x86_64-linux-gnu /lib


--> Installing PyTorch and your chatgpt github fork on FreeBSD


# fetch https://gist.githubusercontent.com/shkhln/40ef290463e78fb2b0000c60f4ad797e=
/raw/f640983249607e38af405c95c457ce4afc85c608/uvm_ioctl_override.c

# /compat/ubuntu/bin/gcc --sysroot=3D/compat/ubuntu -m64 -std=3Dc99 -Wall -=
ldl -fPIC -shared -o dummy-uvm.so uvm_ioctl_override.c

# pkg install linux-miniconda-installer
# miniconda-installer
# bash
# source /home/marietto/miniconda3/etc/profile.d/conda.sh
# conda activate

(base) # conda activate pytorch

(pytorch) # conda activate

(base) # conda activate

(base) # git clone your chatgpt github fork

On Fri, Apr 21, 2023 at 1:34=E2=80=AFPM Aryeh Friedman <aryeh.friedman@gmail.com> w= rote:
On Fri, Ap= r 21, 2023 at 6:40=E2=80=AFAM Mario Marietto <marietto2008@gmail.com> wrote:
>
> You don't need bhyve to make that,but only the Linuxulator. I don&= #39;t think the type of cpu will make any difference. I've used the Int= el I9 cpu. I tried FreeBSD 13.1 and I haven't found problems. For sure = using python env is tricky,but if you have the thinkering attitude,you will= have some fun.

I already have a VM allocated on it (the same host has 3 other VM's on<= br> it).=C2=A0 =C2=A0I guess that is one thing I missed was the linuxulator (th= e
linsuckslator is more like it) and as far tinkering goes it is fine to
a point but not when it has taken *DAYS* away from paying projects (I
am a freelancer).

BTW I will be trying your specific command lines tomorrow (I must get
back to paid work).

P.S. The point of this project is to start a new project called
babySpock that is a personal assistant for me and my programming
partner/wife in all but legal detail.=C2=A0 babySpock will hopefully be
able to help with pair programming/design brainstorming, general
clerical office tasks, be a halfway decent conversation partner
(roughly on or near the level of chatGPT which inspired this project
in the first place in order to increase the amount of "context" t= hat
it could store and to slice and dice context as needed to feed the
more expensive models just relevant context as well use multiple
models.... basically a DIY hobbyist AM (artificial mind with the final
goal being artificial mature minds [AMM] instead of AGI due to the
rule making paradox) lab that has to "earn its own way in life" (= i.e.
if it is not useful it will likely die from misuse).

>
> On Fri, Apr 21, 2023 at 12:26=E2=80=AFPM Aryeh Friedman <aryeh.friedman@gmail.co= m> wrote:
>>
>> The more I am fighting with it in linux (only thing there is docs = for)
>> the more obvious it just doesn't work on
>>
>> On Fri, Apr 21, 2023 at 6:19=E2=80=AFAM Mario Marietto <marietto2008@gmail.com= > wrote:
>> >
>> > Can't you install pytorch using the linux miniconda insta= ller like below ?
>> >
>> > # fetch https://gist.= githubusercontent.com/shkhln/40ef290463e78fb2b0000c60f4ad797e/raw/f64098324= 9607e38af405c95c457ce4afc85c608/uvm_ioctl_override.c
>> >
>> > # /compat/ubuntu/bin/gcc --sysroot=3D/compat/ubuntu -m64 -std= =3Dc99 -Wall -ldl -fPIC -shared -o dummy-uvm.so uvm_ioctl_override.c
>> >
>> > # pkg install linux-miniconda-installer
>> > # miniconda-installer
>> > # bash
>> > # source /home/marietto/miniconda3/etc/profile.d/conda.sh
>> > # conda activate
>> >
>> > (base) # conda activate pytorch
>> >
>> Will this work a bhyve on an AMD Ryzen 5 host?=C2=A0 =C2=A0After p= laying with it
>> in several linux instances I always get stuck when it can't fi= nd a
>> compatible version
>>
>> --
>> Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org=
>
>
>
> --
> Mario.



--
Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org


--
Mario.
--000000000000c36d1205f9d7d421-- From nobody Fri Apr 21 13:41:20 2023 X-Original-To: freebsd-hackers@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 4Q2wfb3ZNXz46RNv; Fri, 21 Apr 2023 13:41:27 +0000 (UTC) (envelope-from verm@darkbeer.org) Received: from mx.coeval.ca (mx.coeval.ca [184.75.211.21]) (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 4Q2wfZ56n1z4CQr; Fri, 21 Apr 2023 13:41:26 +0000 (UTC) (envelope-from verm@darkbeer.org) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=darkbeer.org header.s=mail header.b=eUtXgzM0; spf=pass (mx1.freebsd.org: domain of verm@darkbeer.org designates 184.75.211.21 as permitted sender) smtp.mailfrom=verm@darkbeer.org; dmarc=none Received: from mx.darkbeer.org (unknown [192.168.211.20]) by mx.coeval.ca (Postfix) with ESMTP id B59AF43605C; Fri, 21 Apr 2023 13:41:20 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=darkbeer.org; s=mail; t=1682084480; bh=w7FD2QITbIitxb2xiUM7IPOoVwjcvugNfhCj30MIDZ4=; h=Date:From:To:Subject:References:In-Reply-To; b=eUtXgzM0D7nmMkDjr16+HQVxLhRaoAVTXeKmlbbsOAQ6ci9l/7T3GdkZxOgenXg9v pp3ZDSn6mOrzOIAx18hXqB0hSdpb6Xhw+UHimF8HtGZ9JYlX7V/tTQm6yO5ZiN1bae +c0SVgDcYdqZ9E0mgcAHh64tiwdRUuSBxQ9hrsGA= Received: by mx.darkbeer.org (Postfix, from userid 1001) id B363E470C23; Fri, 21 Apr 2023 13:41:20 +0000 (UTC) Date: Fri, 21 Apr 2023 13:41:20 +0000 From: Amar Takhar To: questions@freebsd.org, FreeBSD Mailing List Subject: Re: Installing openAI's GPT-2 Ada AI Language Model Message-ID: <20230421134120.GA12251@darkbeer.org> Mail-Followup-To: questions@freebsd.org, FreeBSD Mailing List References: List-Id: Technical discussions relating to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-hackers List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-hackers@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Spamd-Result: default: False [-3.48 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.98)[-0.978]; R_SPF_ALLOW(-0.20)[+ip4:184.75.211.21]; R_DKIM_ALLOW(-0.20)[darkbeer.org:s=mail]; MIME_GOOD(-0.10)[text/plain]; MLMMJ_DEST(0.00)[freebsd-hackers@freebsd.org,questions@freebsd.org]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; RCPT_COUNT_TWO(0.00)[2]; RCVD_TLS_LAST(0.00)[]; DKIM_TRACE(0.00)[darkbeer.org:+]; ARC_NA(0.00)[]; ASN(0.00)[asn:32489, ipnet:184.75.211.0/24, country:CA]; FROM_HAS_DN(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; TO_DN_SOME(0.00)[]; DMARC_NA(0.00)[darkbeer.org]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MID_RHS_MATCH_FROM(0.00)[] X-Rspamd-Queue-Id: 4Q2wfZ56n1z4CQr X-Spamd-Bar: --- X-ThisMailContainsUnwantedMimeParts: N I have a tutorial I wrote on how to setup PyTorch on FreeBSD with Stable Diffusion. https://github.com/verm/freebsd-stable-diffusion There are some issues with getting PyTorch working on FreeBSD and it's kind of a moving target I had it working once but it quickly broke this was years ago using the Linuxlator it's been rock solid for years. Another thing to note is the miniconda-installer script is hardcoded to an old version of Python you'll have to edit line 56 in the script and change it to 3.9 or 3.10. Not sure what to do about this yet I haven't had a chance to email the maintainer. I'd recommend going this route. Amar. From nobody Fri Apr 21 20:06:43 2023 X-Original-To: freebsd-hackers@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 4Q35CS3Zvsz46qFn; Fri, 21 Apr 2023 20:07:00 +0000 (UTC) (envelope-from aryeh.friedman@gmail.com) Received: from mail-ed1-x535.google.com (mail-ed1-x535.google.com [IPv6:2a00:1450:4864:20::535]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Q35CR1pkrz3MDZ; Fri, 21 Apr 2023 20:06:59 +0000 (UTC) (envelope-from aryeh.friedman@gmail.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20221208 header.b=ZerseuHc; spf=pass (mx1.freebsd.org: domain of aryeh.friedman@gmail.com designates 2a00:1450:4864:20::535 as permitted sender) smtp.mailfrom=aryeh.friedman@gmail.com; dmarc=pass (policy=none) header.from=gmail.com Received: by mail-ed1-x535.google.com with SMTP id 4fb4d7f45d1cf-506b20efd4cso3474922a12.3; Fri, 21 Apr 2023 13:06:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1682107615; x=1684699615; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=MjCDBvU1JfVGOjXjvI7MmMWQiU2126FYw62smAeVkYc=; b=ZerseuHcUOh4L0Sn42N7Hq5h8WPUAmBaJ1Rsc8EKYKkpW3HlhNphZS5na60ZiWr/3m 5D3x5EZPGq/0Q1Nd8s7dxTfaT3rsAjJXtT0xKDBv+zXRgMeduOx1BLV8/LSZFDhSbKHi 9TBwK4eRjwkcZCkCpgpeEcNpW0WQCUtYhD7BdsekTzyN5FYkFHNfB/i75cK2x9MLe50w L5+UNDLa14C8Fuzn6amwiqdSfjgMSrnmzQWj242+2kW00XT909LG3ySt++GCVlh0LF6g uhBkAiZkg72zJeqLP0K5fRcJFn3FEhB/onODQk5fyXi6mhUQNDwQUhPWm8H9uRYGE5Wy JVPw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1682107615; x=1684699615; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=MjCDBvU1JfVGOjXjvI7MmMWQiU2126FYw62smAeVkYc=; b=O59s2fd2Ts5FisW5c/pPkVw3QSf+UiRVy14ioY5kN1u6TJrQoQAfRiPfu6tQxkqufi v3qaIBzeI8csgIKQvBh5SD71AU41myP2ZIPNhv/V+72ai0NPL6wEMmFwZuKiu+i55sPi ohmvTor0JsEmjcwwf7Jvt2C53hsLk4eKfv5R99BETfld3oVfJyscjhVT6JN/hfWyhKN+ eqIpm/wrt6W8ExZXEFOD2tX3FS6FW8ee/BVrzMDzzOco9HoqC50grHUquOqxWVAP1Ia8 RXSgddAbFudLQqA3gdNMKbLKTJp2vFd+xS9y01Pbnpnzf/q/uts+5U31kOdtPCWqRpox qYLw== X-Gm-Message-State: AAQBX9dYcHA9Kk7TFapLp8R+NxwSu7Pn4q4yCgYZkKpxmpQp/s85VqJg 8hdMOEk/4MPYpcpJQakJu39lJLqHk2y6GrOW9f91I+jS X-Google-Smtp-Source: AKy350a5gcuP6aP9kIxLxwfKz/dJfUxf+RYDI+uiwZY6g1hMUgLVIxdb+gDcm8zLWt/8qtJeud1ktP9/0NimFmX4UtI= X-Received: by 2002:aa7:da8e:0:b0:506:ad45:49b1 with SMTP id q14-20020aa7da8e000000b00506ad4549b1mr5931225eds.42.1682107615280; Fri, 21 Apr 2023 13:06:55 -0700 (PDT) List-Id: Technical discussions relating to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-hackers List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-hackers@freebsd.org MIME-Version: 1.0 From: Aryeh Friedman Date: Fri, 21 Apr 2023 16:06:43 -0400 Message-ID: Subject: How do I get a new freebsd- mailing list made To: FreeBSD chat , FreeBSD Mailing List , FreeBSD Mailing List Content-Type: text/plain; charset="UTF-8" X-Spamd-Result: default: False [-4.00 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-0.996]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20221208]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36]; MIME_GOOD(-0.10)[text/plain]; RCVD_IN_DNSWL_NONE(0.00)[2a00:1450:4864:20::535:from]; RCVD_TLS_LAST(0.00)[]; MLMMJ_DEST(0.00)[freebsd-chat@freebsd.org,freebsd-questions@freebsd.org,freebsd-hackers@freebsd.org]; MIME_TRACE(0.00)[0:+]; FROM_EQ_ENVFROM(0.00)[]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; FREEMAIL_ENVFROM(0.00)[gmail.com]; DKIM_TRACE(0.00)[gmail.com:+]; MID_RHS_MATCH_FROMTLD(0.00)[]; TAGGED_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; ARC_NA(0.00)[]; TO_DN_ALL(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; TO_MATCH_ENVRCPT_ALL(0.00)[]; FREEMAIL_FROM(0.00)[gmail.com]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim]; RCVD_COUNT_TWO(0.00)[2] X-Rspamd-Queue-Id: 4Q35CR1pkrz3MDZ X-Spamd-Bar: --- X-ThisMailContainsUnwantedMimeParts: N It appears there is a core of people who are interested in various DIY AI (using existing ANN's like GPT-2) on FreeBSD. As it turns out getting this up and running is "fun" to say the least and I suspect the number of interested people will grow. So how do I get such a list made on the freebsd.org mailing lists? (something like freebsd-ai@ perhaps) -- Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org From nobody Fri Apr 21 20:33:58 2023 X-Original-To: freebsd-hackers@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 4Q35ps3Jljz46rg0; Fri, 21 Apr 2023 20:34:13 +0000 (UTC) (envelope-from aryeh.friedman@gmail.com) Received: from mail-ed1-x529.google.com (mail-ed1-x529.google.com [IPv6:2a00:1450:4864:20::529]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Q35pq4hlBz4SP6; Fri, 21 Apr 2023 20:34:11 +0000 (UTC) (envelope-from aryeh.friedman@gmail.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20221208 header.b=NQ03rj3f; spf=pass (mx1.freebsd.org: domain of aryeh.friedman@gmail.com designates 2a00:1450:4864:20::529 as permitted sender) smtp.mailfrom=aryeh.friedman@gmail.com; dmarc=pass (policy=none) header.from=gmail.com Received: by mail-ed1-x529.google.com with SMTP id 4fb4d7f45d1cf-504eac2f0b2so3547453a12.3; Fri, 21 Apr 2023 13:34:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1682109250; x=1684701250; h=content-transfer-encoding:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=YkDas9gqXYEflyNNKJCQyinCuEWwOugo2fZYapa9u6c=; b=NQ03rj3fmdeXV0Y3+v4gCmNIRtLb3rgAGFevlTYA7Sb9VBbP+707xfFmnKU9uHz+C/ NTFSLFCsCz0zLYHFkRaI2INt1u4GzgPIaYpIGn6GC8tcDUxVrMT7i/fM4+Azf9uFyWUE DajTJoofVwBjUWUE4kwPxITulDk/1SxtQRkhH1yLE4HjK/qO1mUPrRQH89RaZKEiWp4H 6+ocZ3oydeOW3t0qFvUOl6NFJRtI460dje0Wph/lxvsG52C9WCBqFLdl6SH3/OroLB63 aR0+H7LRgh0W28eRiPCh/HU6o4o6ASjuml9aN0733/hxQ/+8yc0/BZX4VDxKpFYYZWWo WY2g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1682109250; x=1684701250; h=content-transfer-encoding:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=YkDas9gqXYEflyNNKJCQyinCuEWwOugo2fZYapa9u6c=; b=KraI7cYO80cJGpWfaQ8DRqTLrP92IMPL2yTHQUA1QceQIoXn8S/vDatuOIg0j68yKI xr85AlRUp9aCy64/kQW8RfePoxl7Suyn+nYRjknSeFzkiV/Wa4+6lrvYTxrLZFkwwaiR sQ828Xws8XwJjnNmPGLQZJtFloFe4EgYaWu7Fb+otWBTIsseiQz7L20G9cFMLbcMMm7g O+9sXenImzIKq6X7sUZMF0//mCzqhVhcQj5+12dojb3CrSzlWWf0ihEN7YE1yjtaTOhF 90IjhqmAolXbzhaGpTqwFmszBralgUr5NdqT5np5tYhd+isR219B/sKjHwuLxnUPsn/2 jd/A== X-Gm-Message-State: AAQBX9cOCml4J9pw+ftq7x5yT3f8/agA08PAn9XOC6xolkQ1amDe4nSO n0kmLbUwyIJVFo1y83yntFvcZdXO0aod5CNFJ+2s1NIm X-Google-Smtp-Source: AKy350bTrwbE9ByfS0ufXYxQzFsyxoyNaQVVEvbe3dw1FIgCtk7qYCe1HPRX8QK4JeUXclFbd098A6y19G/BEjGdrck= X-Received: by 2002:a05:6402:1849:b0:504:b313:5898 with SMTP id v9-20020a056402184900b00504b3135898mr6304528edy.27.1682109249852; Fri, 21 Apr 2023 13:34:09 -0700 (PDT) List-Id: Technical discussions relating to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-hackers List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-hackers@freebsd.org MIME-Version: 1.0 References: <20230421134120.GA12251@darkbeer.org> In-Reply-To: <20230421134120.GA12251@darkbeer.org> From: Aryeh Friedman Date: Fri, 21 Apr 2023 16:33:58 -0400 Message-ID: Subject: Re: Installing openAI's GPT-2 Ada AI Language Model To: questions@freebsd.org, FreeBSD Mailing List Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Spamd-Result: default: False [-3.99 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.99)[-0.993]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20221208]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36:c]; MIME_GOOD(-0.10)[text/plain]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; TO_DN_SOME(0.00)[]; BLOCKLISTDE_FAIL(0.00)[2a00:1450:4864:20::529:server fail]; ARC_NA(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[2a00:1450:4864:20::529:from]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; MLMMJ_DEST(0.00)[questions@freebsd.org,freebsd-hackers@freebsd.org]; DKIM_TRACE(0.00)[gmail.com:+]; MID_RHS_MATCH_FROMTLD(0.00)[]; FREEMAIL_FROM(0.00)[gmail.com]; TAGGED_FROM(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; RCVD_TLS_LAST(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; MIME_TRACE(0.00)[0:+]; RCVD_COUNT_TWO(0.00)[2] X-Rspamd-Queue-Id: 4Q35pq4hlBz4SP6 X-Spamd-Bar: --- X-ThisMailContainsUnwantedMimeParts: N On Fri, Apr 21, 2023 at 9:41=E2=80=AFAM Amar Takhar wro= te: > > I have a tutorial I wrote on how to setup PyTorch on FreeBSD with Stable > Diffusion. > > https://github.com/verm/freebsd-stable-diffusion Thanks for the pointer but it assumes I have a (nvidia) GPU available. Since this is a VM on bhyve there is no currently working GPU passthrough for it. (I do use a nVidia Geforce GT 1030 with nvidia-modeselect but it is not passable to the VM and due to hardware resources don't have a physical machine I can assign to the task). I have gotten as far as the part in the blog as installing pyTorch and keep getting "no compatible versions found" out of pip and when I search for any suitable ones it seems to not be there. Thus I have to revert to building pytorch from scratch and it blows up because the host/guest CPU is not Intel. > > There are some issues with getting PyTorch working on FreeBSD and it's ki= nd of a > moving target I had it working once but it quickly broke this was years a= go > using the Linuxlator it's been rock solid for years. > > Another thing to note is the miniconda-installer script is hardcoded to a= n old > version of Python you'll have to edit line 56 in the script and change it= to 3.9 > or 3.10. Not sure what to do about this yet I haven't had a chance to em= ail the > maintainer. > > I'd recommend going this route. > > > Amar. > --=20 Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org From nobody Fri Apr 21 21:37:08 2023 X-Original-To: freebsd-hackers@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 4Q37DB6HxYz46wLb; Fri, 21 Apr 2023 21:37:46 +0000 (UTC) (envelope-from marietto2008@gmail.com) Received: from mail-yb1-xb33.google.com (mail-yb1-xb33.google.com [IPv6:2607:f8b0:4864:20::b33]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Q37D94l2Mz45kR; Fri, 21 Apr 2023 21:37:45 +0000 (UTC) (envelope-from marietto2008@gmail.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20221208 header.b="FSYY/Vkp"; spf=pass (mx1.freebsd.org: domain of marietto2008@gmail.com designates 2607:f8b0:4864:20::b33 as permitted sender) smtp.mailfrom=marietto2008@gmail.com; dmarc=pass (policy=none) header.from=gmail.com Received: by mail-yb1-xb33.google.com with SMTP id 3f1490d57ef6-b92284f69ebso2893865276.3; Fri, 21 Apr 2023 14:37:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1682113064; x=1684705064; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=ghVmaqj7PTYJVEgmfrths/ch0MdNroWIQKDqup+a4jM=; b=FSYY/VkpKHZcOaIHaQDNKkwk25gpqMNp25Z7ECFpUyj5aPdcU4kiFzNEtVhVMd8r/o eaUDMN/lASDJ9w8Spdxy2iwBuU7Y/OBVYezzoS1jr/M9r4yJjYKiH/0qyO9sEyCiByuL mRJ/GMrC3ZwT1Bf2xWskrLGQBiEZ/GnL+Bd77JRlLT9vBIsiM+LwcbTLHW13UWZ0Kcdn iLGMSAZ7FqB0xwPKnVmq8O67sFi+MJYPCv7VgpjabCrniINv2tuZJwo9JWJvLKrWokKn DGzmUyyocHmnL++LPCPK55d0bRM1bck2dMLKlSz1n3mM5cpnuNQXTEuQ8nD73fjjBzpv 9voQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1682113064; x=1684705064; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=ghVmaqj7PTYJVEgmfrths/ch0MdNroWIQKDqup+a4jM=; b=hl3d7bBJRT9IC/cXudSHB7WeCnt03K8/dkHeNOZe/cMUFFzF/C7VRaITNE9/c7mXWO tStMXQscr9P/QdfWcxw9d4Nvka2p5O1Im/elC7YWRNlqqGP2B/dOuW86T0AHeIaSeZ2U OFxUY7/nWHswTYreHmGab/HDXVFqajgm8dPzidilVAES3GfSmUmsv8sPPrbsoQMtjSHq vwi+WEA+4mUMgr4zQA4aFq313FlVxwSHgVMuJ0T0q48ATSkm78+YGB+MDgax90a2aXkr ho2/awDyhlDZkpH4vejMByVQE4ri5F6I+Hk1q2rDDie592b+DXoXUroib5SYhDhmmFQX PWqg== X-Gm-Message-State: AAQBX9eGk5/ywPWUGd87uh8rTTxLhVl3xpc3Yfm+UV0HbJsQ81xnHJ2f 5p5iy1AE3iaRAzVtJ/GyTjtOVg5qNOrZOZyhAv4= X-Google-Smtp-Source: AKy350b7Z0tKp5vEkuNQrGFjUFI23bJLkvpvoEWswNJNr4AdzufyGe9M8garQKnFTi9ieIm1g5kEl8IwihtgDYFGdRY= X-Received: by 2002:a25:3252:0:b0:b8f:60cf:18cc with SMTP id y79-20020a253252000000b00b8f60cf18ccmr3863564yby.23.1682113064469; Fri, 21 Apr 2023 14:37:44 -0700 (PDT) List-Id: Technical discussions relating to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-hackers List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-hackers@freebsd.org MIME-Version: 1.0 References: <20230421134120.GA12251@darkbeer.org> In-Reply-To: From: Mario Marietto Date: Fri, 21 Apr 2023 23:37:08 +0200 Message-ID: Subject: Re: Installing openAI's GPT-2 Ada AI Language Model To: Aryeh Friedman Cc: questions@freebsd.org, FreeBSD Mailing List Content-Type: multipart/alternative; boundary="000000000000ae0bba05f9df7784" X-Spamd-Result: default: False [-4.00 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-0.997]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20221208]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; RCPT_COUNT_THREE(0.00)[3]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TAGGED_RCPT(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::b33:from]; ARC_NA(0.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; MLMMJ_DEST(0.00)[questions@freebsd.org,freebsd-hackers@freebsd.org]; DKIM_TRACE(0.00)[gmail.com:+]; MID_RHS_MATCH_FROMTLD(0.00)[]; FREEMAIL_FROM(0.00)[gmail.com]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim]; FREEMAIL_TO(0.00)[gmail.com]; RCVD_TLS_LAST(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; MIME_TRACE(0.00)[0:+,1:+,2:~]; RCVD_COUNT_TWO(0.00)[2] X-Rspamd-Queue-Id: 4Q37D94l2Mz45kR X-Spamd-Bar: --- X-ThisMailContainsUnwantedMimeParts: N --000000000000ae0bba05f9df7784 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 1) try to use the linuxulator instead of bhyve (try to remember what Albert Einstein tells about those people that want to solve a problem without changing their perspective : he does not spend nice words for those people) 2) actually an nvidia gpu can be passed-thru within linux (and within windows 11 if the gpu is amd) 3) the tutorial that we are suggesting may work even if you don't want to use your gpu 4) probably you should find the exact version of pytorch that it wants On Fri, Apr 21, 2023 at 10:34=E2=80=AFPM Aryeh Friedman wrote: > On Fri, Apr 21, 2023 at 9:41=E2=80=AFAM Amar Takhar w= rote: > > > > I have a tutorial I wrote on how to setup PyTorch on FreeBSD with Stabl= e > > Diffusion. > > > > https://github.com/verm/freebsd-stable-diffusion > > Thanks for the pointer but it assumes I have a (nvidia) GPU available. > Since this is a VM on bhyve there is no currently working GPU > passthrough for it. (I do use a nVidia Geforce GT 1030 with > nvidia-modeselect but it is not passable to the VM and due to hardware > resources don't have a physical machine I can assign to the task). > > I have gotten as far as the part in the blog as installing pyTorch and > keep getting "no compatible versions found" out of pip and when I > search for any suitable ones it seems to not be there. Thus I have > to revert to building pytorch from scratch and it blows up because the > host/guest CPU is not Intel. > > > > > There are some issues with getting PyTorch working on FreeBSD and it's > kind of a > > moving target I had it working once but it quickly broke this was years > ago > > using the Linuxlator it's been rock solid for years. > > > > Another thing to note is the miniconda-installer script is hardcoded to > an old > > version of Python you'll have to edit line 56 in the script and change > it to 3.9 > > or 3.10. Not sure what to do about this yet I haven't had a chance to > email the > > maintainer. > > > > I'd recommend going this route. > > > > > > Amar. > > > > > -- > Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org > > --=20 Mario. --000000000000ae0bba05f9df7784 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
1) try to use the linuxulator instead of bhyve (try t= o remember what Albert Einstein tells about those people that want to solve= a problem without changing their perspective : he does not spend nice word= s for those people)

2) actually an nvidia gpu = can be passed-thru within linux (and within windows 11 if the gpu is amd)

3) the tutorial that we are suggesting may work eve= n if you don't want to use your gpu

4) probabl= y you should find the exact version of pytorch that it wants
=

On Fri, Apr 21, 2023 at 10:34=E2=80=AFPM Aryeh Friedman <aryeh.friedman@gmail.com> wro= te:
On Fri, Apr = 21, 2023 at 9:41=E2=80=AFAM Amar Takhar <verm@darkbeer.org> wrote:
>
> I have a tutorial I wrote on how to setup PyTorch on FreeBSD with Stab= le
> Diffusion.
>
>=C2=A0 =C2=A0https://github.com/verm/freebsd-sta= ble-diffusion

Thanks for the pointer but it assumes I have a (nvidia) GPU available.
=C2=A0 Since this is a VM on bhyve there is no currently working GPU
passthrough for it.=C2=A0 (I do use a nVidia Geforce GT 1030 with
nvidia-modeselect but it is not passable to the VM and due to hardware
resources don't have a physical machine I can assign to the task).

I have gotten as far as the part in the blog as installing pyTorch and
keep getting "no compatible versions found" out of pip and when I=
search for any suitable ones it seems to not be there.=C2=A0 =C2=A0Thus I h= ave
to revert to building pytorch from scratch and it blows up because the
host/guest CPU is not Intel.

>
> There are some issues with getting PyTorch working on FreeBSD and it&#= 39;s kind of a
> moving target I had it working once but it quickly broke this was year= s ago
> using the Linuxlator it's been rock solid for years.
>
> Another thing to note is the miniconda-installer script is hardcoded t= o an old
> version of Python you'll have to edit line 56 in the script and ch= ange it to 3.9
> or 3.10.=C2=A0 Not sure what to do about this yet I haven't had a = chance to email the
> maintainer.
>
> I'd recommend going this route.
>
>
> Amar.
>


--
Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org



--
Mario.
--000000000000ae0bba05f9df7784-- From nobody Fri Apr 21 22:01:45 2023 X-Original-To: freebsd-hackers@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 4Q37m64JRDz1HCGv; Fri, 21 Apr 2023 22:01:58 +0000 (UTC) (envelope-from aryeh.friedman@gmail.com) Received: from mail-ed1-x536.google.com (mail-ed1-x536.google.com [IPv6:2a00:1450:4864:20::536]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Q37m61nfNz3rDk; Fri, 21 Apr 2023 22:01:58 +0000 (UTC) (envelope-from aryeh.friedman@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-ed1-x536.google.com with SMTP id 4fb4d7f45d1cf-5066ce4f725so3136858a12.1; Fri, 21 Apr 2023 15:01:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1682114517; x=1684706517; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=bZT/Va21BIY8o5+GdxM4gnxD60n4/0cirj/bbJulO44=; b=Lg5HLXxj9S1+qJkmDuCvpWg3YM0WoNkby8yP8HtwO2Or9wHqD3uAr8KImDhNwy0SBC mpyEHaDfbiE1vSfojR1iKasINkPdGvvDAI3qnxjgNxB6pRuKiZgVut9g0HqYR4wEhrpg zPVoxFR18rDv1YirVENCf3P587ROaITJmsoL3dT4DBiQKMlL1hMw2YQcOOeUcC3SV1dG 7VGNAx4HejOEw4h8cO7TCVbHKjF8Sc69sePXHt9fWBY6LkoP6pUZod2D/jklDPRaWA22 df3IVP4Q2peZ54bCi+Hg3JotTkonuZZG1MwbqNQu68Nq24OCce0FT5xJNtnUECyjpBvK 5H6w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1682114517; x=1684706517; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=bZT/Va21BIY8o5+GdxM4gnxD60n4/0cirj/bbJulO44=; b=AAjZy9Ck/eip0UlMUbqQL53WQabx5R/8aMuhHfBwUJhXOJpffp9RFjpHClJxc/ybZO jUnbbjJL8bY9laW0iY2Vn7A1v6NfnAgaJa+5JEe027kvxLSLfRv+xP3X4wV2C3kEWHCo mPQYbEFHwcpxyoQ6LLAlHRw0YN8c39ItJ3JwOzBphATUBHvscAeKGJawfbYQOsDt4oL2 Gsm+NJPKBYKqN6Fvo+Z/3/VmrLlHti6eb2ojlPqorl6Xh/u+ntkMn0M3mQCRFMJxPhmm dna8793LMSJqNRijrlCcocLTnKdtVv+9gJcjS5tkN3PpAhuJFtEoaD8/5YCZSCyeUQv+ gXzg== X-Gm-Message-State: AAQBX9cZwSqYI2rVqKEPl9wqqrEQLazt86GGpBXwGQhajiuQUJ6sxdsd fhsei4CyYdaD7mWwfIllxxb2gYqDbhsrpwxVTamCoav2 X-Google-Smtp-Source: AKy350ZrWnvI8vNqA8g3MlkrRAayo3DkwrUGkTezH45ODIlcquF4UM1KJvZe25Wed8lMaNsc2ANalO6LF0d7Gw6+KdI= X-Received: by 2002:aa7:c592:0:b0:504:b228:878d with SMTP id g18-20020aa7c592000000b00504b228878dmr6414039edq.25.1682114516857; Fri, 21 Apr 2023 15:01:56 -0700 (PDT) List-Id: Technical discussions relating to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-hackers List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-hackers@freebsd.org MIME-Version: 1.0 References: <20230421134120.GA12251@darkbeer.org> In-Reply-To: From: Aryeh Friedman Date: Fri, 21 Apr 2023 18:01:45 -0400 Message-ID: Subject: Re: Installing openAI's GPT-2 Ada AI Language Model To: Mario Marietto Cc: questions@freebsd.org, FreeBSD Mailing List Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Rspamd-Queue-Id: 4Q37m61nfNz3rDk X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; TAGGED_FROM(0.00)[]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N On Fri, Apr 21, 2023 at 5:37=E2=80=AFPM Mario Marietto wrote: > > 1) try to use the linuxulator instead of bhyve (try to remember what Albe= rt Einstein tells about those people that want to solve a problem without c= hanging their perspective : he does not spend nice words for those people) For long term deployment options (eventually I want a VM image people can just download and run) running it on the host in the long term is not a good idea and due to lack of hardware resources (and budget) the only non-production/development platform that I can use is a VM on my production VM host (has 3 other production machines on it). Thus *ANY* solution that does not involve VM's is a non-go. > > 2) actually an nvidia gpu can be passed-thru within linux (and within win= dows 11 if the gpu is amd) See above we don't want to force people to have specific hardware. If I remember right, weren't you the person I was helping late last year to setup pass-thru on bhyve for your nvidia and it turned out to need a bhyve patch (I assume from what you have said this was for the 2 os's you mentioned). If I remember right this was specifically so you could set up GPT-2. > > 3) the tutorial that we are suggesting may work even if you don't want to= use your gpu I was pointed to another tutorial privately that explains how to do it on a VM (I hope ;-)) > > 4) probably you should find the exact version of pytorch that it wants According to chatGPT (and other sources) it will work on anything newer than 1.13 but does not specify anything beyond that. From nobody Sat Apr 22 08:19:00 2023 X-Original-To: freebsd-hackers@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 4Q3PSK6VWMz46NCg; Sat, 22 Apr 2023 08:19:13 +0000 (UTC) (envelope-from aryeh.friedman@gmail.com) Received: from mail-ed1-x52d.google.com (mail-ed1-x52d.google.com [IPv6:2a00:1450:4864:20::52d]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Q3PSK4WPTz3HW3; Sat, 22 Apr 2023 08:19:13 +0000 (UTC) (envelope-from aryeh.friedman@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-ed1-x52d.google.com with SMTP id 4fb4d7f45d1cf-5055141a8fdso3590255a12.3; Sat, 22 Apr 2023 01:19:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1682151552; x=1684743552; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=M04E3hBM1aF2iU5C2gyKvr91XzXUwmbctA0QQ6/5itU=; b=bPKxB5yFRvcYGuQHGl+tgAgiolwiYL445psM83n/HYOk6iZVOfQgxOU73nbaAa1ZYB MvU1gHNF2B9IGZnv+0OZxPL+tHP3xw+o9aVZxygRTpMQCt1GYHokgrmkV1621oVLWFoF PuTPhL44zgeBZTslRT30QuRP1sM7xLtqssqcony8YgNTZsrmUdHPZ6RvQ0Qn0/1pQYkF W32gwCSDlSdA64mnnOIh+etphgTv297z5bK/KV+7JS+RPDEwG+twtmWTaQ1kLjXrhKWj a8X1C+aAYoqF/ZJ4jHprVg2TM9qBPhdkL2J3qu9oiS+dmXaRYbJff5S3nXlRUoaeSWaX UERQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1682151552; x=1684743552; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=M04E3hBM1aF2iU5C2gyKvr91XzXUwmbctA0QQ6/5itU=; b=O5/OUHmdQMAJgeVrYjqQxDyccbC60QvqMbNJCO6uL27q73ZWml09B0DjdUx1nLXdMz n8t+Vw4paOBmI+RRYozOwc5elcQhxvzOlgpVv3YsYD+cK+wnFARU5IarvEG1klp1Exbt iW1GQjRRYw4KeFNShM6N7c9jR3QkhaZ/oORV43j3XgOgOy6xz9kBsGsvpFsd/QOGNafz vw4kU0zymOeyhoESLipgyF1+S5bJ5yJonlIe5t/72AEjs6Jq0iGMXu4EFbBfFXtSm5b2 8rfkRLmH3kbN4U35RxMy6NW5/rYvvXwv+aTBVo3kR/6dXkPW9uAfrBqUgSQ+51KB+e7/ d7qg== X-Gm-Message-State: AAQBX9fdW9WP5ycE6wB6ZhxbH6Fk6j3vl2GEC2k6zlCgN7NM0kPl5Pwc EXunD1lwzeqaUTvrmsUTaZBD6BhGSh7AmXnITKqu6pfgvS4= X-Google-Smtp-Source: AKy350YxnQ8rL06TOweWFmV8LBc/JBoSvtoMAmBvQVvY0nvVuYGuc60birJP3hmj15Zn3pn94p8eB2ntSK0XiDdylH0= X-Received: by 2002:aa7:de11:0:b0:506:b209:edb with SMTP id h17-20020aa7de11000000b00506b2090edbmr6323628edv.38.1682151552087; Sat, 22 Apr 2023 01:19:12 -0700 (PDT) List-Id: Technical discussions relating to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-hackers List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-hackers@freebsd.org MIME-Version: 1.0 References: In-Reply-To: From: Aryeh Friedman Date: Sat, 22 Apr 2023 04:19:00 -0400 Message-ID: Subject: Re: Installing openAI's GPT-2 Ada AI Language Model To: Mario Marietto Cc: FreeBSD Mailing List , FreeBSD Mailing List , Yuri Victorovich Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Rspamd-Queue-Id: 4Q3PSK4WPTz3HW3 X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; TAGGED_FROM(0.00)[] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N On Fri, Apr 21, 2023 at 8:31=E2=80=AFAM Mario Marietto wrote: > > If you don't want to use the GPU,the commands should be more or less the = following : > > > sudo touch /usr/local/etc/rc.d/ubuntu && chmod +x /usr/local/etc/rc.d/ubu= ntu > > # Make it have this content: > > #!/bin/sh > # > # PROVIDE: ubuntu > # REQUIRE: archdep mountlate > # KEYWORD: nojail > # > # This is a modified version of /etc/rc.d/linux > # Based on the script by mrclksr: > # https://github.com/mrclksr/linux-browser-installer/blob/main/rc.d/ubunt= u.in > # > . /etc/rc.subr > > name=3D"ubuntu" > desc=3D"Enable Ubuntu chroot, and Linux ABI" > rcvar=3D"ubuntu_enable" > start_cmd=3D"${name}_start" > stop_cmd=3D":" > > unmounted() > { > [ `stat -f "%d" "$1"` =3D=3D `stat -f "%d" "$1/.."` -a \ > `stat -f "%i" "$1"` !=3D `stat -f "%i" "$1/.."` ] > } > > ubuntu_start() > { > local _emul_path _tmpdir > > load_kld -e 'linux(aout|elf)' linux > case `sysctl -n hw.machine_arch` in > amd64) > load_kld -e 'linux64elf' linux64 > ;; > esac > if [ -x /compat/ubuntu/sbin/ldconfigDisabled ]; then > _tmpdir=3D`mktemp -d -t linux-ldconfig` > /compat/ubuntu/sbin/ldconfig -C ${_tmpdir}/ld.so.cache > if ! cmp -s ${_tmpdir}/ld.so.cache /compat/ubuntu/etc/ld.so.cache= ; then > cat ${_tmpdir}/ld.so.cache > /compat/ubuntu/etc/ld.so.cache > fi > rm -rf ${_tmpdir} > fi > > # Linux uses the pre-pts(4) tty naming scheme. > load_kld pty > > # Handle unbranded ELF executables by defaulting to ELFOSABI_LINUX. > if [ `sysctl -ni kern.elf64.fallback_brand` -eq "-1" ]; then > sysctl kern.elf64.fallback_brand=3D3 > /dev/null > fi > > if [ `sysctl -ni kern.elf32.fallback_brand` -eq "-1" ]; then > sysctl kern.elf32.fallback_brand=3D3 > /dev/null > fi > sysctl compat.linux.emul_path=3D/compat/ubuntu > > _emul_path=3D"/compat/ubuntu" > unmounted "${_emul_path}/dev" && (mount -o nocover -t devfs devfs "${= _emul_path}/dev" || exit 1) > unmounted "${_emul_path}/dev/fd" && (mount -o nocover,linrdlnk -t fde= scfs fdescfs "${_emul_path}/dev/fd" || exit 1) > unmounted "${_emul_path}/dev/shm" && (mount -o nocover,mode=3D1777 -t= tmpfs tmpfs "${_emul_path}/dev/shm" || exit 1) > unmounted "${_emul_path}/home" && (mount -t nullfs /home "${_emul_pat= h}/home" || exit 1) > unmounted "${_emul_path}/proc" && (mount -o nocover -t linprocfs linp= rocfs "${_emul_path}/proc" || exit 1) > unmounted "${_emul_path}/sys" && (mount -o nocover -t linsysfs linsys= fs "${_emul_path}/sys" || exit 1) > unmounted "${_emul_path}/tmp" && (mount -t nullfs /tmp "${_emul_path}= /tmp" || exit 1) > unmounted /dev/fd && (mount -o nocover -t fdescfs fdescfs /dev/fd || = exit 1) > unmounted /proc && (mount -o nocover -t procfs procfs /proc || exit 1= ) > true > } > > load_rc_config $name > run_rc_command "$1" > > sysrc ubuntu_enable=3DYES > > # Create necessary mount points for a working Linuxulator: > mkdir -p {/compat/ubuntu/dev/fd,/compat/ubuntu/dev/shm,/compat/ubuntu/hom= e,/compat/ubuntu/tmp,/compat/ubuntu/proc,/compat/ubuntu/sys} > > # Start Ubuntu service: > service ubuntu start > > # Install needed packages: > pkg install debootstrap pulseaudio > > # Install Ubuntu 20.04 into /compat/ubuntu: > debootstrap --arch=3Damd64 --no-check-gpg focal /compat/ubuntu > > # Restart Ubuntu service to make sure everything is properly mounted: > service ubuntu restart > > # Fix broken symlink: > cd /compat/ubuntu/lib64/ && rm ./ld-linux-x86-64.so.2 ; ln -s ../lib/x86_= 64-linux-gnu/ld-2.31.so ld-linux-x86-64.so.2 > > # Chroot into your Linux environment: > chroot /compat/ubuntu /bin/bash > > # Set correct timezone inside your chroot: > printf "%b\n" "0.0 0 0.0\n0\nUTC" > /etc/adjtime > sudo dpkg-reconfigure tzdata # For some reason sudo is necessary here, ot= herwise it fails. > > # Fix APT package manager: > printf "APT::Cache-Start 251658240;" > /etc/apt/apt.conf.d/00aptitude > > # Enable more repositories: > printf "deb http://archive.ubuntu.com/ubuntu/ focal main restricted unive= rse multiverse" > /etc/apt/sources.list > > # Install required programs: > > apt update ; apt install -y apt-transport-https curl fonts-symbola gnupg = pulseaudio build-essential gcc gfortran > > # Exit out of chroot > exit > > # Fix x86_64-linux-gnu libraries path between ubuntu and freebsd > cp -r /compat/ubuntu/usr/lib/x86_64-linux-gnu /lib > > > --> Installing PyTorch and your chatgpt github fork on FreeBSD > > > # fetch https://gist.githubusercontent.com/shkhln/40ef290463e78fb2b0000c6= 0f4ad797e/raw/f640983249607e38af405c95c457ce4afc85c608/uvm_ioctl_override.c > > # /compat/ubuntu/bin/gcc --sysroot=3D/compat/ubuntu -m64 -std=3Dc99 -Wall= -ldl -fPIC -shared -o dummy-uvm.so uvm_ioctl_override.c > > # pkg install linux-miniconda-installer > # miniconda-installer > # bash > # source /home/marietto/miniconda3/etc/profile.d/conda.sh > # conda activate > > (base) # conda activate pytorch > > (pytorch) # conda activate > > (base) # conda activate > > (base) # git clone your chatgpt github fork I have done that I think and get: (base) [babyspock@babyspock ~]$ python src/generate_unconditional_samples.py --model_name 117M --nsamples 5 --length 512 python: can't open file '/usr/opt/babySpock/src/generate_unconditional_samples.py': [Errno 2] No such file or directory (base) [babyspock@babyspock ~]$ cd gpt-2/ (base) [babyspock@babyspock ~/gpt-2]$ python src/generate_unconditional_samples.py --model_name 117M --nsamples 5 --length 512 2023-04-22 00:17:18.661083: I tensorflow/tsl/cuda/cudart_stub.cc:28] Could not find cuda drivers on your machine, GPU will not be used. 2023-04-22 00:17:18.710468: I tensorflow/tsl/cuda/cudart_stub.cc:28] Could not find cuda drivers on your machine, GPU will not be used. 2023-04-22 00:17:18.710951: I tensorflow/core/platform/cpu_feature_guard.cc:182] This TensorFlow binary is optimized to use available CPU instructions in performance-critical operations. To enable the following instructions: AVX2 FMA, in other operations, rebuild TensorFlow with the appropriate compiler flags. 2023-04-22 00:17:19.429409: W tensorflow/compiler/tf2tensorrt/utils/py_utils.cc:38] TF-TRT Warning: Could not find TensorRT Traceback (most recent call last): File "/usr/opt/babySpock/gpt-2/src/generate_unconditional_samples.py", line 9, in import model, sample, encoder File "/usr/opt/babySpock/gpt-2/src/model.py", line 3, in from tensorflow.contrib.training import HParams ModuleNotFoundError: No module named 'tensorflow.contrib' > > > On Fri, Apr 21, 2023 at 1:34=E2=80=AFPM Aryeh Friedman wrote: >> >> On Fri, Apr 21, 2023 at 6:40=E2=80=AFAM Mario Marietto wrote: >> > >> > You don't need bhyve to make that,but only the Linuxulator. I don't th= ink the type of cpu will make any difference. I've used the Intel I9 cpu. I= tried FreeBSD 13.1 and I haven't found problems. For sure using python env= is tricky,but if you have the thinkering attitude,you will have some fun. >> >> I already have a VM allocated on it (the same host has 3 other VM's on >> it). I guess that is one thing I missed was the linuxulator (the >> linsuckslator is more like it) and as far tinkering goes it is fine to >> a point but not when it has taken *DAYS* away from paying projects (I >> am a freelancer). >> >> BTW I will be trying your specific command lines tomorrow (I must get >> back to paid work). >> >> P.S. The point of this project is to start a new project called >> babySpock that is a personal assistant for me and my programming >> partner/wife in all but legal detail. babySpock will hopefully be >> able to help with pair programming/design brainstorming, general >> clerical office tasks, be a halfway decent conversation partner >> (roughly on or near the level of chatGPT which inspired this project >> in the first place in order to increase the amount of "context" that >> it could store and to slice and dice context as needed to feed the >> more expensive models just relevant context as well use multiple >> models.... basically a DIY hobbyist AM (artificial mind with the final >> goal being artificial mature minds [AMM] instead of AGI due to the >> rule making paradox) lab that has to "earn its own way in life" (i.e. >> if it is not useful it will likely die from misuse). >> >> > >> > On Fri, Apr 21, 2023 at 12:26=E2=80=AFPM Aryeh Friedman wrote: >> >> >> >> The more I am fighting with it in linux (only thing there is docs for= ) >> >> the more obvious it just doesn't work on >> >> >> >> On Fri, Apr 21, 2023 at 6:19=E2=80=AFAM Mario Marietto wrote: >> >> > >> >> > Can't you install pytorch using the linux miniconda installer like = below ? >> >> > >> >> > # fetch https://gist.githubusercontent.com/shkhln/40ef290463e78fb2b= 0000c60f4ad797e/raw/f640983249607e38af405c95c457ce4afc85c608/uvm_ioctl_over= ride.c >> >> > >> >> > # /compat/ubuntu/bin/gcc --sysroot=3D/compat/ubuntu -m64 -std=3Dc99= -Wall -ldl -fPIC -shared -o dummy-uvm.so uvm_ioctl_override.c >> >> > >> >> > # pkg install linux-miniconda-installer >> >> > # miniconda-installer >> >> > # bash >> >> > # source /home/marietto/miniconda3/etc/profile.d/conda.sh >> >> > # conda activate >> >> > >> >> > (base) # conda activate pytorch >> >> > >> >> Will this work a bhyve on an AMD Ryzen 5 host? After playing with i= t >> >> in several linux instances I always get stuck when it can't find a >> >> compatible version >> >> >> >> -- >> >> Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org >> > >> > >> > >> > -- >> > Mario. >> >> >> >> -- >> Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org > > > > -- > Mario. --=20 Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org From nobody Sat Apr 22 09:18:40 2023 X-Original-To: freebsd-hackers@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 4Q3Qnf6ff0z46Slv; Sat, 22 Apr 2023 09:19:18 +0000 (UTC) (envelope-from marietto2008@gmail.com) Received: from mail-yb1-xb2f.google.com (mail-yb1-xb2f.google.com [IPv6:2607:f8b0:4864:20::b2f]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Q3Qnf4dWmz3shH; Sat, 22 Apr 2023 09:19:18 +0000 (UTC) (envelope-from marietto2008@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-yb1-xb2f.google.com with SMTP id 3f1490d57ef6-b994571219fso640333276.1; Sat, 22 Apr 2023 02:19:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1682155157; x=1684747157; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=FmP+3F6BuzPAEXVR603Flnd+q8XUp5xBDu8J1FfhE3w=; b=Wr7jjY9ueijuv2rBUpPUfWTpcYIeWhgfEztn9kTD2DAmt5CYvBDDyR9PNyXAHGTG61 zm8Tb8NGYJsH3lfO4KXCnSU8W3ClGqdp8j7coPG2+Qcg/Nd/Yz5dV9DfKvJunzPrOeJS P8Y/34uUmIatX0LK5GN08Wc8AVa0sJVMTwGPH2Oyj3PnSQSZcfj2r+ZNcMDBrHMg4nir AelaJX6nhjRYtmuMY+N9L5PlcVoHMeHN38Er4f7A+R3peGQXxTs/0sOn/d1B4QrN5dA+ fg/ZAnSoyf7y5I0Csf36VQ1pppqelpzHoqGXaYssSV6B4AvHhy/y/IIvUfl1J6C6cVoE uDeQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1682155157; x=1684747157; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=FmP+3F6BuzPAEXVR603Flnd+q8XUp5xBDu8J1FfhE3w=; b=X0a/EgdVf2CkZliVtZuHhkkxXXd6zd2yxg4AzMHdi8WIeI4lQjebTSvdnYDo2dOJ5E CMbzSnHZAfC3qICE9V3zth26s0dE62NckfUzanv7l6CJM+BfzUjvXc5pZ/xOc9Glbqyx 8zqK5bPEbfAp7p9V6Xez1ut2lcKin50jbY4GO6NCGaze1G0BqMblmfF4Uz8MdB15d0Ub n5bWqDFS/YU0CQL/dRLp9potV8Lu/A04WUOtwJbOpN/Sc9WMMtCXfkkmg5j8RhOIzarp u4xGfUAnvDHD1fuugunnX6gFD7d18vPhROg4QtfH27CIAa38WzFkFKFxPTP5bK1mo+Hd 485A== X-Gm-Message-State: AAQBX9fZsk4fVDFmoCfXSMAYYJauvkvmzYaFC6Zwv5R1kX5cEtYZ2C7r DZ+bjhurKnCVRSKvhK7aKWaz5Ujgn+MA5n/EYWSPooWTlLzVzw== X-Google-Smtp-Source: AKy350YRhr8RpCO04yPalB8Uf5Ub85xnhCWQueK4Q3k3lTHfpZr4AiuhPjwXFhyORDbb/cSjshT39+x0+5zuXjsX/o0= X-Received: by 2002:a25:2d5:0:b0:b8f:4a52:15db with SMTP id 204-20020a2502d5000000b00b8f4a5215dbmr4593004ybc.60.1682155157054; Sat, 22 Apr 2023 02:19:17 -0700 (PDT) List-Id: Technical discussions relating to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-hackers List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-hackers@freebsd.org MIME-Version: 1.0 References: In-Reply-To: From: Mario Marietto Date: Sat, 22 Apr 2023 11:18:40 +0200 Message-ID: Subject: Re: Installing openAI's GPT-2 Ada AI Language Model To: Odhiambo Washington Cc: Aryeh Friedman , FreeBSD Mailing List , FreeBSD Mailing List , Yuri Victorovich Content-Type: multipart/alternative; boundary="00000000000097e7d305f9e94448" X-Rspamd-Queue-Id: 4Q3Qnf4dWmz3shH X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; TAGGED_RCPT(0.00)[] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N --00000000000097e7d305f9e94448 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable marietto@marietto-nano:~$ python3 Python 3.10.6 (main, Mar 10 2023, 10:55:28) [GCC 11.3.0] on linux Type "help", "copyright", "credits" or "license" for more information. >>> import tensorflow as tf >>> tf.__version__ '2.12.0' >>> print(tf.reduce_sum(tf.random.normal([1000, 1000]))) tf.Tensor(51.500687, shape=3D(), dtype=3Dfloat32) https://qengineering.eu/install-tensorflow-2.4.0-on-jetson-nano.html On Sat, Apr 22, 2023 at 10:47=E2=80=AFAM Odhiambo Washington wrote: > > > On Sat, Apr 22, 2023 at 11:20=E2=80=AFAM Aryeh Friedman > wrote: > >> On Fri, Apr 21, 2023 at 8:31=E2=80=AFAM Mario Marietto >> wrote: >> > >> > If you don't want to use the GPU,the commands should be more or less >> the following : >> > >> > >> > sudo touch /usr/local/etc/rc.d/ubuntu && chmod +x >> /usr/local/etc/rc.d/ubuntu >> > >> > # Make it have this content: >> > >> > #!/bin/sh >> > # >> > # PROVIDE: ubuntu >> > # REQUIRE: archdep mountlate >> > # KEYWORD: nojail >> > # >> > # This is a modified version of /etc/rc.d/linux >> > # Based on the script by mrclksr: >> > # >> https://github.com/mrclksr/linux-browser-installer/blob/main/rc.d/ubuntu= .in >> > # >> > . /etc/rc.subr >> > >> > name=3D"ubuntu" >> > desc=3D"Enable Ubuntu chroot, and Linux ABI" >> > rcvar=3D"ubuntu_enable" >> > start_cmd=3D"${name}_start" >> > stop_cmd=3D":" >> > >> > unmounted() >> > { >> > [ `stat -f "%d" "$1"` =3D=3D `stat -f "%d" "$1/.."` -a \ >> > `stat -f "%i" "$1"` !=3D `stat -f "%i" "$1/.."` ] >> > } >> > >> > ubuntu_start() >> > { >> > local _emul_path _tmpdir >> > >> > load_kld -e 'linux(aout|elf)' linux >> > case `sysctl -n hw.machine_arch` in >> > amd64) >> > load_kld -e 'linux64elf' linux64 >> > ;; >> > esac >> > if [ -x /compat/ubuntu/sbin/ldconfigDisabled ]; then >> > _tmpdir=3D`mktemp -d -t linux-ldconfig` >> > /compat/ubuntu/sbin/ldconfig -C ${_tmpdir}/ld.so.cache >> > if ! cmp -s ${_tmpdir}/ld.so.cache >> /compat/ubuntu/etc/ld.so.cache; then >> > cat ${_tmpdir}/ld.so.cache > /compat/ubuntu/etc/ld.so.cach= e >> > fi >> > rm -rf ${_tmpdir} >> > fi >> > >> > # Linux uses the pre-pts(4) tty naming scheme. >> > load_kld pty >> > >> > # Handle unbranded ELF executables by defaulting to ELFOSABI_LINUX= . >> > if [ `sysctl -ni kern.elf64.fallback_brand` -eq "-1" ]; then >> > sysctl kern.elf64.fallback_brand=3D3 > /dev/null >> > fi >> > >> > if [ `sysctl -ni kern.elf32.fallback_brand` -eq "-1" ]; then >> > sysctl kern.elf32.fallback_brand=3D3 > /dev/null >> > fi >> > sysctl compat.linux.emul_path=3D/compat/ubuntu >> > >> > _emul_path=3D"/compat/ubuntu" >> > unmounted "${_emul_path}/dev" && (mount -o nocover -t devfs devfs >> "${_emul_path}/dev" || exit 1) >> > unmounted "${_emul_path}/dev/fd" && (mount -o nocover,linrdlnk -t >> fdescfs fdescfs "${_emul_path}/dev/fd" || exit 1) >> > unmounted "${_emul_path}/dev/shm" && (mount -o nocover,mode=3D1777= -t >> tmpfs tmpfs "${_emul_path}/dev/shm" || exit 1) >> > unmounted "${_emul_path}/home" && (mount -t nullfs /home >> "${_emul_path}/home" || exit 1) >> > unmounted "${_emul_path}/proc" && (mount -o nocover -t linprocfs >> linprocfs "${_emul_path}/proc" || exit 1) >> > unmounted "${_emul_path}/sys" && (mount -o nocover -t linsysfs >> linsysfs "${_emul_path}/sys" || exit 1) >> > unmounted "${_emul_path}/tmp" && (mount -t nullfs /tmp >> "${_emul_path}/tmp" || exit 1) >> > unmounted /dev/fd && (mount -o nocover -t fdescfs fdescfs /dev/fd >> || exit 1) >> > unmounted /proc && (mount -o nocover -t procfs procfs /proc || exi= t >> 1) >> > true >> > } >> > >> > load_rc_config $name >> > run_rc_command "$1" >> > >> > sysrc ubuntu_enable=3DYES >> > >> > # Create necessary mount points for a working Linuxulator: >> > mkdir -p >> {/compat/ubuntu/dev/fd,/compat/ubuntu/dev/shm,/compat/ubuntu/home,/compa= t/ubuntu/tmp,/compat/ubuntu/proc,/compat/ubuntu/sys} >> > >> > # Start Ubuntu service: >> > service ubuntu start >> > >> > # Install needed packages: >> > pkg install debootstrap pulseaudio >> > >> > # Install Ubuntu 20.04 into /compat/ubuntu: >> > debootstrap --arch=3Damd64 --no-check-gpg focal /compat/ubuntu >> > >> > # Restart Ubuntu service to make sure everything is properly mounted: >> > service ubuntu restart >> > >> > # Fix broken symlink: >> > cd /compat/ubuntu/lib64/ && rm ./ld-linux-x86-64.so.2 ; ln -s >> ../lib/x86_64-linux-gnu/ld-2.31.so ld-linux-x86-64.so.2 >> > >> > # Chroot into your Linux environment: >> > chroot /compat/ubuntu /bin/bash >> > >> > # Set correct timezone inside your chroot: >> > printf "%b\n" "0.0 0 0.0\n0\nUTC" > /etc/adjtime >> > sudo dpkg-reconfigure tzdata # For some reason sudo is necessary here, >> otherwise it fails. >> > >> > # Fix APT package manager: >> > printf "APT::Cache-Start 251658240;" > /etc/apt/apt.conf.d/00aptitude >> > >> > # Enable more repositories: >> > printf "deb http://archive.ubuntu.com/ubuntu/ focal main restricted >> universe multiverse" > /etc/apt/sources.list >> > >> > # Install required programs: >> > >> > apt update ; apt install -y apt-transport-https curl fonts-symbola >> gnupg pulseaudio build-essential gcc gfortran >> > >> > # Exit out of chroot >> > exit >> > >> > # Fix x86_64-linux-gnu libraries path between ubuntu and freebsd >> > cp -r /compat/ubuntu/usr/lib/x86_64-linux-gnu /lib >> > >> > >> > --> Installing PyTorch and your chatgpt github fork on FreeBSD >> > >> > >> > # fetch >> https://gist.githubusercontent.com/shkhln/40ef290463e78fb2b0000c60f4ad79= 7e/raw/f640983249607e38af405c95c457ce4afc85c608/uvm_ioctl_override.c >> > >> > # /compat/ubuntu/bin/gcc --sysroot=3D/compat/ubuntu -m64 -std=3Dc99 -W= all >> -ldl -fPIC -shared -o dummy-uvm.so uvm_ioctl_override.c >> > >> > # pkg install linux-miniconda-installer >> > # miniconda-installer >> > # bash >> > # source /home/marietto/miniconda3/etc/profile.d/conda.sh >> > # conda activate >> > >> > (base) # conda activate pytorch >> > >> > (pytorch) # conda activate >> > >> > (base) # conda activate >> > >> > (base) # git clone your chatgpt github fork >> >> >> I have done that I think and get: >> >> (base) [babyspock@babyspock ~]$ python >> src/generate_unconditional_samples.py --model_name 117M --nsamples 5 >> --length 512 >> python: can't open file >> '/usr/opt/babySpock/src/generate_unconditional_samples.py': [Errno 2] >> No such file or directory >> (base) [babyspock@babyspock ~]$ cd gpt-2/ >> (base) [babyspock@babyspock ~/gpt-2]$ python >> src/generate_unconditional_samples.py --model_name 117M --nsamples 5 >> --length 512 >> 2023-04-22 00:17:18.661083: I tensorflow/tsl/cuda/cudart_stub.cc:28] >> Could not find cuda drivers on your machine, GPU will not be used. >> 2023-04-22 00:17:18.710468: I tensorflow/tsl/cuda/cudart_stub.cc:28] >> Could not find cuda drivers on your machine, GPU will not be used. >> 2023-04-22 00:17:18.710951: I >> tensorflow/core/platform/cpu_feature_guard.cc:182] This TensorFlow >> binary is optimized to use available CPU instructions in >> performance-critical operations. >> To enable the following instructions: AVX2 FMA, in other operations, >> rebuild TensorFlow with the appropriate compiler flags. >> 2023-04-22 00:17:19.429409: W >> tensorflow/compiler/tf2tensorrt/utils/py_utils.cc:38] TF-TRT Warning: >> Could not find TensorRT >> Traceback (most recent call last): >> File "/usr/opt/babySpock/gpt-2/src/generate_unconditional_samples.py", >> line 9, in >> import model, sample, encoder >> File "/usr/opt/babySpock/gpt-2/src/model.py", line 3, in >> from tensorflow.contrib.training import HParams >> ModuleNotFoundError: No module named 'tensorflow.contrib' >> > > Use Python3.7 or earlier. > > -- > Best regards, > Odhiambo WASHINGTON, > Nairobi,KE > +254 7 3200 0004/+254 7 2274 3223 > "Oh, the cruft.", egrep -v '^$|^.*#' =C2=AF\_(=E3=83=84)_/=C2=AF :-) > [How to ask smart questions: > http://www.catb.org/~esr/faqs/smart-questions.html] > --=20 Mario. --00000000000097e7d305f9e94448 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
mariett= o@marietto-nano:~$ python3
Python 3.10.6 (main, Mar 10 2023, 10:55:28) [GCC 11.3.0] on linu= x
Type "help", "copyright", "credits" or &q= uot;license" for more information.
>>> import tensorflow as tf
>>> tf.__version__
'2.12.0'
>>> print(tf.reduce_sum(tf.random.normal([1000, 1000]))) =C2= =A0
tf.Tensor(51.500687, shape=3D(), dtype=3Dfloat32)

https://qengineering.eu/install-tensorflow-2.4.0-on-jetson= -nano.html

On Sat, Apr 22, 2023 at 10:47=E2=80=AFAM Odhiambo Washingto= n <odhiambo@gmail.com> wrot= e:


On Sat, Apr 22, 2023 at 11:20=E2=80=AFAM Aryeh Fri= edman <ary= eh.friedman@gmail.com> wrote:
On Fri, Apr 21, 2023 at 8:31=E2=80=AFAM Mario Marietto= <marietto20= 08@gmail.com> wrote:
>
> If you don't want to use the GPU,the commands should be more or le= ss the following :
>
>
> sudo touch /usr/local/etc/rc.d/ubuntu && chmod +x /usr/local/e= tc/rc.d/ubuntu
>
> # Make it have this content:
>
> #!/bin/sh
> #
> # PROVIDE: ubuntu
> # REQUIRE: archdep mountlate
> # KEYWORD: nojail
> #
> # This is a modified version of /etc/rc.d/linux
> # Based on the script by mrclksr:
> # https://github.com= /mrclksr/linux-browser-installer/blob/main/rc.d/ubuntu.in
> #
> . /etc/rc.subr
>
> name=3D"ubuntu"
> desc=3D"Enable Ubuntu chroot, and Linux ABI"
> rcvar=3D"ubuntu_enable"
> start_cmd=3D"${name}_start"
> stop_cmd=3D":"
>
> unmounted()
> {
>=C2=A0 =C2=A0 =C2=A0[ `stat -f "%d" "$1"` =3D=3D `s= tat -f "%d" "$1/.."` -a \
>=C2=A0 =C2=A0 =C2=A0 =C2=A0`stat -f "%i" "$1"` !=3D= `stat -f "%i" "$1/.."` ]
> }
>
> ubuntu_start()
> {
>=C2=A0 =C2=A0 =C2=A0local _emul_path _tmpdir
>
>=C2=A0 =C2=A0 =C2=A0load_kld -e 'linux(aout|elf)' linux
>=C2=A0 =C2=A0 =C2=A0case `sysctl -n hw.machine_arch` in
>=C2=A0 =C2=A0 =C2=A0amd64)
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0load_kld -e 'linux64elf' linu= x64
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0;;
>=C2=A0 =C2=A0 =C2=A0esac
>=C2=A0 =C2=A0 =C2=A0if [ -x /compat/ubuntu/sbin/ldconfigDisabled ]; the= n
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0_tmpdir=3D`mktemp -d -t linux-ldconfi= g`
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0/compat/ubuntu/sbin/ldconfig -C ${_tm= pdir}/ld.so.cache
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0if ! cmp -s ${_tmpdir}/ld.so.cache /c= ompat/ubuntu/etc/ld.so.cache; then
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0cat ${_tmpdir}/ld.so.ca= che > /compat/ubuntu/etc/ld.so.cache
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0fi
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0rm -rf ${_tmpdir}
>=C2=A0 =C2=A0 =C2=A0fi
>
>=C2=A0 =C2=A0 =C2=A0# Linux uses the pre-pts(4) tty naming scheme.
>=C2=A0 =C2=A0 =C2=A0load_kld pty
>
>=C2=A0 =C2=A0 =C2=A0# Handle unbranded ELF executables by defaulting to= ELFOSABI_LINUX.
>=C2=A0 =C2=A0 =C2=A0if [ `sysctl -ni kern.elf64.fallback_brand` -eq &qu= ot;-1" ]; then
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0sysctl kern.elf64.fallback_brand=3D3 = > /dev/null
>=C2=A0 =C2=A0 =C2=A0fi
>
>=C2=A0 =C2=A0 =C2=A0if [ `sysctl -ni kern.elf32.fallback_brand` -eq &qu= ot;-1" ]; then
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0sysctl kern.elf32.fallback_brand=3D3 = > /dev/null
>=C2=A0 =C2=A0 =C2=A0fi
>=C2=A0 =C2=A0 =C2=A0sysctl compat.linux.emul_path=3D/compat/ubuntu
>
>=C2=A0 =C2=A0 =C2=A0_emul_path=3D"/compat/ubuntu"
>=C2=A0 =C2=A0 =C2=A0unmounted "${_emul_path}/dev" && = (mount -o nocover -t devfs devfs "${_emul_path}/dev" || exit 1) >=C2=A0 =C2=A0 =C2=A0unmounted "${_emul_path}/dev/fd" &&am= p; (mount -o nocover,linrdlnk -t fdescfs fdescfs "${_emul_path}/dev/fd= " || exit 1)
>=C2=A0 =C2=A0 =C2=A0unmounted "${_emul_path}/dev/shm" &&a= mp; (mount -o nocover,mode=3D1777 -t tmpfs tmpfs "${_emul_path}/dev/sh= m" || exit 1)
>=C2=A0 =C2=A0 =C2=A0unmounted "${_emul_path}/home" &&= (mount -t nullfs /home "${_emul_path}/home" || exit 1)
>=C2=A0 =C2=A0 =C2=A0unmounted "${_emul_path}/proc" &&= (mount -o nocover -t linprocfs linprocfs "${_emul_path}/proc" ||= exit 1)
>=C2=A0 =C2=A0 =C2=A0unmounted "${_emul_path}/sys" && = (mount -o nocover -t linsysfs linsysfs "${_emul_path}/sys" || exi= t 1)
>=C2=A0 =C2=A0 =C2=A0unmounted "${_emul_path}/tmp" && = (mount -t nullfs /tmp "${_emul_path}/tmp" || exit 1)
>=C2=A0 =C2=A0 =C2=A0unmounted /dev/fd && (mount -o nocover -t f= descfs fdescfs /dev/fd || exit 1)
>=C2=A0 =C2=A0 =C2=A0unmounted /proc && (mount -o nocover -t pro= cfs procfs /proc || exit 1)
>=C2=A0 =C2=A0 =C2=A0true
> }
>
> load_rc_config $name
> run_rc_command "$1"
>
> sysrc ubuntu_enable=3DYES
>
> # Create necessary mount points for a working Linuxulator:
> mkdir -p {/compat/ubuntu/dev/fd,/compat/ubuntu/dev/shm,/compat/ubuntu/= home,/compat/ubuntu/tmp,/compat/ubuntu/proc,/compat/ubuntu/sys}
>
> # Start Ubuntu service:
> service ubuntu start
>
> # Install needed packages:
> pkg install debootstrap pulseaudio
>
> # Install Ubuntu 20.04 into /compat/ubuntu:
> debootstrap --arch=3Damd64 --no-check-gpg focal /compat/ubuntu
>
> # Restart Ubuntu service to make sure everything is properly mounted:<= br> > service ubuntu restart
>
> # Fix broken symlink:
> cd /compat/ubuntu/lib64/ && rm ./ld-linux-x86-64.so.2 ; ln -s = ../lib/x86_64-linux-gnu/ld-2.31.so ld-linux-x86-64.so.2
>
> # Chroot into your Linux environment:
> chroot /compat/ubuntu /bin/bash
>
> # Set correct timezone inside your chroot:
> printf "%b\n" "0.0 0 0.0\n0\nUTC" > /etc/adjtim= e
> sudo dpkg-reconfigure tzdata # For some reason sudo is necessary here,= otherwise it fails.
>
> # Fix APT package manager:
> printf "APT::Cache-Start 251658240;" > /etc/apt/apt.conf.= d/00aptitude
>
> # Enable more repositories:
> printf "deb http://archive.ubuntu.com/ubuntu/ focal m= ain restricted universe multiverse" > /etc/apt/sources.list
>
> # Install required programs:
>
> apt update ; apt install -y apt-transport-https curl fonts-symbola gnu= pg pulseaudio build-essential gcc gfortran
>
> # Exit out of chroot
> exit
>
> # Fix x86_64-linux-gnu libraries path between ubuntu and freebsd
> cp -r /compat/ubuntu/usr/lib/x86_64-linux-gnu /lib
>
>
> --> Installing PyTorch and your chatgpt github fork on FreeBSD
>
>
> # fetch https://gist.githubuse= rcontent.com/shkhln/40ef290463e78fb2b0000c60f4ad797e/raw/f640983249607e38af= 405c95c457ce4afc85c608/uvm_ioctl_override.c
>
> # /compat/ubuntu/bin/gcc --sysroot=3D/compat/ubuntu -m64 -std=3Dc99 -W= all -ldl -fPIC -shared -o dummy-uvm.so uvm_ioctl_override.c
>
> # pkg install linux-miniconda-installer
> # miniconda-installer
> # bash
> # source /home/marietto/miniconda3/etc/profile.d/conda.sh
> # conda activate
>
> (base) # conda activate pytorch
>
> (pytorch) # conda activate
>
> (base) # conda activate
>
> (base) # git clone your chatgpt github fork


I have done that I think and get:

(base) [babyspock@babyspock ~]$ python
src/generate_unconditional_samples.py --model_name 117M --nsamples 5
--length 512
python: can't open file
'/usr/opt/babySpock/src/generate_unconditional_samples.py': [Errno = 2]
No such file or directory
(base) [babyspock@babyspock ~]$ cd gpt-2/
(base) [babyspock@babyspock ~/gpt-2]$ python
src/generate_unconditional_samples.py --model_name 117M --nsamples 5
--length 512
2023-04-22 00:17:18.661083: I tensorflow/tsl/cuda/cudart_stub.cc:28]
Could not find cuda drivers on your machine, GPU will not be used.
2023-04-22 00:17:18.710468: I tensorflow/tsl/cuda/cudart_stub.cc:28]
Could not find cuda drivers on your machine, GPU will not be used.
2023-04-22 00:17:18.710951: I
tensorflow/core/platform/cpu_feature_guard.cc:182] This TensorFlow
binary is optimized to use available CPU instructions in
performance-critical operations.
To enable the following instructions: AVX2 FMA, in other operations,
rebuild TensorFlow with the appropriate compiler flags.
2023-04-22 00:17:19.429409: W
tensorflow/compiler/tf2tensorrt/utils/py_utils.cc:38] TF-TRT Warning:
Could not find TensorRT
Traceback (most recent call last):
=C2=A0 File "/usr/opt/babySpock/gpt-2/src/generate_unconditional_sampl= es.py",
line 9, in <module>
=C2=A0 =C2=A0 import model, sample, encoder
=C2=A0 File "/usr/opt/babySpock/gpt-2/src/model.py", line 3, in &= lt;module>
=C2=A0 =C2=A0 from tensorflow.contrib.training import HParams
ModuleNotFoundError: No module named 'tensorflow.contrib'

Use Python3.7 or earlier.

--
Best regards,
Odhiambo WASHINGTON,
Nairobi,K= E
+254 7 3200 0004/+254 7 2274 3223
"Oh, the cruft.",=C2=A0egrep -v '^$|^.*#'=C2=A0=C2=AF\_(=E3=83=84)_/=C2=AF=C2=A0:-)
[H= ow to ask smart questions:=C2=A0http://www.catb.org/~esr/faqs/smart-questions.html]


--
Mario.
--00000000000097e7d305f9e94448-- From nobody Sat Apr 22 18:13:44 2023 X-Original-To: freebsd-hackers@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 4Q3fg25cvHz465Vx; Sat, 22 Apr 2023 18:14:22 +0000 (UTC) (envelope-from marietto2008@gmail.com) Received: from mail-yw1-x1133.google.com (mail-yw1-x1133.google.com [IPv6:2607:f8b0:4864:20::1133]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Q3fg21Bn7z4RGk; Sat, 22 Apr 2023 18:14:22 +0000 (UTC) (envelope-from marietto2008@gmail.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20221208 header.b=ZAFyOvby; spf=pass (mx1.freebsd.org: domain of marietto2008@gmail.com designates 2607:f8b0:4864:20::1133 as permitted sender) smtp.mailfrom=marietto2008@gmail.com; dmarc=pass (policy=none) header.from=gmail.com Received: by mail-yw1-x1133.google.com with SMTP id 00721157ae682-54fb8a8a597so33338207b3.0; Sat, 22 Apr 2023 11:14:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1682187261; x=1684779261; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=2EjtGGnE5kBU7aLe3zl1AdaCRY4OfKfT3ozLNogRVnQ=; b=ZAFyOvbyR4GGwW6bTfZfVQBrfxCc/f6NZT1BG3XbZiRcIwc44LA8eu7cUn0FNOrEzj 1K7oyfvhIYfwQ5Vi+/doMfyGMuULZguf5cVnwEYz0rae1mdCRqgiXvIdXS1PUIgYgYp8 3+TkT5q4PC/C7nQ/m5R2KfmkRJZJ9UwvUcx/Yg8pgLJeQX7t8ZgKdYE/fOdMRXVPgJUo WuFm37aku8QWNQGHRAH5doSOzLaXnm8zmhYbJZC6AhVjHr6/Dj61b1o+28En+bc3O8e4 4/f8CFvePudjYsuZydOEjLIqjc33yW1GU4woC37yeyOoHQsbYTju3JgnmbRkfwjeHTLR Somw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1682187261; x=1684779261; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=2EjtGGnE5kBU7aLe3zl1AdaCRY4OfKfT3ozLNogRVnQ=; b=YIkeRz0dmDm7egvE4RV+EKqWTbaH9tnGuk2gvNWbDI/A3JBArkHhRL4EDz+wIor1Xc yDcEAbHxgTtst44yj12aS31hVb7qmq6XG9HfwxJ4bkSrcoHDJBhEvDnARjFmdutp9NjH GalLP5/dNH7RMq7kZS47wR9YmJ1AwHorw0UIoCj8/+8GFBK6sokRP4dZdEThcr5a8Uey oF1HFHxnN/EoEy+WoYQdQe/XUxkpUY4etB1Tecv+miuiVPYzAPQdKleCrD8h47PNSR/I YlQ3MM8eh7ZU4OjUPvJ/phGdQQu/tR2HK5evj40x4FPx7BfMudPusxZOohT7t8VxT1mv 0WfA== X-Gm-Message-State: AAQBX9cfJy+v+zJ57Xjh/J9rdAlwElEWJUBW/l/csMcVlrR7q6DD3nzh re5eESoQc4lUxiElDUkvK/OfuOszwmG2IW9hsNwB+EV8SLmTVw== X-Google-Smtp-Source: AKy350aSoDH0Ebx+FpjQf6gAeAT79V3ctZ5bHvztwP/t+Co/PHvHZ3FY1fkWNAHzdMr+K5AKQrzZXhNZ+QZ/MBYvZx8= X-Received: by 2002:a81:5201:0:b0:538:4ae4:2d2f with SMTP id g1-20020a815201000000b005384ae42d2fmr4347026ywb.52.1682187260482; Sat, 22 Apr 2023 11:14:20 -0700 (PDT) List-Id: Technical discussions relating to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-hackers List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-hackers@freebsd.org MIME-Version: 1.0 References: In-Reply-To: From: Mario Marietto Date: Sat, 22 Apr 2023 20:13:44 +0200 Message-ID: Subject: Re: Installing openAI's GPT-2 Ada AI Language Model To: Aryeh Friedman , freebsd-hackers , Yuri Victorovich , FreeBSD Mailing List Cc: Odhiambo Washington Content-Type: multipart/alternative; boundary="0000000000001b5a4f05f9f0bedd" X-Spamd-Result: default: False [-2.50 / 15.00]; SUSPICIOUS_RECIPS(1.50)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-0.999]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20221208]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36:c]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; FROM_HAS_DN(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::1133:from]; TAGGED_RCPT(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; MLMMJ_DEST(0.00)[freebsd-hackers@freebsd.org,freebsd-questions@freebsd.org]; TO_MATCH_ENVRCPT_SOME(0.00)[]; ARC_NA(0.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; FREEMAIL_CC(0.00)[gmail.com]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; MID_RHS_MATCH_FROMTLD(0.00)[]; RCPT_COUNT_FIVE(0.00)[5]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim]; FREEMAIL_TO(0.00)[gmail.com,freebsd.org]; RCVD_TLS_LAST(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; MIME_TRACE(0.00)[0:+,1:+,2:~]; FREEMAIL_FROM(0.00)[gmail.com] X-Rspamd-Queue-Id: 4Q3fg21Bn7z4RGk X-Spamd-Bar: -- X-ThisMailContainsUnwantedMimeParts: N --0000000000001b5a4f05f9f0bedd Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable I don't know. This should be evaluated by you. I'm not involved so much in the technicalities : https://github.com/lm-sys/FastChat Let me understand what the Ada (117M) model is,if you want. I want to learn. On Sat, Apr 22, 2023 at 8:10=E2=80=AFPM Aryeh Friedman wrote: > Does GPT-3/3.5 come with a Ada (117M) model? > > On Sat, Apr 22, 2023 at 2:09=E2=80=AFPM Mario Marietto > wrote: > > > > And I'm even more sure that using a linux bhyve VM you can configure > chatgpt 3.5 / 4 even faster than using the linuxulator. > > > > On Sat, Apr 22, 2023 at 8:06=E2=80=AFPM Mario Marietto > wrote: > >> > >> Why are you insisting on chat gpt 2 when you can have chatgpt 3.5 / 4 > installed on your local FreeBSD machine through the linuxulator ? This wi= ll > be my next project. > >> > >> On Sat, Apr 22, 2023 at 8:00=E2=80=AFPM Aryeh Friedman < > aryeh.friedman@gmail.com> wrote: > >>> > >>> My next step is to wipe the vm and try again (this time making it > >>> scripted so I can do repeated test runs and very stuff systematically= ) > >>> > >>> On Sat, Apr 22, 2023 at 6:53=E2=80=AFAM Odhiambo Washington < > odhiambo@gmail.com> wrote: > >>> > > >>> > If you find a suitable, working version, please let me know. > >>> > > >>> > > >>> > On Sat, Apr 22, 2023 at 1:05=E2=80=AFPM Aryeh Friedman < > aryeh.friedman@gmail.com> wrote: > >>> >> > >>> >> Seems like 2 steps forward and one backwards I had it kind of > working > >>> >> under the wrong version of python going to wipe the machine and tr= y > >>> >> again with 3.7 I think I screwed something up.... and according to > >>> >> what I can ting the no tensorflow.contrib has to deal with version > of > >>> >> tensor flow... gpt-2 wants <2.0.0 it appears (preference for 1.15) > >>> >> > >>> >> On Sat, Apr 22, 2023 at 5:26=E2=80=AFAM Odhiambo Washington < > odhiambo@gmail.com> wrote: > >>> >> > > >>> >> > @Mario Marietto are you by any chance trying to address the issu= e > raised by Aryeh? > >>> >> > > >>> >> > ``` > >>> >> > ModuleNotFoundError: No module named 'tensorflow.contrib' > >>> >> > ``` > >>> >> > The problem is NOT about installing tensorflow, but rather > getting the correct version that will not lead to the above error. > >>> >> > > >>> >> > > >>> >> > > >>> >> > On Sat, Apr 22, 2023 at 12:19=E2=80=AFPM Mario Marietto < > marietto2008@gmail.com> wrote: > >>> >> >> > >>> >> >> marietto@marietto-nano:~$ python3 > >>> >> >> Python 3.10.6 (main, Mar 10 2023, 10:55:28) [GCC 11.3.0] on lin= ux > >>> >> >> Type "help", "copyright", "credits" or "license" for more > information. > >>> >> >> >>> import tensorflow as tf > >>> >> >> >>> tf.__version__ > >>> >> >> '2.12.0' > >>> >> >> >>> print(tf.reduce_sum(tf.random.normal([1000, 1000]))) > >>> >> >> tf.Tensor(51.500687, shape=3D(), dtype=3Dfloat32) > >>> >> >> > >>> >> >> > https://qengineering.eu/install-tensorflow-2.4.0-on-jetson-nano.html > >>> >> >> > >>> >> >> On Sat, Apr 22, 2023 at 10:47=E2=80=AFAM Odhiambo Washington < > odhiambo@gmail.com> wrote: > >>> >> >>> > >>> >> >>> > >>> >> >>> > >>> >> >>> On Sat, Apr 22, 2023 at 11:20=E2=80=AFAM Aryeh Friedman < > aryeh.friedman@gmail.com> wrote: > >>> >> >>>> > >>> >> >>>> On Fri, Apr 21, 2023 at 8:31=E2=80=AFAM Mario Marietto < > marietto2008@gmail.com> wrote: > >>> >> >>>> > > >>> >> >>>> > If you don't want to use the GPU,the commands should be mor= e > or less the following : > >>> >> >>>> > > >>> >> >>>> > > >>> >> >>>> > sudo touch /usr/local/etc/rc.d/ubuntu && chmod +x > /usr/local/etc/rc.d/ubuntu > >>> >> >>>> > > >>> >> >>>> > # Make it have this content: > >>> >> >>>> > > >>> >> >>>> > #!/bin/sh > >>> >> >>>> > # > >>> >> >>>> > # PROVIDE: ubuntu > >>> >> >>>> > # REQUIRE: archdep mountlate > >>> >> >>>> > # KEYWORD: nojail > >>> >> >>>> > # > >>> >> >>>> > # This is a modified version of /etc/rc.d/linux > >>> >> >>>> > # Based on the script by mrclksr: > >>> >> >>>> > # > https://github.com/mrclksr/linux-browser-installer/blob/main/rc.d/ubuntu.= in > >>> >> >>>> > # > >>> >> >>>> > . /etc/rc.subr > >>> >> >>>> > > >>> >> >>>> > name=3D"ubuntu" > >>> >> >>>> > desc=3D"Enable Ubuntu chroot, and Linux ABI" > >>> >> >>>> > rcvar=3D"ubuntu_enable" > >>> >> >>>> > start_cmd=3D"${name}_start" > >>> >> >>>> > stop_cmd=3D":" > >>> >> >>>> > > >>> >> >>>> > unmounted() > >>> >> >>>> > { > >>> >> >>>> > [ `stat -f "%d" "$1"` =3D=3D `stat -f "%d" "$1/.."` -a = \ > >>> >> >>>> > `stat -f "%i" "$1"` !=3D `stat -f "%i" "$1/.."` ] > >>> >> >>>> > } > >>> >> >>>> > > >>> >> >>>> > ubuntu_start() > >>> >> >>>> > { > >>> >> >>>> > local _emul_path _tmpdir > >>> >> >>>> > > >>> >> >>>> > load_kld -e 'linux(aout|elf)' linux > >>> >> >>>> > case `sysctl -n hw.machine_arch` in > >>> >> >>>> > amd64) > >>> >> >>>> > load_kld -e 'linux64elf' linux64 > >>> >> >>>> > ;; > >>> >> >>>> > esac > >>> >> >>>> > if [ -x /compat/ubuntu/sbin/ldconfigDisabled ]; then > >>> >> >>>> > _tmpdir=3D`mktemp -d -t linux-ldconfig` > >>> >> >>>> > /compat/ubuntu/sbin/ldconfig -C > ${_tmpdir}/ld.so.cache > >>> >> >>>> > if ! cmp -s ${_tmpdir}/ld.so.cache > /compat/ubuntu/etc/ld.so.cache; then > >>> >> >>>> > cat ${_tmpdir}/ld.so.cache > > /compat/ubuntu/etc/ld.so.cache > >>> >> >>>> > fi > >>> >> >>>> > rm -rf ${_tmpdir} > >>> >> >>>> > fi > >>> >> >>>> > > >>> >> >>>> > # Linux uses the pre-pts(4) tty naming scheme. > >>> >> >>>> > load_kld pty > >>> >> >>>> > > >>> >> >>>> > # Handle unbranded ELF executables by defaulting to > ELFOSABI_LINUX. > >>> >> >>>> > if [ `sysctl -ni kern.elf64.fallback_brand` -eq "-1" ]; > then > >>> >> >>>> > sysctl kern.elf64.fallback_brand=3D3 > /dev/null > >>> >> >>>> > fi > >>> >> >>>> > > >>> >> >>>> > if [ `sysctl -ni kern.elf32.fallback_brand` -eq "-1" ]; > then > >>> >> >>>> > sysctl kern.elf32.fallback_brand=3D3 > /dev/null > >>> >> >>>> > fi > >>> >> >>>> > sysctl compat.linux.emul_path=3D/compat/ubuntu > >>> >> >>>> > > >>> >> >>>> > _emul_path=3D"/compat/ubuntu" > >>> >> >>>> > unmounted "${_emul_path}/dev" && (mount -o nocover -t > devfs devfs "${_emul_path}/dev" || exit 1) > >>> >> >>>> > unmounted "${_emul_path}/dev/fd" && (mount -o > nocover,linrdlnk -t fdescfs fdescfs "${_emul_path}/dev/fd" || exit 1) > >>> >> >>>> > unmounted "${_emul_path}/dev/shm" && (mount -o > nocover,mode=3D1777 -t tmpfs tmpfs "${_emul_path}/dev/shm" || exit 1) > >>> >> >>>> > unmounted "${_emul_path}/home" && (mount -t nullfs /hom= e > "${_emul_path}/home" || exit 1) > >>> >> >>>> > unmounted "${_emul_path}/proc" && (mount -o nocover -t > linprocfs linprocfs "${_emul_path}/proc" || exit 1) > >>> >> >>>> > unmounted "${_emul_path}/sys" && (mount -o nocover -t > linsysfs linsysfs "${_emul_path}/sys" || exit 1) > >>> >> >>>> > unmounted "${_emul_path}/tmp" && (mount -t nullfs /tmp > "${_emul_path}/tmp" || exit 1) > >>> >> >>>> > unmounted /dev/fd && (mount -o nocover -t fdescfs > fdescfs /dev/fd || exit 1) > >>> >> >>>> > unmounted /proc && (mount -o nocover -t procfs procfs > /proc || exit 1) > >>> >> >>>> > true > >>> >> >>>> > } > >>> >> >>>> > > >>> >> >>>> > load_rc_config $name > >>> >> >>>> > run_rc_command "$1" > >>> >> >>>> > > >>> >> >>>> > sysrc ubuntu_enable=3DYES > >>> >> >>>> > > >>> >> >>>> > # Create necessary mount points for a working Linuxulator: > >>> >> >>>> > mkdir -p > {/compat/ubuntu/dev/fd,/compat/ubuntu/dev/shm,/compat/ubuntu/home,/compat= /ubuntu/tmp,/compat/ubuntu/proc,/compat/ubuntu/sys} > >>> >> >>>> > > >>> >> >>>> > # Start Ubuntu service: > >>> >> >>>> > service ubuntu start > >>> >> >>>> > > >>> >> >>>> > # Install needed packages: > >>> >> >>>> > pkg install debootstrap pulseaudio > >>> >> >>>> > > >>> >> >>>> > # Install Ubuntu 20.04 into /compat/ubuntu: > >>> >> >>>> > debootstrap --arch=3Damd64 --no-check-gpg focal /compat/ubu= ntu > >>> >> >>>> > > >>> >> >>>> > # Restart Ubuntu service to make sure everything is properl= y > mounted: > >>> >> >>>> > service ubuntu restart > >>> >> >>>> > > >>> >> >>>> > # Fix broken symlink: > >>> >> >>>> > cd /compat/ubuntu/lib64/ && rm ./ld-linux-x86-64.so.2 ; ln > -s ../lib/x86_64-linux-gnu/ld-2.31.so ld-linux-x86-64.so.2 > >>> >> >>>> > > >>> >> >>>> > # Chroot into your Linux environment: > >>> >> >>>> > chroot /compat/ubuntu /bin/bash > >>> >> >>>> > > >>> >> >>>> > # Set correct timezone inside your chroot: > >>> >> >>>> > printf "%b\n" "0.0 0 0.0\n0\nUTC" > /etc/adjtime > >>> >> >>>> > sudo dpkg-reconfigure tzdata # For some reason sudo is > necessary here, otherwise it fails. > >>> >> >>>> > > >>> >> >>>> > # Fix APT package manager: > >>> >> >>>> > printf "APT::Cache-Start 251658240;" > > /etc/apt/apt.conf.d/00aptitude > >>> >> >>>> > > >>> >> >>>> > # Enable more repositories: > >>> >> >>>> > printf "deb http://archive.ubuntu.com/ubuntu/ focal main > restricted universe multiverse" > /etc/apt/sources.list > >>> >> >>>> > > >>> >> >>>> > # Install required programs: > >>> >> >>>> > > >>> >> >>>> > apt update ; apt install -y apt-transport-https curl > fonts-symbola gnupg pulseaudio build-essential gcc gfortran > >>> >> >>>> > > >>> >> >>>> > # Exit out of chroot > >>> >> >>>> > exit > >>> >> >>>> > > >>> >> >>>> > # Fix x86_64-linux-gnu libraries path between ubuntu and > freebsd > >>> >> >>>> > cp -r /compat/ubuntu/usr/lib/x86_64-linux-gnu /lib > >>> >> >>>> > > >>> >> >>>> > > >>> >> >>>> > --> Installing PyTorch and your chatgpt github fork on > FreeBSD > >>> >> >>>> > > >>> >> >>>> > > >>> >> >>>> > # fetch > https://gist.githubusercontent.com/shkhln/40ef290463e78fb2b0000c60f4ad797= e/raw/f640983249607e38af405c95c457ce4afc85c608/uvm_ioctl_override.c > >>> >> >>>> > > >>> >> >>>> > # /compat/ubuntu/bin/gcc --sysroot=3D/compat/ubuntu -m64 > -std=3Dc99 -Wall -ldl -fPIC -shared -o dummy-uvm.so uvm_ioctl_override.c > >>> >> >>>> > > >>> >> >>>> > # pkg install linux-miniconda-installer > >>> >> >>>> > # miniconda-installer > >>> >> >>>> > # bash > >>> >> >>>> > # source /home/marietto/miniconda3/etc/profile.d/conda.sh > >>> >> >>>> > # conda activate > >>> >> >>>> > > >>> >> >>>> > (base) # conda activate pytorch > >>> >> >>>> > > >>> >> >>>> > (pytorch) # conda activate > >>> >> >>>> > > >>> >> >>>> > (base) # conda activate > >>> >> >>>> > > >>> >> >>>> > (base) # git clone your chatgpt github fork > >>> >> >>>> > >>> >> >>>> > >>> >> >>>> I have done that I think and get: > >>> >> >>>> > >>> >> >>>> (base) [babyspock@babyspock ~]$ python > >>> >> >>>> src/generate_unconditional_samples.py --model_name 117M > --nsamples 5 > >>> >> >>>> --length 512 > >>> >> >>>> python: can't open file > >>> >> >>>> '/usr/opt/babySpock/src/generate_unconditional_samples.py': > [Errno 2] > >>> >> >>>> No such file or directory > >>> >> >>>> (base) [babyspock@babyspock ~]$ cd gpt-2/ > >>> >> >>>> (base) [babyspock@babyspock ~/gpt-2]$ python > >>> >> >>>> src/generate_unconditional_samples.py --model_name 117M > --nsamples 5 > >>> >> >>>> --length 512 > >>> >> >>>> 2023-04-22 00:17:18.661083: I > tensorflow/tsl/cuda/cudart_stub.cc:28] > >>> >> >>>> Could not find cuda drivers on your machine, GPU will not be > used. > >>> >> >>>> 2023-04-22 00:17:18.710468: I > tensorflow/tsl/cuda/cudart_stub.cc:28] > >>> >> >>>> Could not find cuda drivers on your machine, GPU will not be > used. > >>> >> >>>> 2023-04-22 00:17:18.710951: I > >>> >> >>>> tensorflow/core/platform/cpu_feature_guard.cc:182] This > TensorFlow > >>> >> >>>> binary is optimized to use available CPU instructions in > >>> >> >>>> performance-critical operations. > >>> >> >>>> To enable the following instructions: AVX2 FMA, in other > operations, > >>> >> >>>> rebuild TensorFlow with the appropriate compiler flags. > >>> >> >>>> 2023-04-22 00:17:19.429409: W > >>> >> >>>> tensorflow/compiler/tf2tensorrt/utils/py_utils.cc:38] TF-TRT > Warning: > >>> >> >>>> Could not find TensorRT > >>> >> >>>> Traceback (most recent call last): > >>> >> >>>> File > "/usr/opt/babySpock/gpt-2/src/generate_unconditional_samples.py", > >>> >> >>>> line 9, in > >>> >> >>>> import model, sample, encoder > >>> >> >>>> File "/usr/opt/babySpock/gpt-2/src/model.py", line 3, in > > >>> >> >>>> from tensorflow.contrib.training import HParams > >>> >> >>>> ModuleNotFoundError: No module named 'tensorflow.contrib' > >>> >> >>> > >>> >> >>> > >>> >> >>> Use Python3.7 or earlier. > >>> >> >>> > >>> >> >>> -- > >>> >> >>> Best regards, > >>> >> >>> Odhiambo WASHINGTON, > >>> >> >>> Nairobi,KE > >>> >> >>> +254 7 3200 0004/+254 7 2274 3223 > >>> >> >>> "Oh, the cruft.", egrep -v '^$|^.*#' =C2=AF\_(=E3=83=84)_/=C2= =AF :-) > >>> >> >>> [How to ask smart questions: > http://www.catb.org/~esr/faqs/smart-questions.html] > >>> >> >> > >>> >> >> > >>> >> >> > >>> >> >> -- > >>> >> >> Mario. > >>> >> > > >>> >> > > >>> >> > > >>> >> > -- > >>> >> > Best regards, > >>> >> > Odhiambo WASHINGTON, > >>> >> > Nairobi,KE > >>> >> > +254 7 3200 0004/+254 7 2274 3223 > >>> >> > "Oh, the cruft.", egrep -v '^$|^.*#' =C2=AF\_(=E3=83=84)_/=C2=AF= :-) > >>> >> > [How to ask smart questions: > http://www.catb.org/~esr/faqs/smart-questions.html] > >>> >> > >>> >> > >>> >> > >>> >> -- > >>> >> Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org > >>> > > >>> > > >>> > > >>> > -- > >>> > Best regards, > >>> > Odhiambo WASHINGTON, > >>> > Nairobi,KE > >>> > +254 7 3200 0004/+254 7 2274 3223 > >>> > "Oh, the cruft.", egrep -v '^$|^.*#' =C2=AF\_(=E3=83=84)_/=C2=AF :-= ) > >>> > [How to ask smart questions: > http://www.catb.org/~esr/faqs/smart-questions.html] > >>> > >>> > >>> > >>> -- > >>> Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org > >> > >> > >> > >> -- > >> Mario. > > > > > > > > -- > > Mario. > > > > -- > Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org > --=20 Mario. --0000000000001b5a4f05f9f0bedd Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
I don't know. This should be evaluated by you. I&= #39;m not involved so much in the technicalities :


Let me understand what the Ada (1= 17M) model is,if you want. I want to learn.=C2=A0

On Sat, Apr 22,= 2023 at 8:10=E2=80=AFPM Aryeh Friedman <aryeh.friedman@gmail.com> wrote:
Does GPT-3/3.5 come with a Ada (117M) = model?

On Sat, Apr 22, 2023 at 2:09=E2=80=AFPM Mario Marietto <marietto2008@gmail.com> = wrote:
>
> And I'm even more sure that using a linux bhyve VM you can configu= re chatgpt 3.5 / 4 even faster than using the linuxulator.
>
> On Sat, Apr 22, 2023 at 8:06=E2=80=AFPM Mario Marietto <marietto2008@gmail.com= > wrote:
>>
>> Why are you insisting on chat gpt 2 when you can have chatgpt 3.5 = / 4 installed on your local FreeBSD machine through the linuxulator ? This = will be my next project.
>>
>> On Sat, Apr 22, 2023 at 8:00=E2=80=AFPM Aryeh Friedman <aryeh.friedman@gmail= .com> wrote:
>>>
>>> My next step is to wipe the vm and try again (this time making= it
>>> scripted so I can do repeated test runs and very stuff systema= tically)
>>>
>>> On Sat, Apr 22, 2023 at 6:53=E2=80=AFAM Odhiambo Washington &l= t;odhiambo@gmail.co= m> wrote:
>>> >
>>> > If you find a suitable, working version, please let me kn= ow.
>>> >
>>> >
>>> > On Sat, Apr 22, 2023 at 1:05=E2=80=AFPM Aryeh Friedman &l= t;aryeh.fried= man@gmail.com> wrote:
>>> >>
>>> >> Seems like 2 steps forward and one backwards I had it= kind of working
>>> >> under the wrong version of python going to wipe the m= achine and try
>>> >> again with 3.7 I think I screwed something up.... and= according to
>>> >> what I can ting the no tensorflow.contrib has to deal= with version of
>>> >> tensor flow... gpt-2 wants <2.0.0 it appears (pref= erence for 1.15)
>>> >>
>>> >> On Sat, Apr 22, 2023 at 5:26=E2=80=AFAM Odhiambo Wash= ington <odhiambo= @gmail.com> wrote:
>>> >> >
>>> >> > @Mario Marietto are you by any chance trying to = address the issue raised by Aryeh?
>>> >> >
>>> >> > ```
>>> >> > ModuleNotFoundError: No module named 'tensor= flow.contrib'
>>> >> > ```
>>> >> > The problem is NOT about installing tensorflow, = but rather getting the correct version that will not lead to the above erro= r.
>>> >> >
>>> >> >
>>> >> >
>>> >> > On Sat, Apr 22, 2023 at 12:19=E2=80=AFPM Mario M= arietto <mar= ietto2008@gmail.com> wrote:
>>> >> >>
>>> >> >> marietto@marietto-nano:~$ python3
>>> >> >> Python 3.10.6 (main, Mar 10 2023, 10:55:28) = [GCC 11.3.0] on linux
>>> >> >> Type "help", "copyright"= , "credits" or "license" for more information.
>>> >> >> >>> import tensorflow as tf
>>> >> >> >>> tf.__version__
>>> >> >> '2.12.0'
>>> >> >> >>> print(tf.reduce_sum(tf.random.n= ormal([1000, 1000])))
>>> >> >> tf.Tensor(51.500687, shape=3D(), dtype=3Dflo= at32)
>>> >> >>
>>> >> >> h= ttps://qengineering.eu/install-tensorflow-2.4.0-on-jetson-nano.html
>>> >> >>
>>> >> >> On Sat, Apr 22, 2023 at 10:47=E2=80=AFAM Odh= iambo Washington <odhiambo@gmail.com> wrote:
>>> >> >>>
>>> >> >>>
>>> >> >>>
>>> >> >>> On Sat, Apr 22, 2023 at 11:20=E2=80=AFAM= Aryeh Friedman <aryeh.friedman@gmail.com> wrote:
>>> >> >>>>
>>> >> >>>> On Fri, Apr 21, 2023 at 8:31=E2=80= =AFAM Mario Marietto <marietto2008@gmail.com> wrote:
>>> >> >>>> >
>>> >> >>>> > If you don't want to use th= e GPU,the commands should be more or less the following :
>>> >> >>>> >
>>> >> >>>> >
>>> >> >>>> > sudo touch /usr/local/etc/rc.d/= ubuntu && chmod +x /usr/local/etc/rc.d/ubuntu
>>> >> >>>> >
>>> >> >>>> > # Make it have this content: >>> >> >>>> >
>>> >> >>>> > #!/bin/sh
>>> >> >>>> > #
>>> >> >>>> > # PROVIDE: ubuntu
>>> >> >>>> > # REQUIRE: archdep mountlate >>> >> >>>> > # KEYWORD: nojail
>>> >> >>>> > #
>>> >> >>>> > # This is a modified version of= /etc/rc.d/linux
>>> >> >>>> > # Based on the script by mrclks= r:
>>> >> >>>> > # https://github.com/mrclksr/linux-browser-installer/blo= b/main/rc.d/ubuntu.in
>>> >> >>>> > #
>>> >> >>>> > . /etc/rc.subr
>>> >> >>>> >
>>> >> >>>> > name=3D"ubuntu"
>>> >> >>>> > desc=3D"Enable Ubuntu chro= ot, and Linux ABI"
>>> >> >>>> > rcvar=3D"ubuntu_enable&quo= t;
>>> >> >>>> > start_cmd=3D"${name}_start= "
>>> >> >>>> > stop_cmd=3D":"
>>> >> >>>> >
>>> >> >>>> > unmounted()
>>> >> >>>> > {
>>> >> >>>> >=C2=A0 =C2=A0 =C2=A0[ `stat -f &= quot;%d" "$1"` =3D=3D `stat -f "%d" "$1/..&qu= ot;` -a \
>>> >> >>>> >=C2=A0 =C2=A0 =C2=A0 =C2=A0`stat= -f "%i" "$1"` !=3D `stat -f "%i" "$1/..= "` ]
>>> >> >>>> > }
>>> >> >>>> >
>>> >> >>>> > ubuntu_start()
>>> >> >>>> > {
>>> >> >>>> >=C2=A0 =C2=A0 =C2=A0local _emul_= path _tmpdir
>>> >> >>>> >
>>> >> >>>> >=C2=A0 =C2=A0 =C2=A0load_kld -e = 'linux(aout|elf)' linux
>>> >> >>>> >=C2=A0 =C2=A0 =C2=A0case `sysctl= -n hw.machine_arch` in
>>> >> >>>> >=C2=A0 =C2=A0 =C2=A0amd64)
>>> >> >>>> >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0load_kld -e 'linux64elf' linux64
>>> >> >>>> >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0;;
>>> >> >>>> >=C2=A0 =C2=A0 =C2=A0esac
>>> >> >>>> >=C2=A0 =C2=A0 =C2=A0if [ -x /com= pat/ubuntu/sbin/ldconfigDisabled ]; then
>>> >> >>>> >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0_tmpdir=3D`mktemp -d -t linux-ldconfig`
>>> >> >>>> >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0/compat/ubuntu/sbin/ldconfig -C ${_tmpdir}/ld.so.cache
>>> >> >>>> >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0if ! cmp -s ${_tmpdir}/ld.so.cache /compat/ubuntu/etc/ld.so.cache; then<= br> >>> >> >>>> >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0cat ${_tmpdir}/ld.so.cache > /compat/ubuntu/etc/ld.so.c= ache
>>> >> >>>> >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0fi
>>> >> >>>> >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0rm -rf ${_tmpdir}
>>> >> >>>> >=C2=A0 =C2=A0 =C2=A0fi
>>> >> >>>> >
>>> >> >>>> >=C2=A0 =C2=A0 =C2=A0# Linux uses= the pre-pts(4) tty naming scheme.
>>> >> >>>> >=C2=A0 =C2=A0 =C2=A0load_kld pty=
>>> >> >>>> >
>>> >> >>>> >=C2=A0 =C2=A0 =C2=A0# Handle unb= randed ELF executables by defaulting to ELFOSABI_LINUX.
>>> >> >>>> >=C2=A0 =C2=A0 =C2=A0if [ `sysctl= -ni kern.elf64.fallback_brand` -eq "-1" ]; then
>>> >> >>>> >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0sysctl kern.elf64.fallback_brand=3D3 > /dev/null
>>> >> >>>> >=C2=A0 =C2=A0 =C2=A0fi
>>> >> >>>> >
>>> >> >>>> >=C2=A0 =C2=A0 =C2=A0if [ `sysctl= -ni kern.elf32.fallback_brand` -eq "-1" ]; then
>>> >> >>>> >=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0sysctl kern.elf32.fallback_brand=3D3 > /dev/null
>>> >> >>>> >=C2=A0 =C2=A0 =C2=A0fi
>>> >> >>>> >=C2=A0 =C2=A0 =C2=A0sysctl compa= t.linux.emul_path=3D/compat/ubuntu
>>> >> >>>> >
>>> >> >>>> >=C2=A0 =C2=A0 =C2=A0_emul_path= =3D"/compat/ubuntu"
>>> >> >>>> >=C2=A0 =C2=A0 =C2=A0unmounted &q= uot;${_emul_path}/dev" && (mount -o nocover -t devfs devfs &qu= ot;${_emul_path}/dev" || exit 1)
>>> >> >>>> >=C2=A0 =C2=A0 =C2=A0unmounted &q= uot;${_emul_path}/dev/fd" && (mount -o nocover,linrdlnk -t fde= scfs fdescfs "${_emul_path}/dev/fd" || exit 1)
>>> >> >>>> >=C2=A0 =C2=A0 =C2=A0unmounted &q= uot;${_emul_path}/dev/shm" && (mount -o nocover,mode=3D1777 -t= tmpfs tmpfs "${_emul_path}/dev/shm" || exit 1)
>>> >> >>>> >=C2=A0 =C2=A0 =C2=A0unmounted &q= uot;${_emul_path}/home" && (mount -t nullfs /home "${_emu= l_path}/home" || exit 1)
>>> >> >>>> >=C2=A0 =C2=A0 =C2=A0unmounted &q= uot;${_emul_path}/proc" && (mount -o nocover -t linprocfs linp= rocfs "${_emul_path}/proc" || exit 1)
>>> >> >>>> >=C2=A0 =C2=A0 =C2=A0unmounted &q= uot;${_emul_path}/sys" && (mount -o nocover -t linsysfs linsys= fs "${_emul_path}/sys" || exit 1)
>>> >> >>>> >=C2=A0 =C2=A0 =C2=A0unmounted &q= uot;${_emul_path}/tmp" && (mount -t nullfs /tmp "${_emul_= path}/tmp" || exit 1)
>>> >> >>>> >=C2=A0 =C2=A0 =C2=A0unmounted /d= ev/fd && (mount -o nocover -t fdescfs fdescfs /dev/fd || exit 1) >>> >> >>>> >=C2=A0 =C2=A0 =C2=A0unmounted /p= roc && (mount -o nocover -t procfs procfs /proc || exit 1)
>>> >> >>>> >=C2=A0 =C2=A0 =C2=A0true
>>> >> >>>> > }
>>> >> >>>> >
>>> >> >>>> > load_rc_config $name
>>> >> >>>> > run_rc_command "$1" >>> >> >>>> >
>>> >> >>>> > sysrc ubuntu_enable=3DYES
>>> >> >>>> >
>>> >> >>>> > # Create necessary mount points= for a working Linuxulator:
>>> >> >>>> > mkdir -p {/compat/ubuntu/dev/fd= ,/compat/ubuntu/dev/shm,/compat/ubuntu/home,/compat/ubuntu/tmp,/compat/ubun= tu/proc,/compat/ubuntu/sys}
>>> >> >>>> >
>>> >> >>>> > # Start Ubuntu service:
>>> >> >>>> > service ubuntu start
>>> >> >>>> >
>>> >> >>>> > # Install needed packages:
>>> >> >>>> > pkg install debootstrap pulseau= dio
>>> >> >>>> >
>>> >> >>>> > # Install Ubuntu 20.04 into /co= mpat/ubuntu:
>>> >> >>>> > debootstrap --arch=3Damd64 --no= -check-gpg focal /compat/ubuntu
>>> >> >>>> >
>>> >> >>>> > # Restart Ubuntu service to mak= e sure everything is properly mounted:
>>> >> >>>> > service ubuntu restart
>>> >> >>>> >
>>> >> >>>> > # Fix broken symlink:
>>> >> >>>> > cd /compat/ubuntu/lib64/ &&= amp; rm ./ld-linux-x86-64.so.2 ; ln -s ../lib/x86_64-linux-gnu/ld-2.31.so ld-li= nux-x86-64.so.2
>>> >> >>>> >
>>> >> >>>> > # Chroot into your Linux enviro= nment:
>>> >> >>>> > chroot /compat/ubuntu /bin/bash=
>>> >> >>>> >
>>> >> >>>> > # Set correct timezone inside y= our chroot:
>>> >> >>>> > printf "%b\n" "0= .0 0 0.0\n0\nUTC" > /etc/adjtime
>>> >> >>>> > sudo dpkg-reconfigure tzdata # = For some reason sudo is necessary here, otherwise it fails.
>>> >> >>>> >
>>> >> >>>> > # Fix APT package manager:
>>> >> >>>> > printf "APT::Cache-Start 2= 51658240;" > /etc/apt/apt.conf.d/00aptitude
>>> >> >>>> >
>>> >> >>>> > # Enable more repositories:
>>> >> >>>> > printf "deb http:/= /archive.ubuntu.com/ubuntu/ focal main restricted universe multiverse&q= uot; > /etc/apt/sources.list
>>> >> >>>> >
>>> >> >>>> > # Install required programs: >>> >> >>>> >
>>> >> >>>> > apt update ; apt install -y apt= -transport-https curl fonts-symbola gnupg pulseaudio build-essential gcc gf= ortran
>>> >> >>>> >
>>> >> >>>> > # Exit out of chroot
>>> >> >>>> > exit
>>> >> >>>> >
>>> >> >>>> > # Fix x86_64-linux-gnu librarie= s path between ubuntu and freebsd
>>> >> >>>> > cp -r /compat/ubuntu/usr/lib/x8= 6_64-linux-gnu /lib
>>> >> >>>> >
>>> >> >>>> >
>>> >> >>>> > --> Installing PyTorch and y= our chatgpt github fork on FreeBSD
>>> >> >>>> >
>>> >> >>>> >
>>> >> >>>> > # fetch https://gist.githubusercontent.com/shkhln/40ef290463e78fb2= b0000c60f4ad797e/raw/f640983249607e38af405c95c457ce4afc85c608/uvm_ioctl_ove= rride.c
>>> >> >>>> >
>>> >> >>>> > # /compat/ubuntu/bin/gcc --sysr= oot=3D/compat/ubuntu -m64 -std=3Dc99 -Wall -ldl -fPIC -shared -o dummy-uvm.= so uvm_ioctl_override.c
>>> >> >>>> >
>>> >> >>>> > # pkg install linux-miniconda-i= nstaller
>>> >> >>>> > # miniconda-installer
>>> >> >>>> > # bash
>>> >> >>>> > # source /home/marietto/minicon= da3/etc/profile.d/conda.sh
>>> >> >>>> > # conda activate
>>> >> >>>> >
>>> >> >>>> > (base) # conda activate pytorch=
>>> >> >>>> >
>>> >> >>>> > (pytorch) # conda activate
>>> >> >>>> >
>>> >> >>>> > (base) # conda activate
>>> >> >>>> >
>>> >> >>>> > (base) # git clone your chatgpt= github fork
>>> >> >>>>
>>> >> >>>>
>>> >> >>>> I have done that I think and get: >>> >> >>>>
>>> >> >>>> (base) [babyspock@babyspock ~]$ pyth= on
>>> >> >>>> src/generate_unconditional_samples.p= y --model_name 117M --nsamples 5
>>> >> >>>> --length 512
>>> >> >>>> python: can't open file
>>> >> >>>> '/usr/opt/babySpock/src/generate= _unconditional_samples.py': [Errno 2]
>>> >> >>>> No such file or directory
>>> >> >>>> (base) [babyspock@babyspock ~]$ cd g= pt-2/
>>> >> >>>> (base) [babyspock@babyspock ~/gpt-2]= $ python
>>> >> >>>> src/generate_unconditional_samples.p= y --model_name 117M --nsamples 5
>>> >> >>>> --length 512
>>> >> >>>> 2023-04-22 00:17:18.661083: I tensor= flow/tsl/cuda/cudart_stub.cc:28]
>>> >> >>>> Could not find cuda drivers on your = machine, GPU will not be used.
>>> >> >>>> 2023-04-22 00:17:18.710468: I tensor= flow/tsl/cuda/cudart_stub.cc:28]
>>> >> >>>> Could not find cuda drivers on your = machine, GPU will not be used.
>>> >> >>>> 2023-04-22 00:17:18.710951: I
>>> >> >>>> tensorflow/core/platform/cpu_feature= _guard.cc:182] This TensorFlow
>>> >> >>>> binary is optimized to use available= CPU instructions in
>>> >> >>>> performance-critical operations.
>>> >> >>>> To enable the following instructions= : AVX2 FMA, in other operations,
>>> >> >>>> rebuild TensorFlow with the appropri= ate compiler flags.
>>> >> >>>> 2023-04-22 00:17:19.429409: W
>>> >> >>>> tensorflow/compiler/tf2tensorrt/util= s/py_utils.cc:38] TF-TRT Warning:
>>> >> >>>> Could not find TensorRT
>>> >> >>>> Traceback (most recent call last): >>> >> >>>>=C2=A0 =C2=A0File "/usr/opt/baby= Spock/gpt-2/src/generate_unconditional_samples.py",
>>> >> >>>> line 9, in <module>
>>> >> >>>>=C2=A0 =C2=A0 =C2=A0import model, sam= ple, encoder
>>> >> >>>>=C2=A0 =C2=A0File "/usr/opt/baby= Spock/gpt-2/src/model.py", line 3, in <module>
>>> >> >>>>=C2=A0 =C2=A0 =C2=A0from tensorflow.c= ontrib.training import HParams
>>> >> >>>> ModuleNotFoundError: No module named= 'tensorflow.contrib'
>>> >> >>>
>>> >> >>>
>>> >> >>> Use Python3.7 or earlier.
>>> >> >>>
>>> >> >>> --
>>> >> >>> Best regards,
>>> >> >>> Odhiambo WASHINGTON,
>>> >> >>> Nairobi,KE
>>> >> >>> +254 7 3200 0004/+254 7 2274 3223
>>> >> >>> "Oh, the cruft.", egrep -v = 9;^$|^.*#' =C2=AF\_(=E3=83=84)_/=C2=AF :-)
>>> >> >>> [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]
>>> >> >>
>>> >> >>
>>> >> >>
>>> >> >> --
>>> >> >> Mario.
>>> >> >
>>> >> >
>>> >> >
>>> >> > --
>>> >> > Best regards,
>>> >> > Odhiambo WASHINGTON,
>>> >> > Nairobi,KE
>>> >> > +254 7 3200 0004/+254 7 2274 3223
>>> >> > "Oh, the cruft.", egrep -v '^$|^.*= #' =C2=AF\_(=E3=83=84)_/=C2=AF :-)
>>> >> > [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]
>>> >>
>>> >>
>>> >>
>>> >> --
>>> >> Aryeh M. Friedman, Lead Developer, http://www.Petite= Cloud.org
>>> >
>>> >
>>> >
>>> > --
>>> > Best regards,
>>> > Odhiambo WASHINGTON,
>>> > Nairobi,KE
>>> > +254 7 3200 0004/+254 7 2274 3223
>>> > "Oh, the cruft.", egrep -v '^$|^.*#' = =C2=AF\_(=E3=83=84)_/=C2=AF :-)
>>> > [How to ask smart questions: htt= p://www.catb.org/~esr/faqs/smart-questions.html]
>>>
>>>
>>>
>>> --
>>> Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org=
>>
>>
>>
>> --
>> Mario.
>
>
>
> --
> Mario.



--
Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org


--
Mario.
--0000000000001b5a4f05f9f0bedd--