From nobody Sat Nov 25 22:20:33 2023 X-Original-To: freebsd-arm@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4Sd5sh32Cpz528pS; Sat, 25 Nov 2023 22:21:12 +0000 (UTC) (envelope-from marietto2008@gmail.com) Received: from mail-ej1-x633.google.com (mail-ej1-x633.google.com [IPv6:2a00:1450:4864:20::633]) (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 4Sd5sh0FJrz3fc5; Sat, 25 Nov 2023 22:21:12 +0000 (UTC) (envelope-from marietto2008@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-ej1-x633.google.com with SMTP id a640c23a62f3a-a00191363c1so445272766b.0; Sat, 25 Nov 2023 14:21:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1700950870; x=1701555670; darn=freebsd.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=t/lSNxASWRvsK2cphJI1ZwX564P/D/fkfRr4BwwJkyA=; b=jkrnr40BYs43XvUxtYhA+UdOh6tOUfNhMjLZTZBkmoTgDQG+XGp5JniHEN6Sqefl37 VIZ+LdGQUvf0omiX/o+lHFVeEOwFrqUEQZr1KVdCETfeOcR8Tj2Cce/+ESvuJiG2gpH3 daKP0mlClK4KLAFBF62bT66HAnO7qmGgjSKG7s16c3syIHWLmJsJQyJ3+OEbF+Cce21K HTaZOJr6FNSZZO28IpEmto4LWkUAabtt3Tz+mlJby3SPzJRqPyMrkODjXx+9CvxfG7NI 3Vuvy3vjDPUeM31FuTwh8DaSkXGMVYfQo/hQ9KV8qxJSgPSwbnROB0Y0/bVOW9oiZ5wH T4PA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1700950870; x=1701555670; 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=t/lSNxASWRvsK2cphJI1ZwX564P/D/fkfRr4BwwJkyA=; b=INwETliex+aPCGivvr38h9lXRAahV/MFa+nLqEVuqCiyI/WPomVY5b8U/6mboKAx06 jrKdeMDVNQpHTx5Su4O2Y4ylFdHcCLqjanfMjHzUMWEX0VQUwRtaO4Haj6J5x2T1q8kg BYrlok0kyP6OjAfcdMnSH0tIpG+hlYS5TPfiVMFYf+muvXa5o1+boWNnzTlLBtEz4CqM EbUIL6Iytnr94zO3FScwgBM8krwPj6PW9SSwkcMsUdUoG0+UVbPHW5ueTJIb6y5G1ggO rqGCHXooLdJA6D7fBCzHHzl/O8Ho5mG0Ob7ei+rctXfLS0lwmzXE71Qjr2yUROHIRY3K c2YA== X-Gm-Message-State: AOJu0YwQBu0HE7pjK1sEKJY81qTvK6+G9QvCiBHkru5/HMpjZHYYju4Q mI2uJC+pc9mVHMJ50IVrgtuUUj9MooAm4kOREFHY7zOyeKY= X-Google-Smtp-Source: AGHT+IEhkzwilMD6ERaL2bwBn3rOcuTDkx1lGUDZ5xkUD+poku47ky/zmkiWI0tfZHohL3AQulxcriuBDhJofy1Va5I= X-Received: by 2002:a17:906:dfcf:b0:a04:937a:f8b0 with SMTP id jt15-20020a170906dfcf00b00a04937af8b0mr5281464ejc.28.1700950869800; Sat, 25 Nov 2023 14:21:09 -0800 (PST) List-Id: Porting FreeBSD to ARM processors List-Archive: https://lists.freebsd.org/archives/freebsd-arm List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arm@freebsd.org MIME-Version: 1.0 References: In-Reply-To: From: Mario Marietto Date: Sat, 25 Nov 2023 23:20:33 +0100 Message-ID: Subject: Re: Should we boot the FreeBSD kernel in ELF format or in zImage format ? How? To: Warner Losh Cc: freebsd-hackers , freebsd-arm@freebsd.org, FreeBSD Current , FreeBSD Mailing List , freebsd-xen@freebsd.org, royger@freebsd.org Content-Type: multipart/alternative; boundary="0000000000005ff95f060b017cde" X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated 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-Queue-Id: 4Sd5sh0FJrz3fc5 --0000000000005ff95f060b017cde Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable I really don't know where to start. It sounds too technical for me. I don't even know what to ask to understand where to start. mmm...can someone provide some documentation ? but not too much dense with technicalities. Thanks. On Sat, Nov 25, 2023 at 6:02=E2=80=AFPM Warner Losh wrote: > > > On Sat, Nov 25, 2023 at 4:41=E2=80=AFAM Mario Marietto > wrote: > >> Hello to everyone. >> >> we have just virtualized Debian 12 on our arm (32 bit) Chromebook. As >> host / dom0 we have chosen Devuan 5,and for guest / domU,Debian 12. It >> works great. But our goal is different. We want to virtualize FreeBSD as >> domU. Can we have a working Xen PV network driver for a FreeBSD arm gues= t >> ?. I found that Julien Grall has ported the Xen drivers to FreeBSD on ar= m. >> I would like to know if Julien's work was accepted upstream by FreeBSD, = in >> which case FreeBSD as a Xen guest on arm should work if we enable the Xe= n >> PV drivers in the FreeBSD on arm kernel. If Julien's work was not accept= ed >> upstream by FreeBSD, we will have to find his patches and apply them >> ourselves to the FreeBSD on arm kernel. >> >> We found these slides : >> >> >> https://events.static.linuxfound.org/sites/events/files/slides/Porting%2= 0FreeBSD%20on%20Xen%20on%20ARM%20.pdf >> >> Slide 13 refers to a XENHVM FreeBSD on arm kernel config - that is what >> we want to find. >> >> It looks like when that slide presentation was written, there were some >> limitations on FreeBSD Xen guests. For example, for our debian bookworm >> guest, I am using vcpus =3D '2' to match the number of real cpus on our >> Chromebook, but slide 13 mentions support for only 1 VCPU with a FreeBSD >> guest, so I will need to change that vcpus =3D '1' in the FreeBSD guest >> config unless support for 2 or more vcpus was added later, which is >> possible because that slide presentation is 9 years old. >> >> Here is where I would expect to find the XENHVM FreeBSD on arm kernel >> config file: >> >> https://cgit.freebsd.org/src/tree/sys/arm/conf >> >> But it is not there unless I am not understanding something correctly. >> For now, unfortunately conclude that the support for Xen on arm that Jul= ien >> Grall mentioned in that slide presentation 9 years ago was never added t= o >> the official FreeBSD source code. I am searching the web now to see if t= he >> patches that Julien Grall wrote are still posted somewhere online. If we >> cannot find them, we can ask here and on the xen-users mailing list. Jul= ien >> regularly reads that list and responds to question about Xen on arm, so = I >> think he will tell us how to find the patches if we cannot find them onl= ine. >> >> According to this page from the FreeBSD wiki: >> >> https://wiki.freebsd.org/Xen >> >> I think FreeBSD only supports Xen on x86, not arm. So this is going to b= e >> a bit of a challenge to get a Xen FreeBSD guest on arm working. We know >> Julien Grall has some patches that made it work in the past ! >> >> I found a slightly newer slide presentation by Julien here: >> >> https://www.slideshare.net/xen_com_mgr/bsdcan-2015-how-to-port-your-bsd >> >> It is about the same, but it mentions the GENERIC FreeBSD kernel support= s >> Xen on arm64, but still says we need the XENHVM FreeBSD config for Xen o= n >> arm 32 bit, which I haven't found online yet. >> >> Please,take a look at this output of the linux kernel that can boot on >> Xen, and the FreeBSD kernel that cannot : >> >> >> % file zImage-6.1.59-stb-xen-cbe+ >> zImage-6.1.59-stb-xen-cbe+: Linux kernel ARM boot executable zImage (lit= tle-endian) >> >> % file FREEBSD-XENVIRT >> FREEBSD-XENVIRT: ELF 32-bit LSB executable, ARM, EABI5 version 1 (SYSV),= dynamically linked, interpreter /red/herring, for FreeBSD 11.0 (1100048), = not stripped >> >> >> The FreeBSD kernel that won't boot is in ELF format but the Linux kernel >> that does boot is in zImage format. >> >> I spent time reading the docs on xenbits.xenproject.org, and according >> to those docs Xen on arm only knows how to boot a kernel in the zImage >> format, so the FreeBSD kernel is in a format that modern Xen incorrectly >> detects as an x86 kernel. >> >> I also watched Julien Grall's 30 minute video presentation of his work t= o >> boot FreeBSD/arm on Xen at FOSDEM 2014 here : >> >> https://archive.fosdem.org/2014/schedule/event/freebsd_xen_arm/ >> >> In that video, and in other places, Julien mentions that the boot ABI fo= r >> FreeBSD/arm on Xen was not yet developed and he was getting occasional >> crashes and needed to investigate the problem. He mentioned the zImage A= BI >> that Linux uses, but pointed out FreeBSD does not use that format, and b= ack >> then it was an open question which format to use to boot FreeBSD/arm on >> Xen. Unfortunately, nine years later, the only supported format is still >> the zImage format that Linux uses. >> >> It looks like Julien's work back then was using an ELF binary to boot >> FreeBSD/arm on Xen instead of the supported zImage format that Linux use= s >> and the modern Xen toolstack exits with an error when trying to boot the >> FreeBSD ELF formatted binary that Julien's patch creates. So the best >> solution would be to try to port the rules to build a FreeBSD kernel in = the >> zImage format instead of the ELF format. I have been studying the Makefi= les >> in Linux to see how Linux builds the Linux arm kernel in the zImage form= at, >> but it is not trivial to understand >> > > Look at kernel.bin in FreeBSD's kernel. It's enabled -DWITH_KERNEL_BIN. I= t > should be easy to adapt the target to build that. I've done similar thing= s > with u-boot formats in the past, but that was 4 employers and 20 years ag= o > now. > > This path is not well trod. I do know that arm64 virtualization with bhyv= e > is hitting the tree. I'm not sure how easy/hard this will be to modernize= . > I'm interested to see how your explorations go. > > Warner > --=20 Mario. --0000000000005ff95f060b017cde Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
I really don't know where to start. It sounds too tech= nical for me. I don't even know what to ask to understand where to star= t. mmm...can someone provide some documentation ? but not too much dense wi= th technicalities. Thanks.

On Sat, Nov 25, 2023 at 6:02=E2=80=AFPM Warn= er Losh <imp@bsdimp.com> wrote:=


On Sat, Nov 25, 2023 at 4:41=E2=80=AFAM Mario Mariet= to <marietto= 2008@gmail.com> wrote:
= Hello to everyone.

we have just virtualized Debian 12 on our ar= m (32 bit) Chromebook. As host / dom0 we have chosen Devuan 5,and for guest / domU,Debian 12. It=20 works great. But our goal is different. We want to virtualize FreeBSD as domU. Can we have a working Xen PV network driver for a FreeBSD arm=20 guest ?. I found that Julien Grall has ported the Xen drivers to FreeBSD on arm. I would like to know if Julien's work was accepted upstream by= =20 FreeBSD, in which case FreeBSD as a Xen guest on arm should work if we=20 enable the Xen PV drivers in the FreeBSD on arm kernel. If Julien's wor= k was not accepted upstream by FreeBSD, we will have to find his patches=20 and apply them ourselves to the FreeBSD on arm kernel.

We found these slides :

https://events.static.linuxfound.org/sites/events/file= s/slides/Porting%20FreeBSD%20on%20Xen%20on%20ARM%20.pdf

Slide 13 refers to a XENHVM FreeBSD on arm kernel config - that is what = we want to find.

It looks like when that slide presentation was written, there were=20 some limitations on FreeBSD Xen guests. For example, for our debian=20 bookworm guest, I am using vcpus =3D '2' to match the number of rea= l cpus=20 on our Chromebook, but slide 13 mentions support for only 1 VCPU with a=20 FreeBSD guest, so I will need to change that vcpus =3D '1' in the F= reeBSD=20 guest config unless support for 2 or more vcpus was added later, which=20 is possible because that slide presentation is 9 years old.

Here is where I would expect to find the XENHVM FreeBSD on arm kernel co= nfig file:

https://cgit.freebsd.org/src/tree/sys/arm/= conf

But it is not there unless I am not understanding something=20 correctly. For now, unfortunately conclude that the support for Xen on=20 arm that Julien Grall mentioned in that slide presentation 9 years ago=20 was never added to the official FreeBSD source code. I am searching the=20 web now to see if the patches that Julien Grall wrote are still posted=20 somewhere online. If we cannot find them, we can ask here and on the=20 xen-users mailing list. Julien regularly reads that list and responds to question about Xen on arm, so I think he will tell us how to find the=20 patches if we cannot find them online.

According to this page from the FreeBSD wiki:

https://wiki.freebsd.org/Xen

I think FreeBSD only supports Xen on x86, not arm. So this is going=20 to be a bit of a challenge to get a Xen FreeBSD guest on arm working. We know Julien Grall has some patches that made it work in the past !

I found a slightly newer slide presentation by Julien here:

https://www.slide= share.net/xen_com_mgr/bsdcan-2015-how-to-port-your-bsd

It is about the same, but it mentions the GENERIC FreeBSD kernel=20 supports Xen on arm64, but still says we need the XENHVM FreeBSD config=20 for Xen on arm 32 bit, which I haven't found online yet.

Please,take a look at this output of the linux kernel that can boot on X= en, and the FreeBSD kernel that cannot :


% file zImage-6.1.59-stb-xen-cbe+
zImage-6.1.59-stb-xen-cbe+: Linux kernel ARM boot executable zImage (little=
-endian)

% file FREEBSD-XENVIRT         =20
FREEBSD-XENVIRT: ELF 32-bit LSB executable, ARM, EABI5 version 1 (SYSV), dy=
namically linked, interpreter /red/herring, for FreeBSD 11.0 (1100048), not=
 stripped


The FreeBSD kernel that won't boot is in ELF format but t= he Linux kernel that does boot is in zImage format.

I spent time reading the docs on xenbits.xenproject.org, and=20 according to those docs Xen on arm only knows how to boot a kernel in=20 the zImage format, so the FreeBSD kernel is in a format that modern Xen=20 incorrectly detects as an x86 kernel.

I also watched Julien Grall's 30 minute video presentation of his wo= rk to boot FreeBSD/arm on Xen at FOSDEM 2014 here :

https://archive.fosdem.or= g/2014/schedule/event/freebsd_xen_arm/

In that video, and in other places, Julien mentions that the boot ABI for FreeBSD/arm on Xen was not yet developed and he was getting=20 occasional crashes and needed to investigate the problem. He mentioned=20 the zImage ABI that Linux uses, but pointed out FreeBSD does not use=20 that format, and back then it was an open question which format to use=20 to boot FreeBSD/arm on Xen. Unfortunately, nine years later, the only=20 supported format is still the zImage format that Linux uses.

It looks like Julien's work back then was using an ELF binary to boo= t FreeBSD/arm on Xen instead of the supported zImage format that Linux=20 uses and the modern Xen toolstack exits with an error when trying to=20 boot the FreeBSD ELF formatted binary that Julien's patch creates. So= =20 the best solution would be to try to port the rules to build a FreeBSD=20 kernel in the zImage format instead of the ELF format. I have been=20 studying the Makefiles in Linux to see how Linux builds the Linux arm=20 kernel in the zImage format, but it is not trivial to understand

<= /div>

Look at kernel.bin = in FreeBSD's kernel. It's enabled -DWITH_KERNEL_BIN. It should be e= asy to adapt the target to build that. I've done similar things with u-= boot formats in the past, but that was 4 employers and 20 years ago now.

This path is not well trod. I do know that arm64= virtualization with bhyve is hitting the tree. I'm not sure how easy/h= ard this will be to modernize. I'm interested to see how your explorati= ons go.

Warner


--
Mario.
--0000000000005ff95f060b017cde-- From nobody Sun Nov 26 03:41:11 2023 X-Original-To: freebsd-arm@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4SdDzB4VPdz52X62 for ; Sun, 26 Nov 2023 03:41:26 +0000 (UTC) (envelope-from bakul@iitbombay.org) Received: from mail-ot1-x330.google.com (mail-ot1-x330.google.com [IPv6:2607:f8b0:4864:20::330]) (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 4SdDz90GV3z4bjD for ; Sun, 26 Nov 2023 03:41:24 +0000 (UTC) (envelope-from bakul@iitbombay.org) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=iitbombay-org.20230601.gappssmtp.com header.s=20230601 header.b=y8ElDpzM; spf=pass (mx1.freebsd.org: domain of bakul@iitbombay.org designates 2607:f8b0:4864:20::330 as permitted sender) smtp.mailfrom=bakul@iitbombay.org; dmarc=none Received: by mail-ot1-x330.google.com with SMTP id 46e09a7af769-6d81faeefc4so103547a34.2 for ; Sat, 25 Nov 2023 19:41:24 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=iitbombay-org.20230601.gappssmtp.com; s=20230601; t=1700970083; x=1701574883; darn=freebsd.org; h=to:date:message-id:subject:mime-version:from:from:to:cc:subject :date:message-id:reply-to; bh=VyrGGePTTPOdkXuJGIg0tmrDKxqJs43mWRwc2Mb7geo=; b=y8ElDpzMLybGkJ/sGOayYpq+jiwG0CthA+LmiqL7/FsKd0ifPgdA/YC2SxsXH2/Irl IdO3nFyr3ih6Ce8/prAbOCBWGpui6xaJ31LwRXHZR0eGmkU28xnk6oenP+ArorC3L5MY EnDPCOQlov3iq3qiNgF/jW3ZOudnNEF4O08WSrqztrV5j6x8MCcfmR9eMgsXI5Uyq+B+ vHK162ub/LHrWIJqb+r+4fgihaiPuxG0E1On0JYtxnON191w1ovqijpvBeRG/U7Fe9S0 7mru83IocTDfh6NKNUmQqVOxW1GsDP6L+yGVXTs6h+Y5aspq8MIrl4VQWbXwZMhaLDBI GW9w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1700970083; x=1701574883; h=to:date:message-id:subject:mime-version:from:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=VyrGGePTTPOdkXuJGIg0tmrDKxqJs43mWRwc2Mb7geo=; b=m/6LJy0wuNiTtVm38VoRK7NqTGvpfBgKwL7SDueVGOIun87GnURTEUvaeKz0aYBJYo lxh1YSzTTd8jqWUBw8k7+gpoyXIo/9NJtEvEM36hSZAV6qWq2pS4SDXHMYGZaTN2fJsh a3wU95FulfxthZMA2Ss1yL7eItuugZ586TGTnaqnZW3KfA6zkVt2+7gsgI8gjJdO9HQy 3840npgZ3eZumvu3tAd5XA4Qak4HBmnuFl2elMO7p4GJB8Ew/MIddAl18hI0GX5mbPXu dgNWZz8VvYbSu8eSdHDfG5e0tmIaeLh1FYPEwf0vLKNShdV6hNRI6TnTB/4QgAYk9hLt +5mA== X-Gm-Message-State: AOJu0YyWkJRb3IJs6u1ny14mtLz56usof5nfUcYTkZsjTzuzKv5ZcdfA gDJ+GzWUoXyxuAdt5Vy1r59pKrA9nlCfYKxVPoc= X-Google-Smtp-Source: AGHT+IFH9e5jgLPehMySFZBz4PVaVhzyKQ6OFBDyfszK1sgTYeu1AglOoqhDIrjNpbVaiE4tV++KEw== X-Received: by 2002:a05:6830:18f:b0:6b8:9483:35ba with SMTP id q15-20020a056830018f00b006b8948335bamr9113964ota.24.1700970082859; Sat, 25 Nov 2023 19:41:22 -0800 (PST) Received: from smtpclient.apple (107-215-223-229.lightspeed.sntcca.sbcglobal.net. [107.215.223.229]) by smtp.gmail.com with ESMTPSA id jj14-20020a170903048e00b001c9d6923e7dsm5673961plb.222.2023.11.25.19.41.22 for (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Sat, 25 Nov 2023 19:41:22 -0800 (PST) From: Bakul Shah Content-Type: multipart/alternative; boundary="Apple-Mail=_BE49AF84-1DD8-4F35-AF29-6589DDEC5993" List-Id: Porting FreeBSD to ARM processors List-Archive: https://lists.freebsd.org/archives/freebsd-arm List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arm@freebsd.org Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.200.91.1.1\)) Subject: sbrk Message-Id: <2F758BA2-F7F5-4A2C-85CF-6969EE50309C@iitbombay.org> Date: Sat, 25 Nov 2023 19:41:11 -0800 To: freebsd-arm@freebsd.org X-Mailer: Apple Mail (2.3774.200.91.1.1) X-Spamd-Result: default: False [-3.00 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-0.998]; MV_CASE(0.50)[]; R_DKIM_ALLOW(-0.20)[iitbombay-org.20230601.gappssmtp.com:s=20230601]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::330:from]; MLMMJ_DEST(0.00)[freebsd-arm@freebsd.org]; RCVD_VIA_SMTP_AUTH(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; FROM_EQ_ENVFROM(0.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; RCVD_TLS_LAST(0.00)[]; DKIM_TRACE(0.00)[iitbombay-org.20230601.gappssmtp.com:+]; DMARC_NA(0.00)[iitbombay.org]; RCPT_COUNT_ONE(0.00)[1]; FREEFALL_USER(0.00)[bakul]; ARC_NA(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; FROM_HAS_DN(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-arm@freebsd.org]; TO_MATCH_ENVRCPT_ALL(0.00)[]; TO_DN_NONE(0.00)[]; MID_RHS_MATCH_FROM(0.00)[] X-Rspamd-Queue-Id: 4SdDz90GV3z4bjD X-Spamd-Bar: -- --Apple-Mail=_BE49AF84-1DD8-4F35-AF29-6589DDEC5993 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii Does sbrk not exist on FreeBSD-14 on arm64? Is this by design? $ cat sb.c #include #include int main(int c, char**v) { void *x = sbrk(102400); printf("%p\n", x); } $ cc sb.c ld: error: undefined symbol: sbrk >>> referenced by sb.c >>> /tmp/sb-e97caf.o:(main) cc: error: linker command failed with exit code 1 (use -v to see invocation) --Apple-Mail=_BE49AF84-1DD8-4F35-AF29-6589DDEC5993 Content-Transfer-Encoding: 7bit Content-Type: text/html; charset=us-ascii Does sbrk not exist on FreeBSD-14 on arm64? Is this by design?

$ cat sb.c
#include <unistd.h>
#include <stdio.h>
int main(int c, char**v) {
        void *x = sbrk(102400);
        printf("%p\n", x);
}
$ cc sb.c
ld: error: undefined symbol: sbrk
>>> referenced by sb.c
>>>               /tmp/sb-e97caf.o:(main)
cc: error: linker command failed with exit code 1 (use -v to see invocation)

--Apple-Mail=_BE49AF84-1DD8-4F35-AF29-6589DDEC5993-- From nobody Sun Nov 26 03:43:57 2023 X-Original-To: freebsd-arm@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4SdF2H3p3Tz52YVs for ; Sun, 26 Nov 2023 03:44:07 +0000 (UTC) (envelope-from fuz@fuz.su) Received: from fuz.su (fuz.su [IPv6:2001:41d0:8:e508::1]) (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 "fuz.su", Issuer "fuz.su" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4SdF2H1BYcz4cQh for ; Sun, 26 Nov 2023 03:44:07 +0000 (UTC) (envelope-from fuz@fuz.su) Authentication-Results: mx1.freebsd.org; none Received: from fuz.su (localhost [127.0.0.1]) by fuz.su (8.17.1/8.17.1) with ESMTPS id 3AQ3hwo0025006 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Sun, 26 Nov 2023 04:43:58 +0100 (CET) (envelope-from fuz@fuz.su) Received: (from fuz@localhost) by fuz.su (8.17.1/8.17.1/Submit) id 3AQ3hvqJ025005; Sun, 26 Nov 2023 04:43:57 +0100 (CET) (envelope-from fuz) Date: Sun, 26 Nov 2023 04:43:57 +0100 From: Robert Clausecker To: Bakul Shah Cc: freebsd-arm@freebsd.org Subject: Re: sbrk Message-ID: References: <2F758BA2-F7F5-4A2C-85CF-6969EE50309C@iitbombay.org> List-Id: Porting FreeBSD to ARM processors List-Archive: https://lists.freebsd.org/archives/freebsd-arm List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arm@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <2F758BA2-F7F5-4A2C-85CF-6969EE50309C@iitbombay.org> X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:16276, ipnet:2001:41d0::/32, country:FR] X-Rspamd-Queue-Id: 4SdF2H1BYcz4cQh Hi Bakul, The sbrk() call indeed does not exist on arm64. Use mmap() or malloc() instead. Yours, Robert Clausecker Am Sat, Nov 25, 2023 at 07:41:11PM -0800 schrieb Bakul Shah: > Does sbrk not exist on FreeBSD-14 on arm64? Is this by design? > > $ cat sb.c > #include > #include > int main(int c, char**v) { > void *x = sbrk(102400); > printf("%p\n", x); > } > $ cc sb.c > ld: error: undefined symbol: sbrk > >>> referenced by sb.c > >>> /tmp/sb-e97caf.o:(main) > cc: error: linker command failed with exit code 1 (use -v to see invocation) > -- () ascii ribbon campaign - for an 8-bit clean world /\ - against html email - against proprietary attachments From nobody Sun Nov 26 03:44:10 2023 X-Original-To: freebsd-arm@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4SdF2p1S2fz52YWX for ; Sun, 26 Nov 2023 03:44:34 +0000 (UTC) (envelope-from joseph@josephholsten.com) Received: from pb-smtp1.pobox.com (pb-smtp1.pobox.com [64.147.108.70]) (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 4SdF2n6wX3z4csH for ; Sun, 26 Nov 2023 03:44:33 +0000 (UTC) (envelope-from joseph@josephholsten.com) Authentication-Results: mx1.freebsd.org; none Received: from pb-smtp1.pobox.com (unknown [127.0.0.1]) by pb-smtp1.pobox.com (Postfix) with ESMTP id 398281C2CDD; Sat, 25 Nov 2023 22:44:33 -0500 (EST) (envelope-from joseph@josephholsten.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=pobox.com; h=date:from :to:message-id:in-reply-to:references:subject:mime-version :content-type; s=sasl; bh=akjeeBGBAYrm+lS6vcwTovasoLNBzIQ5jvGgfB MqZZU=; b=kZifR2I93CbF/Fpky3k1s/7sjJYSqNDYv8oeYyzq6HdeNigvU5p4WS EWE3PlYNs+VXzPobBus1q6pI7UyQHw+xhQsGu+59p8fsH/qM+1e2LPH6BqsxRzqp Uz7MeVUzsajEiZSCBdo/jBzrRRXYObRWznvTaPA1E4lXlA9sxZgj8= Received: from pb-smtp1.nyi.icgroup.com (unknown [127.0.0.1]) by pb-smtp1.pobox.com (Postfix) with ESMTP id 217F71C2CDC; Sat, 25 Nov 2023 22:44:33 -0500 (EST) (envelope-from joseph@josephholsten.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=josephholsten.com; h=date:from:to:message-id:in-reply-to:references:subject:mime-version:content-type; s=2016-12.pbsmtp; bh=akjeeBGBAYrm+lS6vcwTovasoLNBzIQ5jvGgfBMqZZU=; b=pTIEJfza0mFT4mVGgFlydGETnjUa/4Q5AHiWOja0ABxIKsHErhPcWLxHxA3wE2rnbaxsGLMQJBSuYfvyrY3rBXgcfx2wFMG4//ofksOMLhaVxHT0vXvfiPZnQB5wyjRk9EZYblhjd3pyZU/FnNfQHAIKSB9EGcgDzUBZiYQftJ0= Received: from [192.168.32.35] (unknown [50.46.14.165]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by pb-smtp1.pobox.com (Postfix) with ESMTPSA id 34C4D1C2CD9; Sat, 25 Nov 2023 22:44:31 -0500 (EST) (envelope-from joseph@josephholsten.com) Date: Sat, 25 Nov 2023 19:44:10 -0800 From: joseph@josephholsten.com To: freebsd-arm@freebsd.org, Bakul Shah Message-ID: <949f8f16-1219-4f4a-abf6-f9727c95681b@Spark> In-Reply-To: <2F758BA2-F7F5-4A2C-85CF-6969EE50309C@iitbombay.org> References: <2F758BA2-F7F5-4A2C-85CF-6969EE50309C@iitbombay.org> Subject: Re: sbrk X-Readdle-Message-ID: 949f8f16-1219-4f4a-abf6-f9727c95681b@Spark List-Id: Porting FreeBSD to ARM processors List-Archive: https://lists.freebsd.org/archives/freebsd-arm List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arm@freebsd.org MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="6562bf1d_3bd91d5a_282" X-Pobox-Relay-ID: 1B7FC1DC-8C0E-11EE-B197-78DCEB2EC81B-15777318!pb-smtp1.pobox.com X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:19151, ipnet:64.147.108.0/24, country:US] X-Rspamd-Queue-Id: 4SdF2n6wX3z4csH --6562bf1d_3bd91d5a_282 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Yes, it=E2=80=99s no longer included. It=E2=80=99s long been deprecated, = but that does make porting things like the original vi a bit challenging.= Is there a particular project you=E2=80=99re trying to use it for=3F -- Joseph Holsten On Nov 25, 2023 at 19:41 -0800, Bakul Shah , wrote= : > Does sbrk not exist on =46reeBSD-14 on arm64=3F Is this by design=3F > > =24=C2=A0cat sb.c > =23include > =23include > int main(int c, char**v) =7B > =C2=A0 =C2=A0 =C2=A0 =C2=A0 void *x =3D sbrk(102400); > =C2=A0 =C2=A0 =C2=A0 =C2=A0 printf(=22%p=5Cn=22, x); > =7D > =24 cc sb.c > ld: error: undefined symbol: sbrk > >>> referenced by sb.c > >>> =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 /tmp/sb-e97caf.o:(= main) > cc: error: linker command failed with exit code 1 (use -v to see invoca= tion) > --6562bf1d_3bd91d5a_282 Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline
Yes, it=E2=80=99s no longer included. It=E2=80=99s = long been deprecated, but that does make porting things like the original= vi a bit challenging.

Is there a particular project you=E2=80=99re trying to use it for=3F

--
Joseph Holsten
On Nov 25, 2023 at 19:41 -0800, Bak= ul Shah <bakul=40iitbombay.org>, wrote:
Does sbrk not exist on =46reeBSD-14 on arm64=3F Is this by desi= gn=3F

=24&=23160;cat sb.c
=23include <unistd.h>
=23include <stdio.h>
int main(int c, char**v) =7B
&=23160; &=23160; &=23160; &=23160; void *x =3D sbrk(102400);
&=23160; &=23160; &=23160; &=23160; printf(=22%p=5Cn=22, x);
=7D
=24 cc sb.c
ld: error: undefined symbol: sbrk
>>> referenced by sb.c
>>> &=23160; &=23160; &=23160; &=23160; &=23160; &=23160; &= =23160; /tmp/sb-e97caf.o:(main)
cc: error: linker command failed with exit code 1 (use -v to see inv= ocation)

--6562bf1d_3bd91d5a_282-- From nobody Sun Nov 26 03:47:45 2023 X-Original-To: freebsd-arm@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4SdF6l1Ypsz52Zs8 for ; Sun, 26 Nov 2023 03:47:59 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-ed1-x532.google.com (mail-ed1-x532.google.com [IPv6:2a00:1450:4864:20::532]) (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 4SdF6k749Kz4f76 for ; Sun, 26 Nov 2023 03:47:58 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-ed1-x532.google.com with SMTP id 4fb4d7f45d1cf-5488bf9e193so4263769a12.2 for ; Sat, 25 Nov 2023 19:47:58 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20230601.gappssmtp.com; s=20230601; t=1700970477; x=1701575277; darn=freebsd.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=MaJJkmB7jVfHQje04aqOyvqqJQxZKVNgzf8vrBcWHrc=; b=JahwTkr7bt8Ulw10lCuHrOGZbxirnYDdmmWzmFV+5bw5tJPGaBm13vwfNkxuuAiUkK tH9P+3VxEBwNlJewvyFZ7wf8JkI/MPhpSyR1w/S7AX4XyCg/2k7nAvz1yyPS9n2RSsgU hug1sAemEpey++yDRuhGzA+4LXeVexDB6M90HD5B4c5YieF9wLRM9FgiRm0/hICCLx2q 4R8+BY4djU2nrz2Pwondh6agP7Rzy6wOmEcqGsKRjMzBRlhcXAcBz7ol2MGR3623/uGq jdRdo8qgO4RyqF8xiVqxvs0+lMFEPiMOmgAQdxCF+FPFWu74L7xrXjVjsTkPeLThgIrj meOA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1700970477; x=1701575277; 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=MaJJkmB7jVfHQje04aqOyvqqJQxZKVNgzf8vrBcWHrc=; b=YmG82h0FMxDAN/pWjk2XmySVwyQWxjZ9v0wrKFCIvvVN5XfuLAG8gyJMCKXcna2kBx DFY3/dVh6grHgQmqs2AJ3NyDIznlcWN9NO2/S59nLmPj0ldC5adbiQVjk5phk/KAFi0y xj79Ex2+PhDNuTU/NItEVFsKPVoCl9WmzpHCdYI5QfyOjBBij+Nm6Xe/mS+gQX72nf0Q U3kUuBTB87vTa1y2eXzCbPFeWOKnQw3/Oxh876ZKHjuhej6U8QjTWdOxKPTuhkx2gr+N OsEpY+R0wMWd80rKpTUCmQw8gnuVUv2pXWONV1cHFrXD/XYRpc32yf5QczeQ4xgdK2IA T14w== X-Gm-Message-State: AOJu0YzkHfK5KY9rEIDcgwHS9yn6saOEKyrE1dBo1YI+fGNvmlZ3UGdc YLsUO/4m3lQEDKXLUoTHFVAYKLsI3KOhVihh5KDXDQ== X-Google-Smtp-Source: AGHT+IFMQQXUTJ3qwEFZltzqufo3g6v/X4eLm5D09B0m3PDOHdYd6Fx05y4OC/vC0R+Mzl5b62VFRKRXeH9oCMmH8Yg= X-Received: by 2002:aa7:d34e:0:b0:540:2c48:7913 with SMTP id m14-20020aa7d34e000000b005402c487913mr5608541edr.38.1700970477416; Sat, 25 Nov 2023 19:47:57 -0800 (PST) List-Id: Porting FreeBSD to ARM processors List-Archive: https://lists.freebsd.org/archives/freebsd-arm List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arm@freebsd.org MIME-Version: 1.0 References: <2F758BA2-F7F5-4A2C-85CF-6969EE50309C@iitbombay.org> <949f8f16-1219-4f4a-abf6-f9727c95681b@Spark> In-Reply-To: <949f8f16-1219-4f4a-abf6-f9727c95681b@Spark> From: Warner Losh Date: Sat, 25 Nov 2023 20:47:45 -0700 Message-ID: Subject: Re: sbrk To: Joseph Holsten Cc: "freebsd-arm@freebsd.org" , Bakul Shah Content-Type: multipart/alternative; boundary="000000000000148268060b060d72" X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated 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-Queue-Id: 4SdF6k749Kz4f76 --000000000000148268060b060d72 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Sat, Nov 25, 2023, 8:44 PM wrote: > Yes, it=E2=80=99s no longer included. It=E2=80=99s long been deprecated, = but that does > make porting things like the original vi a bit challenging. > > Is there a particular project you=E2=80=99re trying to use it for? > It was never included in FreeBSD/arm64 due to the fact that the address space is complicated now and there no longer is an area beyond bss that you can expand into... let alone contract... Emacs was not happy with it... Warner --=20 > Joseph Holsten > On Nov 25, 2023 at 19:41 -0800, Bakul Shah , wrote: > > Does sbrk not exist on FreeBSD-14 on arm64? Is this by design? > > $ cat sb.c > #include > #include > int main(int c, char**v) { > void *x =3D sbrk(102400); > printf("%p\n", x); > } > $ cc sb.c > ld: error: undefined symbol: sbrk > >>> referenced by sb.c > >>> /tmp/sb-e97caf.o:(main) > cc: error: linker command failed with exit code 1 (use -v to see > invocation) > > --000000000000148268060b060d72 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


On Sat, Nov 25, 2023, 8:44 PM <joseph@josephholsten.com> wrote:
<= blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px= #ccc solid;padding-left:1ex">
Yes, it=E2=80=99s no longer included. It=E2=80=99s long b= een deprecated, but that does make porting things like the original vi a bi= t challenging.

Is there a particular project you=E2=80=99re trying to use it for?

It was never included in FreeBSD/arm64 due to the fact that the addres= s space is complicated now and there no longer is an area beyond bss that y= ou can expand into... let alone contract...

Emacs was not happy with it...
<= br>
Warner

--
Joseph Holsten
On Nov 25, 2023 at 19:41 -0800, Bakul Sha= h <bakul@iitbombay.org>, wrote:
Does sbrk n= ot exist on FreeBSD-14 on arm64? Is this by design?

$=C2=A0cat sb.c
#include <unistd.h>
#include <stdio.h>
int main(int c, char**v) {
=C2=A0 =C2=A0 =C2=A0 =C2=A0 void *x =3D sbrk(102400);
=C2=A0 =C2=A0 =C2=A0 =C2=A0 printf("%p\n", x);
}
$ cc sb.c
ld: error: undefined symbol: sbrk
>>> referenced by sb.c
>>> =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 /tmp/sb-= e97caf.o:(main)
cc: error: linker command failed with exit code 1 (use -v to see invoc= ation)

--000000000000148268060b060d72-- From nobody Sun Nov 26 03:58:07 2023 X-Original-To: freebsd-arm@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4SdFLh5xrbz52frb for ; Sun, 26 Nov 2023 03:58:20 +0000 (UTC) (envelope-from bakul@iitbombay.org) Received: from mail-pj1-x102e.google.com (mail-pj1-x102e.google.com [IPv6:2607:f8b0:4864:20::102e]) (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 4SdFLh3Zt2z3CN4 for ; Sun, 26 Nov 2023 03:58:20 +0000 (UTC) (envelope-from bakul@iitbombay.org) Authentication-Results: mx1.freebsd.org; none Received: by mail-pj1-x102e.google.com with SMTP id 98e67ed59e1d1-280260db156so2730058a91.2 for ; Sat, 25 Nov 2023 19:58:20 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=iitbombay-org.20230601.gappssmtp.com; s=20230601; t=1700971099; x=1701575899; darn=freebsd.org; h=references:to:cc:in-reply-to:date:subject:mime-version:message-id :from:from:to:cc:subject:date:message-id:reply-to; bh=T8HaCWnMYoKlf3rz2XbHPPdl4NVLdZBzfiynsnEpEDc=; b=IENslCeIrj8fValZf/f8jOk9WZyXGlaaZvrqdxiXOOnOjgVgfb7UJfpCHXrLR6Pha2 AMw/KqZqDDDghFXuG5/BO12RYkQhIiVBumkW5+yMVGgkjEp75xUsZpRFhd/g84Nz0Lyq b70ETgfMOiipvevmQRqU40Yw4RyFI7HUVEgTbcB7WAlTrrsiIS1yobwK5XNGSix2kvxi 9dvVe5Q4pXKxt/Foq9mW++IoX8h0sWqQ5+E+KjzYjagUzj7YBCbR8eXxXw57s9N84csY 5bED+TjqFCxhIQaKAT/Ryw5JiwpcfA5b4b8Bfzv09xBAwx/PZW/X0LL7oNa9sFpzxOvb X75A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1700971099; x=1701575899; h=references:to:cc:in-reply-to:date:subject:mime-version:message-id :from:x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=T8HaCWnMYoKlf3rz2XbHPPdl4NVLdZBzfiynsnEpEDc=; b=iOioAGq8JPMJb+Ifzj8nGtbbBSpqcronb8CJcRW3rzA7k3bJs8MmwZBB9Y5tbTVqsA x/teG8ltt2R+p9sgd1JbiGF6H0wwjquzSPpkTHD7drFdjq79nRfDk4g5zQsQC6ApJ3Es 3Xcac43ZrdX4cv6ExX0rPUugaDnCmpnifLbIVHr2+DYrsqH7Z/l+wWRrdV05O5XrH0qZ Yq6qU97JuoOuQCOKRpHT8eOhEcqYmoJba/p6VuU7L80NZbAQ0Pvhq49xZVcTncF0Pso5 WhBDp1pZdWKWPj6p5YkTEP8r/tMpG680jW5izzZkbofsEIxVzidiNAT0Axz74s1aChDD GyyA== X-Gm-Message-State: AOJu0YzzQ6eCVcemKe6BCwpdH7yfmjHxr6mS1wDmtdgSTuKBtsb3Dmvo CBGEZB94g8kFGqTXcjyXjlQd3w== X-Google-Smtp-Source: AGHT+IH2tS7JwUjSXkdqsx2wbWz7qO59isuTgfmVk3MbjZPegI2Gkro/tmEH6kW8xBBe2uXc2wE7YQ== X-Received: by 2002:a17:90b:4b0f:b0:285:3444:94d2 with SMTP id lx15-20020a17090b4b0f00b00285344494d2mr9274050pjb.9.1700971098923; Sat, 25 Nov 2023 19:58:18 -0800 (PST) Received: from smtpclient.apple (107-215-223-229.lightspeed.sntcca.sbcglobal.net. [107.215.223.229]) by smtp.gmail.com with ESMTPSA id ca8-20020a17090af30800b002858ac5e401sm3359416pjb.45.2023.11.25.19.58.18 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Sat, 25 Nov 2023 19:58:18 -0800 (PST) From: Bakul Shah Message-Id: <5668E8DE-B3B3-408D-978E-C2358A614803@iitbombay.org> Content-Type: multipart/alternative; boundary="Apple-Mail=_C2A9D6C6-1581-46BD-BA39-083AF3921076" List-Id: Porting FreeBSD to ARM processors List-Archive: https://lists.freebsd.org/archives/freebsd-arm List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arm@freebsd.org Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.200.91.1.1\)) Subject: Re: sbrk Date: Sat, 25 Nov 2023 19:58:07 -0800 In-Reply-To: Cc: Joseph Holsten , "freebsd-arm@freebsd.org" To: Warner Losh References: <2F758BA2-F7F5-4A2C-85CF-6969EE50309C@iitbombay.org> <949f8f16-1219-4f4a-abf6-f9727c95681b@Spark> X-Mailer: Apple Mail (2.3774.200.91.1.1) X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US] X-Rspamd-Queue-Id: 4SdFLh3Zt2z3CN4 --Apple-Mail=_C2A9D6C6-1581-46BD-BA39-083AF3921076 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 On Nov 25, 2023, at 7:47=E2=80=AFPM, Warner Losh wrote: >=20 > On Sat, Nov 25, 2023, 8:44 PM > wrote: >> Yes, it=E2=80=99s no longer included. It=E2=80=99s long been = deprecated, but that does make porting things like the original vi a bit = challenging. >>=20 >> Is there a particular project you=E2=80=99re trying to use it for? >=20 >=20 > It was never included in FreeBSD/arm64 due to the fact that the = address space is complicated now and there no longer is an area beyond = bss that you can expand into... let alone contract... >=20 > Emacs was not happy with it... Thanks. Note that linux does provide it (may be not perfect but I = thought FreeBSD cared more about compatibility....).=20 This came up in trying to compile the v language https://github.com/vlang/v It uses a libgc which seems to be derived from some ancestor of BDW GC = and there are so many defines my eyes glaze over. >=20 > Warner >=20 >> -- >> Joseph Holsten >> On Nov 25, 2023 at 19:41 -0800, Bakul Shah >, wrote: >>> Does sbrk not exist on FreeBSD-14 on arm64? Is this by design? >>>=20 >>> $ cat sb.c >>> #include >>> #include >>> int main(int c, char**v) { >>> void *x =3D sbrk(102400); >>> printf("%p\n", x); >>> } >>> $ cc sb.c >>> ld: error: undefined symbol: sbrk >>> >>> referenced by sb.c >>> >>> /tmp/sb-e97caf.o:(main) >>> cc: error: linker command failed with exit code 1 (use -v to see = invocation) >>>=20 --Apple-Mail=_C2A9D6C6-1581-46BD-BA39-083AF3921076 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 On Nov 25, = 2023, at 7:47=E2=80=AFPM, Warner Losh <imp@bsdimp.com> = wrote:

On Sat, Nov 25, 2023, 8:44 PM <joseph@josephholsten.com> = wrote:
Yes, it=E2=80=99s no longer included. It=E2=80=99s = long been deprecated, but that does make porting things like the = original vi a bit challenging.

Is there a particular project you=E2=80=99re trying to use it = for?

It was never included in = FreeBSD/arm64 due to the fact that the address space is complicated now = and there no longer is an area beyond bss that you can expand into... = let alone contract...

Emacs was not happy with = it...

Thanks. Note that = linux does provide it (may be not perfect but I thought FreeBSD cared = more about compatibility....). 

This came = up in trying to compile the v language

It uses a libgc which seems to be derived from some = ancestor of BDW GC and there are so many defines my eyes glaze = over.


Warner

--
Joseph Holsten
On Nov 25, 2023 at 19:41 -0800, Bakul = Shah <bakul@iitbombay.org>, wrote:
Does sbrk not exist on FreeBSD-14 = on arm64? Is this by design?

$ cat sb.c
#include <unistd.h>
#include <stdio.h>
int main(int c, char**v) {
        void *x =3D sbrk(102400);
        printf("%p\n", x);
}
$ cc sb.c
ld: error: undefined symbol: sbrk
>>> referenced by sb.c
>>>               = /tmp/sb-e97caf.o:(main)
cc: error: linker command failed with exit code 1 (use -v to see = invocation)


= --Apple-Mail=_C2A9D6C6-1581-46BD-BA39-083AF3921076-- From nobody Sun Nov 26 04:56:03 2023 X-Original-To: freebsd-arm@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4SdGdV4ZkMz51tyf for ; Sun, 26 Nov 2023 04:56:14 +0000 (UTC) (envelope-from wlosh@bsdimp.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 4SdGdV2K79z3Xjt for ; Sun, 26 Nov 2023 04:56:14 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-ed1-x52d.google.com with SMTP id 4fb4d7f45d1cf-54917ef6c05so4230278a12.1 for ; Sat, 25 Nov 2023 20:56:14 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20230601.gappssmtp.com; s=20230601; t=1700974573; x=1701579373; darn=freebsd.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=/JO9AG3kQwSZuJ1QbiYYA2FBH/MZQiUD2Lhi6o7J8Mc=; b=SIdJ7NjIASXud5y8ecJyCSFrlbqQAn3CJD0SmODWVT+4ZQ0+leyfVmY7m0cNTeneVZ 23Z+EM4kne70J1SwFmu7AhKd7CyIi/WnUKNw7QpZGlGFEVMb7BGym1t4nobRStbUYT7d Q+kFdig4pVnYhjuVTV2GmxzpHidgtVARPJRxO27Z5TAvAAhpD7y4WjIOiP1UN+b4czSF nRfVWJQix0RflLg/LrYfE/bVmwqQW0lPyMlSeakUmJ5gsBUczqGfYQLMH7zaWlS/K3vf 38IIyYF7i3dDgRpcCWfWouVb4Fb5W6OxP6cK4G37suI5j2Jz34p252ltLVv9QPD3WfhD ucXg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1700974573; x=1701579373; 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=/JO9AG3kQwSZuJ1QbiYYA2FBH/MZQiUD2Lhi6o7J8Mc=; b=nujKe01KoqQXZKqgAPg5fGHq1wg3tcCXVd2pABUi7Sa/5p8XC8qZTAOZSM91iuGIrG hxYdq5Gobpg0rTgnFTvFeLWo1EQFMBYz0ekDwUEDEOAPTf/ncKL74rs5ekvzWB/Um7CM AfrEMy7YObn5JfXzDuTAdW3Hv1k7H2aOxZGZINcrbqimQgY2nGHzHIT0Hop8nkbtQmRm gfAVR2PTuIA4Eq9iy7BgJgA4FMnveXuyLPDbDaP8OAF+6oSrOg/pCrtx6I85BxMbQQbM zlwd9kCVawoJDhgpd65rzACfQy1DEH4zMdFn/MjdsuQFdXgKjKcq2nrDTGY9ESVZwFMk dIyQ== X-Gm-Message-State: AOJu0YyttZWg5KB15NPhHXzoIPMy2hUtSu3QApCr78SB3DcZAbKhoqZm 3GRrvd2RrJMQU5w3FnJvqaiB+D0BA7Mqq3cTdkiK/pnZ8Ieb+QBU X-Google-Smtp-Source: AGHT+IHm3XMmsBuHje3nRizmWV6AmovBJqmiS5agQA6z/F1cIvmDeqLAUw19kh6+VHU4mcBu6QXwskwXQfnr+1CD6+Q= X-Received: by 2002:a05:6402:2207:b0:54b:25e8:c009 with SMTP id cq7-20020a056402220700b0054b25e8c009mr2104639edb.0.1700974572928; Sat, 25 Nov 2023 20:56:12 -0800 (PST) List-Id: Porting FreeBSD to ARM processors List-Archive: https://lists.freebsd.org/archives/freebsd-arm List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arm@freebsd.org MIME-Version: 1.0 References: <2F758BA2-F7F5-4A2C-85CF-6969EE50309C@iitbombay.org> <949f8f16-1219-4f4a-abf6-f9727c95681b@Spark> <5668E8DE-B3B3-408D-978E-C2358A614803@iitbombay.org> In-Reply-To: <5668E8DE-B3B3-408D-978E-C2358A614803@iitbombay.org> From: Warner Losh Date: Sat, 25 Nov 2023 21:56:03 -0700 Message-ID: Subject: Re: sbrk To: Bakul Shah Cc: Joseph Holsten , "freebsd-arm@freebsd.org" Content-Type: multipart/alternative; boundary="0000000000003118ac060b070112" X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated 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-Queue-Id: 4SdGdV2K79z3Xjt --0000000000003118ac060b070112 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Sat, Nov 25, 2023 at 8:58=E2=80=AFPM Bakul Shah wr= ote: > On Nov 25, 2023, at 7:47=E2=80=AFPM, Warner Losh wrote: > > > On Sat, Nov 25, 2023, 8:44 PM wrote: > >> Yes, it=E2=80=99s no longer included. It=E2=80=99s long been deprecated,= but that does >> make porting things like the original vi a bit challenging. >> >> Is there a particular project you=E2=80=99re trying to use it for? >> > > It was never included in FreeBSD/arm64 due to the fact that the address > space is complicated now and there no longer is an area beyond bss that y= ou > can expand into... let alone contract... > > Emacs was not happy with it... > > > Thanks. Note that linux does provide it (may be not perfect but I thought > FreeBSD cared more about compatibility....). > > This came up in trying to compile the v language > https://github.com/vlang/v > > It uses a libgc which seems to be derived from some ancestor of BDW GC an= d > there are so many defines my eyes glaze over. > I see that it also uses tcc, which I coincidentally was looking at in the cdefs modernization efforts I've been doing. You'll need at least one patch to cdefs to get even the basics to compile. And three tests fail (one doesn't matter, one is constructors and dtors and a third fails to detect out of bounds access). I think only the ctor/dtor one is going to make things hard for you. I've not looked into any of the test failures, just a short-coming in cdefs.h since tcc doesn't support .symver yet. sbrk can be faked with mmap of a large area up front with MAP_GUARD that's then grown or shrunk as new sbrk calls happen and remapped with MAP_FIXED. The only draw-back is you need reserve enough address space for all the program's memory needs (like GB of space maybe). The MAP_GUARD mappings are relatively cheap until it's actually used. Heck, you can even map SIGSEGV to check to see if you've "overflowed" the area to make it bigger (I hate that I know this trick, thank you Bourne shell). Looks fun to play with. Maybe I'd help (but I already have too many fun and even more un-fun projects). Warner > Warner > > -- >> Joseph Holsten >> On Nov 25, 2023 at 19:41 -0800, Bakul Shah , wrote: >> >> Does sbrk not exist on FreeBSD-14 on arm64? Is this by design? >> >> $ cat sb.c >> #include >> #include >> int main(int c, char**v) { >> void *x =3D sbrk(102400); >> printf("%p\n", x); >> } >> $ cc sb.c >> ld: error: undefined symbol: sbrk >> >>> referenced by sb.c >> >>> /tmp/sb-e97caf.o:(main) >> cc: error: linker command failed with exit code 1 (use -v to see >> invocation) >> >> > --0000000000003118ac060b070112 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


=
On Sat, Nov 25, 2023 at 8:58=E2=80=AF= PM Bakul Shah <bakul@iitbombay.or= g> wrote:
On Nov 25, 2023, at 7:47=E2=80=AFPM, Warner Losh <imp@bsdimp.com> wrote:
<= blockquote type=3D"cite">

On Sat, Nov 25, 2023, 8:44 P= M <joseph= @josephholsten.com> wrote:
Yes, it=E2=80=99s no longer included. It=E2=80=99s long b= een deprecated, but that does make porting things like the original vi a bi= t challenging.

Is there a particular project you=E2=80=99re trying to use it for?

It was never included in FreeBSD/arm64 due to the fact that the addres= s space is complicated now and there no longer is an area beyond bss that y= ou can expand into... let alone contract...

Emacs was not happy with it...

Thanks. Note that linux does provide it (may be not pe= rfect but I thought FreeBSD cared more about compatibility....).=C2=A0

This came up in trying to compile the v language
=

It uses a libgc which seems to b= e derived from some ancestor of BDW GC and there are so many defines my eye= s glaze over.

I see that it= also uses tcc, which I coincidentally was looking at in the cdefs moderniz= ation efforts I've been doing. You'll need at least one patch to cd= efs to get even the basics to compile. And three tests fail (one doesn'= t matter, one is constructors and dtors and a third fails to detect out of = bounds access). I think only the ctor/dtor one is going to make things hard= for you. I've not looked into any of the test failures, just a short-c= oming in cdefs.h since tcc doesn't support .symver yet.
<= br>
sbrk can be faked with mmap of a large area up front with MAP= _GUARD that's then grown or shrunk as new sbrk calls happen and remappe= d with MAP_FIXED. The only draw-back is you need reserve enough address spa= ce for all the program's memory needs (like GB of space maybe). The MAP= _GUARD mappings are relatively cheap until it's actually used. Heck, yo= u can even map SIGSEGV to check to see if you've "overflowed"= the area to make it bigger (I hate that I know this trick, thank you Bourn= e shell).

Looks fun to play with. Maybe I'= d help (but I already have too many fun and even more un-fun projects).
=

Warner
=C2=A0
=
Warner

--
Joseph Holsten
On Nov 25, 2023 at 19:41 -0800, Bakul Sha= h <bakul@iitbombay.org>, wrote:
Does sbrk not exist on FreeBSD-14 on arm64? Is this by de= sign?

$=C2=A0cat sb.c
#include <unistd.h>
#include <stdio.h>
int main(int c, char**v) {
=C2=A0 =C2=A0 =C2=A0 =C2=A0 void *x =3D sbrk(102400);
=C2=A0 =C2=A0 =C2=A0 =C2=A0 printf("%p\n", x);
}
$ cc sb.c
ld: error: undefined symbol: sbrk
>>> referenced by sb.c
>>> =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 /tmp/sb-= e97caf.o:(main)
cc: error: linker command failed with exit code 1 (use -v to see invoc= ation)


--0000000000003118ac060b070112-- From nobody Sun Nov 26 05:09:50 2023 X-Original-To: freebsd-arm@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4SdGxR1dJVz521pt for ; Sun, 26 Nov 2023 05:10:03 +0000 (UTC) (envelope-from bakul@iitbombay.org) Received: from mail-pj1-x102e.google.com (mail-pj1-x102e.google.com [IPv6:2607:f8b0:4864:20::102e]) (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 4SdGxR18tmz3bJ4 for ; Sun, 26 Nov 2023 05:10:03 +0000 (UTC) (envelope-from bakul@iitbombay.org) Authentication-Results: mx1.freebsd.org; none Received: by mail-pj1-x102e.google.com with SMTP id 98e67ed59e1d1-285be6134ecso2692a91.2 for ; Sat, 25 Nov 2023 21:10:03 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=iitbombay-org.20230601.gappssmtp.com; s=20230601; t=1700975402; x=1701580202; darn=freebsd.org; h=references:to:cc:in-reply-to:date:subject:mime-version:message-id :from:from:to:cc:subject:date:message-id:reply-to; bh=9xNWr9/pFW2Ed00t/1PACQeEqQd0Vhs83sTkisJwx/Q=; b=1LdFN7jzA5oycAK2O4AQY2r3Kk7qBr0o7SDrtGzh0wTLCAYZWmBZ4DB4ICvq+jzCLU ECrMvC/y5ZUou2nE6L5obMtBPSSiRZpiEMT7KT/tP4LJ+tpG6HYWUNLdmznNbxdvQ0fG 7Lk5A77g7vIyFlWznW4m1pQz5WDZwlvTFOC5/tVeMOKX2kTE6ehRtb95LK9DLtYtuVkN IYBkl4PasIR7AI8bhbTct+0rzNaS9iX55s/CFk44OUmBVzxMh78h0hTYhcK9+c4n07JG ka/SxOJpRJtIvkDYICYLrN7tHpny7fnQE18jyocnG3nB5mY1EX6N9ZPHsKMvtDL1k16r ifYg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1700975402; x=1701580202; h=references:to:cc:in-reply-to:date:subject:mime-version:message-id :from:x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=9xNWr9/pFW2Ed00t/1PACQeEqQd0Vhs83sTkisJwx/Q=; b=ILtkaSGn0neD2xv41mB6xH9MlWr/cieWXywre9acK/USdoyARKlsoxv/5sTekb7CO8 uRshr8j8S9x4aSnPmGBtDiq270S5R8w6oQBhQyae2rllKhPnwV5i9pG2eoTex0dUcFty VI4P0Xdi79avFcRU8v2Q67XPbai+k96ANCqJ0Y8eCyLFMZ96WdeCXCNo+zPIha+QGQOm b9qFKMzSM0RlBi6ffHUBzn+zR1Ro2A0AWzA9pcnKTNJgonV/evoXYrsLUjQTL4jdLWu3 iT9MC7gxPAY0BNwNXNIO4yvLWwjMNeRrOSBgWyfANBdLwJLy+ecLVA26WysVOueuV7kT TRmA== X-Gm-Message-State: AOJu0YzrHhPB1ZjlID4sxg+uDGoEzYLxYkqjz2X5UGwmY/u2BihbNbWE nT0tGTRuMpIZY1+M2+a880LuZw== X-Google-Smtp-Source: AGHT+IF+13hK06FUAIL2m5FKQ4fzrSeUOF5Pm9vtICYkGObIxIc8QiJd0Td+Zs/XJ9umbGRjIP09tg== X-Received: by 2002:a17:90b:3e86:b0:285:93f0:b2a7 with SMTP id rj6-20020a17090b3e8600b0028593f0b2a7mr4797897pjb.22.1700975401793; Sat, 25 Nov 2023 21:10:01 -0800 (PST) Received: from smtpclient.apple (107-215-223-229.lightspeed.sntcca.sbcglobal.net. [107.215.223.229]) by smtp.gmail.com with ESMTPSA id qj8-20020a17090b28c800b00285790ff232sm4267307pjb.32.2023.11.25.21.10.00 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Sat, 25 Nov 2023 21:10:01 -0800 (PST) From: Bakul Shah Message-Id: <4BA4DB2E-859A-427E-85AC-80F8F266C7BE@iitbombay.org> Content-Type: multipart/alternative; boundary="Apple-Mail=_0D4BCB9B-6BF2-43FE-879F-A20F0F8808D6" List-Id: Porting FreeBSD to ARM processors List-Archive: https://lists.freebsd.org/archives/freebsd-arm List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arm@freebsd.org Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.200.91.1.1\)) Subject: Re: sbrk Date: Sat, 25 Nov 2023 21:09:50 -0800 In-Reply-To: Cc: Joseph Holsten , "freebsd-arm@freebsd.org" To: Warner Losh References: <2F758BA2-F7F5-4A2C-85CF-6969EE50309C@iitbombay.org> <949f8f16-1219-4f4a-abf6-f9727c95681b@Spark> <5668E8DE-B3B3-408D-978E-C2358A614803@iitbombay.org> X-Mailer: Apple Mail (2.3774.200.91.1.1) X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US] X-Rspamd-Queue-Id: 4SdGxR18tmz3bJ4 --Apple-Mail=_0D4BCB9B-6BF2-43FE-879F-A20F0F8808D6 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 On Nov 25, 2023, at 8:56=E2=80=AFPM, Warner Losh wrote: >=20 > I see that it also uses tcc, which I coincidentally was looking at in = the cdefs modernization efforts I've been doing. You'll need at least = one patch to cdefs to get even the basics to compile. And three tests = fail (one doesn't matter, one is constructors and dtors and a third = fails to detect out of bounds access). I think only the ctor/dtor one is = going to make things hard for you. I've not looked into any of the test = failures, just a short-coming in cdefs.h since tcc doesn't support = .symver yet. using tcc fails with In file included from /tmp/v_1001/ncpu.2284299819361377756.tmp.c:430: /usr/include/stdlib.h:352: error: ARM asm not implemented. tcc also doesn't pass as many tests as clang on amd64 (unfortunately, as = it is compiles so much faster). Its native compiler is nowhere near = ready. It doesn't work well with the ported tcc on freebsd (I forget the = details now). But if you have any bug fixes I am interested! > sbrk can be faked with mmap of a large area up front with MAP_GUARD = that's then grown or shrunk as new sbrk calls happen and remapped with = MAP_FIXED. The only draw-back is you need reserve enough address space = for all the program's memory needs (like GB of space maybe). The = MAP_GUARD mappings are relatively cheap until it's actually used. Heck, = you can even map SIGSEGV to check to see if you've "overflowed" the area = to make it bigger (I hate that I know this trick, thank you Bourne = shell). I worked around with #define USE_MMAP 1. SIGSEGV to grow the stack -- that was a problem on V7 shell on 68000! = Luckily now that is only fit for old farts discussion on TUHS :-) > Looks fun to play with. Maybe I'd help (but I already have too many = fun and even more un-fun projects). It seems to be so far but I haven't written enough code to find its = gotchas.= --Apple-Mail=_0D4BCB9B-6BF2-43FE-879F-A20F0F8808D6 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 On Nov 25, = 2023, at 8:56=E2=80=AFPM, Warner Losh <imp@bsdimp.com> = wrote:

I see that it also uses tcc, which I = coincidentally was looking at in the cdefs modernization efforts I've = been doing. You'll need at least one patch to cdefs to get even the = basics to compile. And three tests fail (one doesn't matter, one is = constructors and dtors and a third fails to detect out of bounds = access). I think only the ctor/dtor one is going to make things hard for = you. I've not looked into any of the test failures, just a short-coming = in cdefs.h since tcc doesn't support .symver = yet.

using tcc fails = with

In file included = from = /tmp/v_1001/ncpu.2284299819361377756.tmp.c:430:
/usr/include/stdlib.h:352: error: ARM asm not = implemented.

tcc also doesn't pass = as many tests as clang on amd64 (unfortunately, as it is compiles so = much faster). Its native compiler is nowhere near = ready.

It doesn't work well with the ported tcc = on freebsd (I forget the details now). But if you have any bug fixes I = am interested!

sbrk can be = faked with mmap of a large area up front with MAP_GUARD that's then = grown or shrunk as new sbrk calls happen and remapped with MAP_FIXED. = The only draw-back is you need reserve enough address space for all the = program's memory needs (like GB of space maybe). The MAP_GUARD mappings = are relatively cheap until it's actually used. Heck, you can even map = SIGSEGV to check to see if you've "overflowed" the area to make it = bigger (I hate that I know this trick, thank you Bourne = shell).

I worked around with = #define USE_MMAP 1.

SIGSEGV to grow the stack = -- that was a problem on V7 shell on 68000! Luckily now that is only fit = for old farts discussion on TUHS :-)

Looks fun to play with. Maybe I'd help (but I already have too = many fun and even more un-fun = projects).

It seems to be so far = but I haven't written enough code to find its = gotchas.
= --Apple-Mail=_0D4BCB9B-6BF2-43FE-879F-A20F0F8808D6-- From nobody Sun Nov 26 05:19:42 2023 X-Original-To: freebsd-arm@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4SdH8p4RjQz5263j for ; Sun, 26 Nov 2023 05:19:54 +0000 (UTC) (envelope-from wlosh@bsdimp.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 4SdH8n4jYdz3dHS for ; Sun, 26 Nov 2023 05:19:53 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-ed1-x535.google.com with SMTP id 4fb4d7f45d1cf-54b0e553979so1695072a12.2 for ; Sat, 25 Nov 2023 21:19:53 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20230601.gappssmtp.com; s=20230601; t=1700975992; x=1701580792; darn=freebsd.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=c/Pff4w+yA9K0F4CIC8mBr37PovwRUw5AeoiT/LA1MQ=; b=D+x7KC4mt7XOAi0rOFgxcaqF+LV4JnCOPki4QToYp8uUQ8JKvUNBRHYMVbBxLamQKC pddF/u0Hp2jaqPTF6iERKJlQ4XTqaz2Vn/IZ37rLBcQIlJFxN8A+6zv+1hnC2ngFCZyd ACW/eyypSxpXilNTu7zDbOZrWzQtDFfHEHz3azyqvOVcJZHjQlvePTgefORR2cZEFf70 Idakn+d2B1ux4MdZycYIiujpTp5zpKBtQMpuN5d9RQ/HBQdm7yjG9xZsMJR+z+3+nvq0 YlDqms536YlXWOD2FiAm3qPkcMIW7R8/++//vSdFYu6peKKYRlKw3Oz/aoIL4J0Rgrtd BAQQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1700975992; x=1701580792; 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=c/Pff4w+yA9K0F4CIC8mBr37PovwRUw5AeoiT/LA1MQ=; b=KN86P64Ibdgjkb/nTHWQUEBhJcdPP7s8D8eOyXegBWgZpmEUhv5rKnWLh9eErJGu4o TZ+9U0tiKQikN/ECiavEFYN+oO7Fo1fOwuYfcYMPcUfzDCMlKjBusYer1T+ojsCMGLSr CLMd4u5/bS17B6wgkmTQNarkCAbNPqjfZHcw7iZBxCqrw0Rn/i3cr1pwO0hGj7BbwK6v 4Y0+0vepl2iGnA5jlmTQOOY/2owmhCqba/NC2FWUQgdcknH73/xKHqFsKkRrKXq+W3Fl D8eBi8gkUt/vU0exc4hJS9lcsqFumpkBBwU9M0S6oYWhGO7X+RDNfHvuxMAYMhGG37CE lsoQ== X-Gm-Message-State: AOJu0Yy7EKBexzfKZZ0i37EWPkSLMRC/pg/xBkbI1QNrRy2BX0vpKh+7 +oqLBa7O6C7izftf28MhxjPlPcloALXws3+eZwCEqLTb4+xUU0GG6Io= X-Google-Smtp-Source: AGHT+IFUEXH82OLw8DqoUqPiyQcQJrf5Bl+mMF8x50luf+TNIACjSI1V2XFltLTpqjFQXO2Y1mvesY6KwgcIR2k9Jts= X-Received: by 2002:a05:6402:35d4:b0:53d:b751:ece1 with SMTP id z20-20020a05640235d400b0053db751ece1mr5424032edc.41.1700975992165; Sat, 25 Nov 2023 21:19:52 -0800 (PST) List-Id: Porting FreeBSD to ARM processors List-Archive: https://lists.freebsd.org/archives/freebsd-arm List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arm@freebsd.org MIME-Version: 1.0 References: <2F758BA2-F7F5-4A2C-85CF-6969EE50309C@iitbombay.org> <949f8f16-1219-4f4a-abf6-f9727c95681b@Spark> <5668E8DE-B3B3-408D-978E-C2358A614803@iitbombay.org> <4BA4DB2E-859A-427E-85AC-80F8F266C7BE@iitbombay.org> In-Reply-To: <4BA4DB2E-859A-427E-85AC-80F8F266C7BE@iitbombay.org> From: Warner Losh Date: Sat, 25 Nov 2023 22:19:42 -0700 Message-ID: Subject: Re: sbrk To: Bakul Shah Cc: Joseph Holsten , "freebsd-arm@freebsd.org" Content-Type: multipart/alternative; boundary="000000000000c8e687060b07557d" X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated 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-Queue-Id: 4SdH8n4jYdz3dHS --000000000000c8e687060b07557d Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Sat, Nov 25, 2023 at 10:10=E2=80=AFPM Bakul Shah w= rote: > On Nov 25, 2023, at 8:56=E2=80=AFPM, Warner Losh wrote: > > > I see that it also uses tcc, which I coincidentally was looking at in the > cdefs modernization efforts I've been doing. You'll need at least one pat= ch > to cdefs to get even the basics to compile. And three tests fail (one > doesn't matter, one is constructors and dtors and a third fails to detect > out of bounds access). I think only the ctor/dtor one is going to make > things hard for you. I've not looked into any of the test failures, just = a > short-coming in cdefs.h since tcc doesn't support .symver yet. > > > using tcc fails with > > In file included from /tmp/v_1001/ncpu.2284299819361377756.tmp.c:430: > /usr/include/stdlib.h:352: error: ARM asm not implemented. > MY fix will fix that... Try this: % diff --git a/sys/sys/cdefs.h b/sys/sys/cdefs.h index 549a51a00893..3fd2ac4e2af4 100644 --- a/sys/sys/cdefs.h +++ b/sys/sys/cdefs.h @@ -532,11 +532,17 @@ __asm__(".section .gnu.warning." #sym); \ __asm__(".asciz \"" msg "\""); \ __asm__(".previous") +#ifndef __TINYC__ #define __sym_compat(sym,impl,verid) \ __asm__(".symver " #impl ", " #sym "@" #verid) #define __sym_default(sym,impl,verid) \ __asm__(".symver " #impl ", " #sym "@@@" #verid) #else +/* TinyC doesn't implement .symver */ +#define __sym_compat(sym,impl,verid) +#define __sym_default(sym,impl,verid) +#endif +#else #define __weak_reference(sym,alias) \ __asm__(".weak alias"); \ __asm__(".equ alias, sym") you can just copy the patches sys/cdefs.h to /usr/include/sys and rebuild tcc and see how it goes. > tcc also doesn't pass as many tests as clang on amd64 (unfortunately, as > it is compiles so much faster). Its native compiler is nowhere near ready= . > I think it fixed another 10 or 15, but there were so many I didn't count them. > It doesn't work well with the ported tcc on freebsd (I forget the details > now). But if you have any bug fixes I am interested! > Sure. included what I have so far above. > sbrk can be faked with mmap of a large area up front with MAP_GUARD that'= s > then grown or shrunk as new sbrk calls happen and remapped with MAP_FIXED= . > The only draw-back is you need reserve enough address space for all the > program's memory needs (like GB of space maybe). The MAP_GUARD mappings a= re > relatively cheap until it's actually used. Heck, you can even map SIGSEGV > to check to see if you've "overflowed" the area to make it bigger (I hate > that I know this trick, thank you Bourne shell). > > > I worked around with #define USE_MMAP 1. > > SIGSEGV to grow the stack -- that was a problem on V7 shell on 68000! > Luckily now that is only fit for old farts discussion on TUHS :-) > Yea... > Looks fun to play with. Maybe I'd help (but I already have too many fun > and even more un-fun projects). > > > It seems to be so far but I haven't written enough code to find its > gotchas. > I'd be interested in knowing... Warner --000000000000c8e687060b07557d Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


=
On Sat, Nov 25, 2023 at 10:10=E2=80= =AFPM Bakul Shah <bakul@iitbombay= .org> wrote:
On Nov 25, 2023, at 8:56=E2=80=AFPM, Warner Losh <imp@bsdimp.com> wrote:

I see that it also u= ses tcc, which I coincidentally was looking at in the cdefs modernization e= fforts I've been doing. You'll need at least one patch to cdefs to = get even the basics to compile. And three tests fail (one doesn't matte= r, one is constructors and dtors and a third fails to detect out of bounds = access). I think only the ctor/dtor one is going to make things hard for yo= u. I've not looked into any of the test failures, just a short-coming i= n cdefs.h since tcc doesn't support .symver yet.

using tcc fails with

In file included from /tmp/v_1001/ncpu.2284299819361377756.tm= p.c:430:
/usr/include/stdlib.h:352: e= rror: ARM asm not implemented.
MY fix will fix that... Try this:

% d= iff --git a/sys/sys/cdefs.h b/sys/sys/cdefs.h
index 549a51a00893..3fd2ac= 4e2af4 100644
--- a/sys/sys/cdefs.h
+++ b/sys/sys/cdefs.h
@@ -532,= 11 +532,17 @@
=C2=A0 =C2=A0 =C2=A0 =C2=A0 __asm__(".section .gnu.wa= rning." #sym); \
=C2=A0 =C2=A0 =C2=A0 =C2=A0 __asm__(".asciz \= "" msg "\""); =C2=A0\
=C2=A0 =C2=A0 =C2=A0 =C2= =A0 __asm__(".previous")
+#ifndef __TINYC__
=C2=A0#define = =C2=A0 =C2=A0 =C2=A0 =C2=A0__sym_compat(sym,impl,verid) =C2=A0 =C2=A0\
= =C2=A0 =C2=A0 =C2=A0 =C2=A0 __asm__(".symver " #impl ", &quo= t; #sym "@" #verid)
=C2=A0#define =C2=A0 =C2=A0 =C2=A0 =C2=A0_= _sym_default(sym,impl,verid) =C2=A0 \
=C2=A0 =C2=A0 =C2=A0 =C2=A0 __asm_= _(".symver " #impl ", " #sym "@@@" #verid)=C2=A0#else
+/* TinyC doesn't implement .symver */
+#define =C2= =A0 =C2=A0 =C2=A0__sym_compat(sym,impl,verid)
+#define =C2=A0 =C2=A0 =C2= =A0__sym_default(sym,impl,verid)
+#endif
+#else
=C2=A0#define =C2= =A0 =C2=A0 =C2=A0 =C2=A0__weak_reference(sym,alias) =C2=A0 =C2=A0 \
=C2= =A0 =C2=A0 =C2=A0 =C2=A0 __asm__(".weak alias"); =C2=A0 =C2=A0 = =C2=A0 =C2=A0 \
=C2=A0 =C2=A0 =C2=A0 =C2=A0 __asm__(".equ alias, sy= m")

you can just copy the patches sys/cdefs.h= to /usr/include/sys and rebuild tcc and see how it goes.
=C2= =A0
tcc al= so doesn't pass as many tests as clang on amd64 (unfortunately, as it i= s compiles so much faster). Its native compiler is nowhere near ready.

I think it fixed another 10 or 15, = but there were so many I didn't count them.
=C2=A0
<= blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-l= eft:1px solid rgb(204,204,204);padding-left:1ex">
It doesn't w= ork well with the ported tcc on freebsd (I forget the details now). But if = you have any bug fixes I am interested!
Sure. included what I have so far above.
=
sbrk can be faked with mmap of a large area up front with= MAP_GUARD that's then grown or shrunk as new sbrk calls happen and rem= apped with MAP_FIXED. The only draw-back is you need reserve enough address= space for all the program's memory needs (like GB of space maybe). The= MAP_GUARD mappings are relatively cheap until it's actually used. Heck= , you can even map SIGSEGV to check to see if you've "overflowed&q= uot; the area to make it bigger (I hate that I know this trick, thank you B= ourne shell).

I worked around wi= th #define USE_MMAP 1.

SIGSEGV to grow the stack -= - that was a problem on V7 shell on 68000! Luckily now that is only fit for= old farts discussion on TUHS :-)

Yea...
<= div>
Looks fun to play= with. Maybe I'd help (but I already have too many fun and even more un= -fun projects).

It seems to be so fa= r but I haven't written enough code to find its gotchas.

I'd be interested in knowing...

Warner
--000000000000c8e687060b07557d-- From nobody Sun Nov 26 05:52:18 2023 X-Original-To: freebsd-arm@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4SdHtN5RFrz52Mvq for ; Sun, 26 Nov 2023 05:52:28 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) (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 4SdHtN0zJ4z4H1Y for ; Sun, 26 Nov 2023 05:52:28 +0000 (UTC) (envelope-from kostikbel@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: from tom.home (kib@localhost [127.0.0.1] (may be forged)) by kib.kiev.ua (8.17.1/8.17.1) with ESMTP id 3AQ5qIZK047592; Sun, 26 Nov 2023 07:52:21 +0200 (EET) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua 3AQ5qIZK047592 Received: (from kostik@localhost) by tom.home (8.17.1/8.17.1/Submit) id 3AQ5qIOj047591; Sun, 26 Nov 2023 07:52:18 +0200 (EET) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Sun, 26 Nov 2023 07:52:18 +0200 From: Konstantin Belousov To: Warner Losh Cc: Joseph Holsten , "freebsd-arm@freebsd.org" , Bakul Shah Subject: Re: sbrk Message-ID: References: <2F758BA2-F7F5-4A2C-85CF-6969EE50309C@iitbombay.org> <949f8f16-1219-4f4a-abf6-f9727c95681b@Spark> List-Id: Porting FreeBSD to ARM processors List-Archive: https://lists.freebsd.org/archives/freebsd-arm List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arm@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FORGED_GMAIL_RCVD,FREEMAIL_FROM, NML_ADSP_CUSTOM_MED autolearn=no autolearn_force=no version=4.0.0 X-Spam-Checker-Version: SpamAssassin 4.0.0 (2022-12-14) on tom.home X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:6939, ipnet:2001:470::/32, country:US] X-Rspamd-Queue-Id: 4SdHtN0zJ4z4H1Y On Sat, Nov 25, 2023 at 08:47:45PM -0700, Warner Losh wrote: > On Sat, Nov 25, 2023, 8:44 PM wrote: > > > Yes, it’s no longer included. It’s long been deprecated, but that does > > make porting things like the original vi a bit challenging. > > > > Is there a particular project you’re trying to use it for? > > > > It was never included in FreeBSD/arm64 due to the fact that the address > space is complicated now and there no longer is an area beyond bss that you > can expand into... let alone contract... > > Emacs was not happy with it... I do not believe there are material differences in handling of user VA between amd64 and arm64 from the application point of view. Also, I believe that removal of sbrk(2) from arm64 was more an experiment to see what breaks, instead of failed attempt to implement it. Now I think that we should claim that the experiment failed and just allow sbrk on all Tier 1 arches. It is not worth the trouble. From nobody Sun Nov 26 19:22:37 2023 X-Original-To: freebsd-arm@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4SddsF2rdwz51yjw for ; Sun, 26 Nov 2023 19:22:41 +0000 (UTC) (envelope-from jcb2023az@gmail.com) Received: from mail-pf1-x42b.google.com (mail-pf1-x42b.google.com [IPv6:2607:f8b0:4864:20::42b]) (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 4SddsD51lMz4fyx for ; Sun, 26 Nov 2023 19:22:40 +0000 (UTC) (envelope-from jcb2023az@gmail.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20230601 header.b="U/Rf4MGW"; spf=pass (mx1.freebsd.org: domain of jcb2023az@gmail.com designates 2607:f8b0:4864:20::42b as permitted sender) smtp.mailfrom=jcb2023az@gmail.com; dmarc=pass (policy=none) header.from=gmail.com Received: by mail-pf1-x42b.google.com with SMTP id d2e1a72fcca58-6c4eb5fda3cso3450755b3a.2 for ; Sun, 26 Nov 2023 11:22:40 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1701026559; x=1701631359; darn=freebsd.org; h=mime-version:subject:message-id:to:from:date:from:to:cc:subject :date:message-id:reply-to; bh=1s4tSRTPyORnNOpJSX47X43FfFdyfA3j7x1gzz/bNV4=; b=U/Rf4MGWD+vrNg5W+4lViTH19fNaE5QB1dKnsqr/vCVM9dOHpzQTJs4BtSreJnn8k5 s/lm6iqG10OBG2fG6IUgfh2jDUSZTNMOVPMekUmDfuBILD/BtNoYjGDXffcfAExYMLLU mbHYs7i/jFf5DKPcNh/IMFb7tN5bGosjzoVOBvexlt7Rb4+XiSYp+UX6ckQZvoSaE9z1 5Td1nxoEJM3WtUZGxtFjz3R7tkzHkWs3crldC+TkvkdJGBAuDlnqwrL90sLq32O8+AeZ 77pBdPHqQxk2F4Ha3ifToKKcqEPo/nzcM0nI2jHT3OIsd7rMyMIYfRCwZQLIauoMFGdR sAdQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1701026559; x=1701631359; h=mime-version:subject:message-id:to:from:date:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=1s4tSRTPyORnNOpJSX47X43FfFdyfA3j7x1gzz/bNV4=; b=IvyIpsSsVogImRB+IF5e71aXEhSiLVvPnCxm10LZj1Ct828Lo2EjKJ6Lw256W1gEE/ WeUNoR7U7ki+ayo7LMOWPJbNrjVDKfhBYVwHXLpEhxrT4LQL3z/DGy4Geyk7nQqjBSf4 9/RE4Xe4Glvfm6yCVY3cEtAC5KVOmV+7LGS//UYX0rgXt9NpEZBHkp6/jEaIFN4DbtHW uMnwj+aCLvVGPOg0xiHrcI5UcLC3qSqL3OzIOvN1WQF9ptlG5pR7jpkqMjGRbZ1nOb89 /y9B2sKSb7KmXRo4akqzRstHf1o0PCqIiJR1MjCB1dOCJ3wYt8/175EeCg8+UHzI3CD0 mQEg== X-Gm-Message-State: AOJu0YzGP3v0YZewiDxUnuWcZ1g1Gh4u4jw243u9mHXQQfESfcyFAEdC 4o9j5yMgA3po0Sws8K2QgGQdtMvxnIE= X-Google-Smtp-Source: AGHT+IGcb8dGL0Siv9JvfaUBBBp21TAc0RiPens5A/hmI3iCC/t5kniBB8Sj82KeOXHNBZNM4Fca0Q== X-Received: by 2002:a05:6a20:da91:b0:187:7761:6155 with SMTP id iy17-20020a056a20da9100b0018777616155mr14499580pzb.55.1701026558678; Sun, 26 Nov 2023 11:22:38 -0800 (PST) Received: from ?IPv6:::1? ([2607:fb91:221:5aaa:ac39:87f1:4ecf:9dfe]) by smtp.gmail.com with ESMTPSA id m1-20020a63fd41000000b005891f3af36asm6483316pgj.87.2023.11.26.11.22.37 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sun, 26 Nov 2023 11:22:38 -0800 (PST) Date: Sun, 26 Nov 2023 11:22:37 -0800 (PST) From: Joe B To: freebsd-arm@freebsd.org Message-ID: <7a13c63d-a50b-429c-a481-0693e9faaf6b@gmail.com> Subject: Freebsd on M1 Macs List-Id: Porting FreeBSD to ARM processors List-Archive: https://lists.freebsd.org/archives/freebsd-arm List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arm@freebsd.org MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_19_209738715.1701026557414" X-Correlation-ID: <7a13c63d-a50b-429c-a481-0693e9faaf6b@gmail.com> X-Spamd-Result: default: False [-3.86 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-0.998]; NEURAL_HAM_MEDIUM(-0.87)[-0.866]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20230601]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; PREVIOUSLY_DELIVERED(0.00)[freebsd-arm@freebsd.org]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::42b:from]; ARC_NA(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; MLMMJ_DEST(0.00)[freebsd-arm@freebsd.org]; DKIM_TRACE(0.00)[gmail.com:+]; TO_DN_NONE(0.00)[]; FREEMAIL_FROM(0.00)[gmail.com]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; RCVD_TLS_LAST(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: 4SddsD51lMz4fyx X-Spamd-Bar: --- ------=_Part_19_209738715.1701026557414 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit I know this is a longshot but I'm going to ask I know MacOS is a BSD but we all know it's very sugarcoated and doesn't look like a BSD. Question will real freeBSD ever come to the m1 Mac's. I got a 16 inch mbp with good specs just taking up space right now Thanks ~ Joe B ------=_Part_19_209738715.1701026557414 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit
I know this is a longshot but I'm going to ask I know MacOS is a BSD but we all know it's very sugarcoated and doesn't look like a BSD.

Question will real freeBSD ever come to the m1 Mac's. I got a 16 inch mbp with good specs just taking up space right now

Thanks

~ Joe B
------=_Part_19_209738715.1701026557414-- From nobody Sun Nov 26 21:00:53 2023 X-Original-To: freebsd-arm@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4Sdh2Z2mGMz522g4 for ; Sun, 26 Nov 2023 21:00:54 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (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 "mxrelay.nyi.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Sdh2Z0CXKz4G5v for ; Sun, 26 Nov 2023 21:00:54 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1701032454; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding; bh=y2S4rWhiiJ8czPbUSPfVO1E4P4w/P2jaTw/EaSYJTTY=; b=J4ynB6HyYKwOIhUjx8JdHqxsIT5LLUjwEJxZSG/z6KOz7CSCWaeV32JSgTuaj3g1gWVPRV eGZ5z3NUGjSj/AfeLQ2tMvTtoyP/EAbd41EC+Khl0bOkflOItQhE3BBO8CXsVPyTMt5z9r JoOO/gGVWaKutYrbacCDcz7u2+bquGYeTtu+LhdynFMlaD/R+uBcfOapewZI2sohX4EEGS aVJS52nIu27LaJBSv0w1dJCqwgiwBMtMxuKXWHbO0lVNL0hOgcgQQmAbxz8XqMs2joi7aC YVBjIIy2j5u5YpYasIRW0NFJvOJJbPo6NYVam3aojhuFZpYtRAUf4FmC/LCqSA== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1701032454; a=rsa-sha256; cv=none; b=U9TNKXLcKtOz5gKhwNVEi4lwwuiZ4sYjQi/UGRMtZYHGjIlJGWzK9Qj7f1P4cGmjwTzJ1Q vkI3C7Y4TEgAYHRgfJrslN7BzZQvKH5glkjpRgU/4TXtPffg1/nLNbBNCuEKc6T+4WcSHa LWSp5XyL6Blo0nTtaCGgcCEePJR8v0/lKGk+YmJ1zZpKV7pN8lvDMHp0fjZlggBh/gU7F3 4Nqkghw6DocJsVfeN3GmkAI1m1BiGI/pGlH7mchbmQiJMy8iIob4dbwY+k05m6kUA+/zOt xVcnPrfX3Bu449KuS5pP1kAhhSuQ4xvc5Y71+2JHQnxYj4QiPILWFJltK5pWbQ== Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (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 mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 4Sdh2Y6Q9Vz19Ym for ; Sun, 26 Nov 2023 21:00:53 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 3AQL0ra0014205 for ; Sun, 26 Nov 2023 21:00:53 GMT (envelope-from bugzilla-noreply@FreeBSD.org) Received: (from bugzilla@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 3AQL0rAY014203 for freebsd-arm@FreeBSD.org; Sun, 26 Nov 2023 21:00:53 GMT (envelope-from bugzilla-noreply@FreeBSD.org) Message-Id: <202311262100.3AQL0rAY014203@kenobi.freebsd.org> X-Authentication-Warning: kenobi.freebsd.org: bugzilla set sender to bugzilla-noreply@FreeBSD.org using -f From: bugzilla-noreply@FreeBSD.org To: freebsd-arm@FreeBSD.org Subject: Problem reports for freebsd-arm@FreeBSD.org that need special attention Date: Sun, 26 Nov 2023 21:00:53 +0000 List-Id: Porting FreeBSD to ARM processors List-Archive: https://lists.freebsd.org/archives/freebsd-arm List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arm@freebsd.org MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="17010324535.A58E.10853" Content-Transfer-Encoding: 7bit --17010324535.A58E.10853 Date: Sun, 26 Nov 2023 21:00:53 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and obsolete releases. Status | Bug Id | Description ------------+-----------+--------------------------------------------------- Open | 238576 | Raspberry Pi 3B+ "shutdown -p" does not shut off Open | 257670 | mpr(4): SAS3008 PCI-Express Fusion-MPT SAS-3: Fat 2 problems total for which you should take action. --17010324535.A58E.10853 Date: Sun, 26 Nov 2023 21:00:53 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8" 
The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and obsolete releases.

Status      |    Bug Id | Description
------------+-----------+---------------------------------------------------
Open        |    238576 | Raspberry Pi 3B+ "shutdown -p" does not shut off 
Open        |    257670 | mpr(4): SAS3008 PCI-Express Fusion-MPT SAS-3: Fat

2 problems total for which you should take action.
--17010324535.A58E.10853-- From nobody Sun Nov 26 22:04:54 2023 X-Original-To: freebsd-arm@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4SdjSV0kF0z52hX8 for ; Sun, 26 Nov 2023 22:04:58 +0000 (UTC) (envelope-from bacon4000@gmail.com) Received: from mail-qk1-x732.google.com (mail-qk1-x732.google.com [IPv6:2607:f8b0:4864:20::732]) (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 4SdjSS5543z4chp for ; Sun, 26 Nov 2023 22:04:56 +0000 (UTC) (envelope-from bacon4000@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-qk1-x732.google.com with SMTP id af79cd13be357-77bc5d8490dso210901285a.2 for ; Sun, 26 Nov 2023 14:04:56 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1701036295; x=1701641095; darn=freebsd.org; h=content-transfer-encoding:in-reply-to:from:content-language :references:to:subject:user-agent:mime-version:date:message-id:from :to:cc:subject:date:message-id:reply-to; bh=elKeG3HT4GwpNxhYqPVMAcDs84bIxRfYZ38BVOfJjsI=; b=VO0Bh5eEBjNDsA0chDeNQt8UJB8MoooUhVJjAI+JOxtoF5JTgFiTTaV/HvoQ7xdnT2 8qYEnNUH2xy3eWNV016K6ug7ku8m47RW4VneKw33SHW+LkhY6w3YVUc7s0YB2f/24MSd rvV7DAtRybyVUMfuPq+RaZ31/5XtT6bRO8NrTlmMZJRsh8YlTerdvoD9FL/meeECOFYQ Zug/GzJVaE1eFE2dlyLVoKKHDZG3l90FHAcoXHbZQYtedOy9E2uLHm3a28p3MwhjaoPZ OIXyDthg9ezVlEs52W6rRo/Wth65kUTSOhPdXS+S725s44P556cQIRk7CUdkA7ldJkX2 8HEg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1701036295; x=1701641095; h=content-transfer-encoding:in-reply-to:from:content-language :references:to:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=elKeG3HT4GwpNxhYqPVMAcDs84bIxRfYZ38BVOfJjsI=; b=qZlqNNIOXZvNFSYW0Cjp0A/4kBBZ2SqV2RG6uHsrfeWGAK+1+KVKtYUmCaCP665rE1 XZ1YkerNgIqM1+P1mD7WQYfbkKzcxO0MY2R3pNo960tOxZwlHjynOI5HGKRC612LpHg9 R5rKuROut+0VlG4rGhmlheWkh1S07UIP8lb4KShXonXvgvcrC0T30auxmYrWT088CsB2 qk/kPC3OuJOCws8VgPoSQK209cmXEKcHXxjd5Btv4QkQ4WHq/pqA3ZsJaQhsSQOIUiCV juV7rqIM+eaJaNLSh6rLb6i7NKveavHWpIKOgussR2b2Gm2KihPRjzPlhEZSvXj2JsD9 ilOQ== X-Gm-Message-State: AOJu0YxfBB3zB0s25oytonoACDLHncreFaJodsG2/eVA7FmRLsZFG9Zh jkBJ5htRIGm80yn5xI4bMbqJsbQYSJs= X-Google-Smtp-Source: AGHT+IE/1I+0f0CtH1zaAPjC5qJ9izp5A3wTFwZ1hdHM/OqHT7L8osaKHk1BrnB9N97Kn2LVwRt/Jg== X-Received: by 2002:a05:620a:8d0f:b0:77d:a51c:dd52 with SMTP id rb15-20020a05620a8d0f00b0077da51cdd52mr1875166qkn.78.1701036295580; Sun, 26 Nov 2023 14:04:55 -0800 (PST) Received: from [192.168.0.3] (cpe-184-58-230-200.wi.res.rr.com. [184.58.230.200]) by smtp.gmail.com with ESMTPSA id az42-20020a05620a172a00b0077da4aaad9csm632461qkb.34.2023.11.26.14.04.55 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sun, 26 Nov 2023 14:04:55 -0800 (PST) Message-ID: <1536d845-9073-4f9b-96f6-fa9647536c00@gmail.com> Date: Sun, 26 Nov 2023 16:04:54 -0600 List-Id: Porting FreeBSD to ARM processors List-Archive: https://lists.freebsd.org/archives/freebsd-arm List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arm@freebsd.org MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: Freebsd on M1 Macs To: Joe B , freebsd-arm@freebsd.org References: <7a13c63d-a50b-429c-a481-0693e9faaf6b@gmail.com> Content-Language: en-US From: Jason Bacon In-Reply-To: <7a13c63d-a50b-429c-a481-0693e9faaf6b@gmail.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US] X-Rspamd-Queue-Id: 4SdjSS5543z4chp On 11/26/23 13:22, Joe B wrote: > > I know this is a longshot but I'm going to ask I know MacOS is a BSD but > we all know it's very sugarcoated and doesn't look like a BSD. > > Question will real freeBSD ever come to the m1 Mac's. I got a 16 inch > mbp with good specs just taking up space right now > > Thanks > > ~ Joe B I assume you've seen https://wiki.freebsd.org/AppleSilicon. Not sure how up-to-date it is. The wikis tend to lag behind reality in my experience. I have run FreeBSD under UTM (Qemu with a GUI). It worked OK, but I wasn't able to get better than 800x600 graphics, and it seemed to cause the host macOS to drop network connections. -- Life is a game. Play hard. Play fair. Have fun. From nobody Sun Nov 26 22:16:02 2023 X-Original-To: freebsd-arm@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4SdjjQ2pd4z52p3f for ; Sun, 26 Nov 2023 22:16:10 +0000 (UTC) (envelope-from jcb2023az@gmail.com) Received: from mail-pl1-x635.google.com (mail-pl1-x635.google.com [IPv6:2607:f8b0:4864:20::635]) (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 4SdjjP5wxZz4gR3 for ; Sun, 26 Nov 2023 22:16:09 +0000 (UTC) (envelope-from jcb2023az@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-pl1-x635.google.com with SMTP id d9443c01a7336-1cfc3f50504so3759895ad.3 for ; Sun, 26 Nov 2023 14:16:09 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1701036965; x=1701641765; darn=freebsd.org; h=mime-version:subject:references:in-reply-to:message-id:cc:to:from :date:from:to:cc:subject:date:message-id:reply-to; bh=4uuP+vV5Ao2Q6S5c6QUn9itutiVhhTJ+9BZ+S2apfT8=; b=DWvnwNn1/HCS7i+d/t6/r4vsgTC4utaj5b2wnoMVOyRpiv8jQswTlIy3hV9Nxhs18u BB0re4A/LMKou8Otn/i0+4OZP+IBFZgb4MPudOUOFSgZ2GFnxGmq3MziGQq1p4rU46sZ J3iLKG7E8+OuOXMjc8vHLwInu7ge4o9Bj9ItnnO5lZVTmJ8H9t8oBeOXJUtV7u+KCKc/ cPAMARCwVjjNicIShgt/zVaqaGgMNcQmu46ouwwnIVtuiJL4UquW0yMnoCWu+BIZHm6R Wc26WRN/mNjcQkq1IPhl5M4yCasS6MOFcsQFLC+VxzuGFmJ0Zk7RBQ2UT5W5Q54LyDt1 ON9A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1701036965; x=1701641765; h=mime-version:subject:references:in-reply-to:message-id:cc:to:from :date:x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=4uuP+vV5Ao2Q6S5c6QUn9itutiVhhTJ+9BZ+S2apfT8=; b=RItfTmisRYAkHxpMIBShDxa0MUm8q3dEhmVuOobvZbwHqcwdZsNQRRkDL2b+2phPwA k7wHq4O8+YpVXbXWEtE0gWLwd2RHz4QuqBjDgGEpYtwkCQk1ij58JmbSZjzvv7Gxn58Q 1L+JHxL9ZHy+TMyIC+depjjftzNzMEJrfQHeG6Cp3RSkXZ5kiFu8Iif3/ogpeCaBdvMm +7vEMzywUZOOCj/vbFIGKQQ/xwuTbUS51UGVRCAqi7EhLOfhYK7PcB1owKXji6LlGCDP EPZlhmkWEGs/FUaO4sRJaf8HdrnW4MQg7tJJNArcSU5/Ymit97CqGPY+9D58Wndt4lYS 2FNA== X-Gm-Message-State: AOJu0YyWtDLuAZtxmyC8TQRASoD8+OFEknRRGHyQIlRxaTEH8ycOTc5L qhOsVt0RZ1z41J2aFhPKJxRDl40MnR8= X-Google-Smtp-Source: AGHT+IGnpKbDnv4SqS0QlNVyTYpcl24dSjA56uH9t6bNuej13p0mlj37RF9eKJoRHl/ZF7ikdG/94w== X-Received: by 2002:a17:902:f814:b0:1cf:bf00:e8b1 with SMTP id ix20-20020a170902f81400b001cfbf00e8b1mr2719299plb.17.1701036965352; Sun, 26 Nov 2023 14:16:05 -0800 (PST) Received: from ?IPv6:::1? ([2607:fb90:8b19:5be2:ac39:c131:68e8:baa]) by smtp.gmail.com with ESMTPSA id e12-20020a170902744c00b001ce5b6e97a9sm6870353plt.54.2023.11.26.14.16.04 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sun, 26 Nov 2023 14:16:05 -0800 (PST) Date: Sun, 26 Nov 2023 14:16:02 -0800 (PST) From: Joe B To: Jason Bacon Cc: freebsd-arm@freebsd.org Message-ID: In-Reply-To: <1536d845-9073-4f9b-96f6-fa9647536c00@gmail.com> References: <7a13c63d-a50b-429c-a481-0693e9faaf6b@gmail.com> <1536d845-9073-4f9b-96f6-fa9647536c00@gmail.com> Subject: Re: Freebsd on M1 Macs List-Id: Porting FreeBSD to ARM processors List-Archive: https://lists.freebsd.org/archives/freebsd-arm List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arm@freebsd.org MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_22_172575478.1701036962832" X-Correlation-ID: X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US] X-Rspamd-Queue-Id: 4SdjjP5wxZz4gR3 ------=_Part_22_172575478.1701036962832 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Nov 26, 2023 2:04:56 PM Jason Bacon : > On 11/26/23 13:22, Joe B wrote: >> I know this is a longshot but I'm going to ask I know MacOS is a BSD but= we all know it's very sugarcoated and doesn't look like a BSD. >> Question will real freeBSD ever come to the m1 Mac's. I got a 16 inch mb= p with good specs just taking up space right now >> Thanks >> ~ Joe B > > I assume you've seen https://wiki.freebsd.org/AppleSilicon.=C2=A0 Not sur= e how up-to-date it is.=C2=A0 The wikis tend to lag behind reality in my ex= perience. > > I have run FreeBSD under UTM (Qemu with a GUI).=C2=A0 It worked OK, but I= wasn't able to get better than 800x600 graphics, and it seemed to cause th= e host macOS to drop network connections. > > -- > Life is a game.=C2=A0 Play hard.=C2=A0 Play fair.=C2=A0 Have fun. Got it. First time seeing that page. Looks like it's going to take a while. I won't= hold my breath. Thanks again ~ Joe B ------=_Part_22_172575478.1701036962832 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit Nov 26, 2023 2:04:56 PM Jason Bacon <bacon4000@gmail.com>:

> On 11/26/23 13:22, Joe B wrote:
>> I know this is a longshot but I'm going to ask I know MacOS is a BSD but we all know it's very sugarcoated and doesn't look like a BSD.
>> Question will real freeBSD ever come to the m1 Mac's. I got a 16 inch mbp with good specs just taking up space right now
>> Thanks
>> ~ Joe B
>
> I assume you've seen https://wiki.freebsd.org/AppleSilicon.  Not sure how up-to-date it is.  The wikis tend to lag behind reality in my experience.
>
> I have run FreeBSD under UTM (Qemu with a GUI).  It worked OK, but I wasn't able to get better than 800x600 graphics, and it seemed to cause the host macOS to drop network connections.
>
> --
> Life is a game.  Play hard.  Play fair.  Have fun.

Got it.

First time seeing that page. Looks like it's going to take a while. I won't hold my breath.

Thanks again

~ Joe B

------=_Part_22_172575478.1701036962832-- From nobody Sun Nov 26 23:11:21 2023 X-Original-To: freebsd-arm@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4SdkxB5VDyz52BNC for ; Sun, 26 Nov 2023 23:11:26 +0000 (UTC) (envelope-from sylvain.saboua@free.fr) Received: from smtp2-g21.free.fr (smtp2-g21.free.fr [IPv6:2a01:e0c:1:1599::11]) (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 4SdkxB3YDqz3CQZ for ; Sun, 26 Nov 2023 23:11:26 +0000 (UTC) (envelope-from sylvain.saboua@free.fr) Authentication-Results: mx1.freebsd.org; none Received: from webmail.free.fr (unknown [172.20.246.1]) (Authenticated sender: sylvain.saboua@free.fr) by smtp2-g21.free.fr (Postfix) with ESMTPA id DF96D2003C1; Mon, 27 Nov 2023 00:11:21 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=free.fr; s=smtp-20201208; t=1701040283; bh=9HPlU1TvZPvtkV7Vc2VgM0JXu3fcwBCOG08s/9HbHJw=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=uk0VDN4LQr0S2cGbmkaZMgmmJJjgZMLDvwOA5pYxUkM7BaoX4xviK6iyOFO9+d+Kf NbmrJoJTfYmFq1eNBA6EtuTSnb9rPF6IQol0Wkll+6RkgLovLkZmbRgVelh8NeXP4U AP6CZ0NjvQ1Bfof1240N2UGv3ZzsnM9XbK8phMBGB4UQNHcZZ1yjjjwUWDnwsL3TUD 3SExteAHjREDAj/TXemeBbV+8QhbKu+BxFJ9Dkj9i8kGpsZODaq5lLPFWJssWcjYhO Qm7UQwJlkZXSJ8LIRrZSddxEBkPVao9C6pd5Nh4JLX0uIJ2/EXpqwSlBY+Z3i1+n6D BhBlEc5NJnGhA== Received: from 2001:861:2c22:4580:5462:f32a:a5b2:1509 via 2001:861:2c22:4580:5462:f32a:a5b2:1509 by webmail.free.fr with HTTP (HTTP/1.0 POST); Mon, 27 Nov 2023 00:11:21 +0100 List-Id: Porting FreeBSD to ARM processors List-Archive: https://lists.freebsd.org/archives/freebsd-arm List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arm@freebsd.org MIME-Version: 1.0 Date: Mon, 27 Nov 2023 00:11:21 +0100 From: Sylvain Saboua To: Joe B Cc: freebsd-arm@freebsd.org Subject: Re: Freebsd on M1 Macs In-Reply-To: <7a13c63d-a50b-429c-a481-0693e9faaf6b@gmail.com> References: <7a13c63d-a50b-429c-a481-0693e9faaf6b@gmail.com> User-Agent: Webmail Free/1.6.5 Message-ID: X-Sender: sylvain.saboua@free.fr Disposition-Notification-To: Sylvain Saboua Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:12322, ipnet:2a01:e00::/26, country:FR] X-Rspamd-Queue-Id: 4SdkxB3YDqz3CQZ Per chance, had you stumbled yet on the helloSystem effort/proposal ? https://hellosystem.github.io/ « It is intended as a system for “mere mortals”, welcoming to switchers from the Mac. FreeBSD is used as the core operating system. » Regards Le 2023-11-26 20:22, Joe B a écrit : > I know this is a longshot but I'm going to ask I know MacOS is a BSD > but we all know it's very sugarcoated and doesn't look like a BSD. > > Question will real freeBSD ever come to the m1 Mac's. I got a 16 inch > mbp with good specs just taking up space right now > > Thanks > > ~ Joe B -- Sylvain Saboua linktr.ee/Sylvain From nobody Sun Nov 26 23:23:00 2023 X-Original-To: freebsd-arm@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4SdlBc0s2Wz52JSl for ; Sun, 26 Nov 2023 23:23:04 +0000 (UTC) (envelope-from jcb2023az@gmail.com) Received: from mail-pg1-x52e.google.com (mail-pg1-x52e.google.com [IPv6:2607:f8b0:4864:20::52e]) (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 4SdlBb2rH1z3GkL for ; Sun, 26 Nov 2023 23:23:03 +0000 (UTC) (envelope-from jcb2023az@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-pg1-x52e.google.com with SMTP id 41be03b00d2f7-5aa481d53e5so2421666a12.1 for ; Sun, 26 Nov 2023 15:23:03 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1701040982; x=1701645782; darn=freebsd.org; h=content-transfer-encoding:mime-version:subject:references :in-reply-to:message-id:cc:to:from:date:from:to:cc:subject:date :message-id:reply-to; bh=UHZHjutoH0d60QC8aQB2bmwmZO17B7xaWF9wB/ruq1I=; b=aszA8hN9lkYlbWPw/b64cnDRHUQsTxVAjL8yUFZ6CtpEclAIdv4Hny6GNqBUR7OSZN drZ6SNWkJaBd7tUetZstPwi2w38YliUXBINy580kjVK4i8pQG6M4W6DMOODNVhEu7jtO Aw3Vu2tfittrTp49ql6fnu5UwOx2hB35ScyeaTjteTS8AhWuRzPK0R4ODZPYxVoVJo2Y qWK/nq8y5ylD2ZkLkXBbizy9bZrcpaR/xAcKaLa8m0m71csGYTUrW+SZ24xEmW2REGSI jEXrXjA4cTwO7kXa5iKvm+veVlG/bnErMajMakpQdThA4Qwxy/85uaEPkCf67+Aj97L8 hvUw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1701040982; x=1701645782; h=content-transfer-encoding:mime-version:subject:references :in-reply-to:message-id:cc:to:from:date:x-gm-message-state:from:to :cc:subject:date:message-id:reply-to; bh=UHZHjutoH0d60QC8aQB2bmwmZO17B7xaWF9wB/ruq1I=; b=febp5POvea4aSTjiiZtxtNGmO7eB1JdF8ZngOztyfqCHt7I37XeGRfg4/M40crn0K0 ddE0/5L0wlNzdbesl1JUvzdJnY2UAEoARyWiNI/48Jx8J8nqTuqPAHgNMHkr+su4BBYC qizaiXZrU74Mw3ZY0g7AbLkbJvLOQzee6KrJLGOPGsa8fpNeYZh9g+bzvdKAH1Ah0nYv /CKtVRCFzNr9ZLrM+J2jhWrZKLmHIMvWRtP/bMvgoW2BIKkjd5bFkMD3NzPGcni0iiYm DhjNoeJoh06koDxeWcIun1zyVfpdhuDapJVUB7mj0zWrTIL6rilhyyxJacScOKXhX+y5 Ffhg== X-Gm-Message-State: AOJu0YwwvGy1zV2Vr+pVnairvsQQVGehIIvvbnvJ61sLM+kHKMw9XFrD HdCx1ryCMRFgzZOfo6f0e4k= X-Google-Smtp-Source: AGHT+IFMYfAHrdhir7595iHK08Qm9WldtW4TgXmHbLmNmROuwG3WUdT8iCnmA0aYVewBUw1mMeOkaQ== X-Received: by 2002:a05:6a20:438a:b0:18a:e176:5283 with SMTP id i10-20020a056a20438a00b0018ae1765283mr9586014pzl.39.1701040981694; Sun, 26 Nov 2023 15:23:01 -0800 (PST) Received: from [127.0.0.1] (c-73-116-164-136.hsd1.ca.comcast.net. [73.116.164.136]) by smtp.gmail.com with ESMTPSA id it18-20020a056a00459200b0068fe9c7b199sm6029391pfb.105.2023.11.26.15.23.00 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sun, 26 Nov 2023 15:23:01 -0800 (PST) Date: Sun, 26 Nov 2023 15:23:00 -0800 (PST) From: Joe B To: Sylvain Saboua Cc: freebsd-arm@freebsd.org Message-ID: <9e9f534d-489f-43c3-a532-4ec0a815596c@gmail.com> In-Reply-To: References: <7a13c63d-a50b-429c-a481-0693e9faaf6b@gmail.com> Subject: Re: Freebsd on M1 Macs List-Id: Porting FreeBSD to ARM processors List-Archive: https://lists.freebsd.org/archives/freebsd-arm List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arm@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Correlation-ID: <9e9f534d-489f-43c3-a532-4ec0a815596c@gmail.com> X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US] X-Rspamd-Queue-Id: 4SdlBb2rH1z3GkL Nov 26, 2023 3:11:24 PM Sylvain Saboua : > Per chance, had you stumbled yet on the helloSystem effort/proposal ? > > https://hellosystem.github.io/ > > =C2=AB=E2=80=AFIt is intended as a system for =E2=80=9Cmere mortals=E2=80= =9D, > welcoming to switchers from the Mac. FreeBSD is > used as the core operating system.=E2=80=AF=C2=BB > > Regards > > Le 2023-11-26 20:22, Joe B a =C3=A9crit=C2=A0: >> I know this is a longshot but I'm going to ask I know MacOS is a BSD but= we all know it's very sugarcoated and doesn't look like a BSD. >> Question will real freeBSD ever come to the m1 Mac's. I got a 16 inch mb= p with good specs just taking up space right now >> Thanks >> ~ Joe B > > -- > Sylvain Saboua > linktr.ee/Sylvain Looks nice. Don't see any mention of it running on an m1 Mac unless I'm missing somethi= ng? ~ Joe B From nobody Sun Nov 26 23:52:45 2023 X-Original-To: freebsd-arm@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4Sdlrt0PsGz52bwX for ; Sun, 26 Nov 2023 23:52:46 +0000 (UTC) (envelope-from kevans@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 4Sdlrs75KMz3Q7d for ; Sun, 26 Nov 2023 23:52:45 +0000 (UTC) (envelope-from kevans@FreeBSD.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1701042766; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=2ipyszTMn6kWFh6hcQGIKHuuLsTUlePYS+Eob8xr+yM=; b=T1SFkmo+hmHbtqfOnqCXGatbKz7RyYK9AtICcvuR2o7UoGR4vXfKg+djpCeQB9YR4qHRmp j9vTMasprwnVwHTjx1zTbf7WJjixHB/5Mgebcc3aW+LSUevCjRn28YqTJ92MWK4VD6a8gz hz6dx6uVZ4ezN4StIPZSAwHsb5P3mjLtnzhY2YkBRvCnj0EOQ8AjC74ccvhdm9vB1iGKu9 eFaTBrESrSu7Gnj5ltOk+kQiOzb8k9Rff+VKZlMtZFFgOB8ePPZ36h0H/fsSm0f0wiDngE Z5iHMdgbRg0Ffh4gA9NERVQfMhUqx5eXskzF6gAGHZQc6ViBhZ0ydSznMw4PlQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1701042766; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=2ipyszTMn6kWFh6hcQGIKHuuLsTUlePYS+Eob8xr+yM=; b=VeToOKgj4GvC7sZn3nnE9H5KgTUCHYVqR4HsUuIlcMKYUuiKIQGs264vIdziuVuK49ZDuW 03O+Z09AsIHRA3gST7Eae0ZUT2YYrQqKLQpEuYmrZIM/al6AlSSE/oebJLPelMDAnwh71i W1+abMcZu0+DzfY2jJXmrZhaRd3FYhIY7L/pCAIJzb7+lpEoG0PBprcDrXTj2VTpwNc1qu 5PUaiUpju7f/VFrQG0RLkuCUQCeiG6IcW+K6QGAmbcHORMpoUoKWJ9jJcF2+BElOTGnGBY Tek2okSF5zIWKk1XZ/D7kLnxV7DTXee3kf3YjZQ7MdAZk9Ps9qm7R8tnr/2FUw== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1701042766; a=rsa-sha256; cv=none; b=ayyM7AtYiPZhmfpEF3ZlpB3E5Ya42AgWINgielwmP+5oTtjO437m65empy/DDEpuVb58oT 2M8Eex8Cc96I6IQ1WZqrG99fTujfV70v2KtoabMAnxb04R/gDO0GGiJLu/tmQuk/ZPHCzh ebZr00jOwkItKfiPVygCvyXTfeIx2tU7AeWcJsrgHHy0A7twFxfw1khJYeQdDg4cDKiO6Q 84MD/cicMkj4hNeV1ZjNz09C7X4IRzPJsKRLQR2fj1rJA5bKBj1SQEch5FC9Jew0hxOXfr MtwRS4/6ZLrqWzCMrUj1dDkHM2SU689Y9iAtYDWgaPEmkO/3Y3BLtyiIWnUaYg== Received: from [10.9.4.95] (unknown [209.182.120.176]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits)) (Client did not present a certificate) (Authenticated sender: kevans/mail) by smtp.freebsd.org (Postfix) with ESMTPSA id 4Sdlrs56gGz808 for ; Sun, 26 Nov 2023 23:52:45 +0000 (UTC) (envelope-from kevans@FreeBSD.org) Message-ID: <3651f45a-a96a-4816-b8fe-5e239e08af22@FreeBSD.org> Date: Sun, 26 Nov 2023 17:52:45 -0600 List-Id: Porting FreeBSD to ARM processors List-Archive: https://lists.freebsd.org/archives/freebsd-arm List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arm@freebsd.org MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: Freebsd on M1 Macs Content-Language: en-US To: freebsd-arm@freebsd.org References: <7a13c63d-a50b-429c-a481-0693e9faaf6b@gmail.com> <1536d845-9073-4f9b-96f6-fa9647536c00@gmail.com> From: Kyle Evans In-Reply-To: <1536d845-9073-4f9b-96f6-fa9647536c00@gmail.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit On 11/26/23 16:04, Jason Bacon wrote: > On 11/26/23 13:22, Joe B wrote: >> >> I know this is a longshot but I'm going to ask I know MacOS is a BSD >> but we all know it's very sugarcoated and doesn't look like a BSD. >> >> Question will real freeBSD ever come to the m1 Mac's. I got a 16 inch >> mbp with good specs just taking up space right now >> >> Thanks >> >> ~ Joe B > > I assume you've seen https://wiki.freebsd.org/AppleSilicon.  Not sure > how up-to-date it is.  The wikis tend to lag behind reality in my > experience. > Yeah, this is a bit out of date. SMP and watchdog bits are good, along with some subset of the USB ports (IOMMU is a WIP). With the branch I'm working on right now, we can go full multi-user on a USB root. Work stalled for a bit because there was a general disagreement with how we integrated parts of the interrupt control into the interrupt framework, but I've been given a vision recently of a clear path forward, so hopefully we can move forward with that and unblock upstreaming some of the other bits. Thanks, Kyle Evans From nobody Mon Nov 27 01:38:55 2023 X-Original-To: freebsd-arm@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4SdpCS5FXHz52kr7 for ; Mon, 27 Nov 2023 01:39:00 +0000 (UTC) (envelope-from bacon4000@gmail.com) Received: from mail-qt1-x82e.google.com (mail-qt1-x82e.google.com [IPv6:2607:f8b0:4864:20::82e]) (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 4SdpCS06Vtz4RFy for ; Mon, 27 Nov 2023 01:39:00 +0000 (UTC) (envelope-from bacon4000@gmail.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20230601 header.b=J1NabQu0; spf=pass (mx1.freebsd.org: domain of bacon4000@gmail.com designates 2607:f8b0:4864:20::82e as permitted sender) smtp.mailfrom=bacon4000@gmail.com; dmarc=pass (policy=none) header.from=gmail.com Received: by mail-qt1-x82e.google.com with SMTP id d75a77b69052e-423c28db22eso3502511cf.1 for ; Sun, 26 Nov 2023 17:39:00 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1701049137; x=1701653937; darn=freebsd.org; h=content-transfer-encoding:in-reply-to:from:content-language :references:to:subject:user-agent:mime-version:date:message-id:from :to:cc:subject:date:message-id:reply-to; bh=fJcO76jfmdUHf1e1GJ9yubW/h6X63jGgBe/+/HSCChU=; b=J1NabQu0DPWxNF557sA4xTAaKj2JrDavNK6xKauClh8aGIosmrFbL6B8ihwBtCsHI7 SwDZZTC/QphwBfB9LWmWKloAUCVVUSmYG/JKFfa3QrJztREDh5Ud4NhtBJCHFmiUkDdg 3vtsyW6+GGEJM6ceLgzkFvGIYe9HqiOzxDSySKIa6dWhVIt5Dxbe/alBuspdAtXh+WV0 AR8hnjPXAc6fOk5db6OTiScviUdsUp2iMAO+DBLoDAr+wamcd9rGw/WVG3lz7ZwRbh7I 4zEmI4OJbPyeUqA6W5r64Uuzb5ETr8UgETpFC5GkI/S0xt4ug4WYEEFxOu+yuCrOPFaF odDQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1701049137; x=1701653937; h=content-transfer-encoding:in-reply-to:from:content-language :references:to:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=fJcO76jfmdUHf1e1GJ9yubW/h6X63jGgBe/+/HSCChU=; b=JglAAlwSzh9pX77xpmv1VBKc5rWfCUfk6lkmdrWQVWMTnhVfujXcmgrw0xyMEAWus2 RL5hqazfAYgTlu9eC/ufjQSv20tjdEry+bsafcdX9Zq77b6JsqS4McRh77scO+4o514m f6JtIgnp6ccwResAlwMekOt/JcXBWHJBg6kI9ZOBozb2u9IPztow9Ywtl1p5xOCBqUpm 9yD9K7zKQF/0Gvp+w1RZpft8AJbZSjyF4LiSyLVzkGFMq9FOdbvxxEjjlRY0ZRCxk9ig 5t/LpRrXcW+QL4dkgCTQF6dfZGsLGk92y9q/vpGuC6Ky+MidjLeXjxGf/zRpCm/DS3n8 IZ9A== X-Gm-Message-State: AOJu0YwXUiXyNaEPKB8LEEYeFxIYfq+wg1hUxSIaPZas+mOfcNQMKLUz hgnBCodvJsoPI3AXWCMi/Vp8nsqXrlg= X-Google-Smtp-Source: AGHT+IH+gangZ9lcWLi/Src9lZX8kMq7HzJ97Jbc2BQ6365q9dddvSLhhtB8fUZQCjDDrKAeW8sGDQ== X-Received: by 2002:ac8:5f83:0:b0:421:bb56:b2e with SMTP id j3-20020ac85f83000000b00421bb560b2emr17585609qta.0.1701049137028; Sun, 26 Nov 2023 17:38:57 -0800 (PST) Received: from [192.168.0.3] (cpe-184-58-230-200.wi.res.rr.com. [184.58.230.200]) by smtp.gmail.com with ESMTPSA id fu26-20020a05622a5d9a00b004166905aa2asm3345261qtb.28.2023.11.26.17.38.56 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sun, 26 Nov 2023 17:38:56 -0800 (PST) Message-ID: Date: Sun, 26 Nov 2023 19:38:55 -0600 List-Id: Porting FreeBSD to ARM processors List-Archive: https://lists.freebsd.org/archives/freebsd-arm List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arm@freebsd.org MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: Freebsd on M1 Macs To: freebsd-arm@freebsd.org References: <7a13c63d-a50b-429c-a481-0693e9faaf6b@gmail.com> <1536d845-9073-4f9b-96f6-fa9647536c00@gmail.com> <3651f45a-a96a-4816-b8fe-5e239e08af22@FreeBSD.org> Content-Language: en-US From: Jason Bacon In-Reply-To: <3651f45a-a96a-4816-b8fe-5e239e08af22@FreeBSD.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: base64 X-Spamd-Result: default: False [1.82 / 15.00]; NEURAL_SPAM_LONG(0.97)[0.966]; NEURAL_SPAM_MEDIUM(0.88)[0.875]; NEURAL_SPAM_SHORT(0.87)[0.866]; 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=20230601]; MIME_BASE64_TEXT(0.10)[]; MIME_GOOD(-0.10)[text/plain]; XM_UA_NO_VERSION(0.01)[]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; PREVIOUSLY_DELIVERED(0.00)[freebsd-arm@freebsd.org]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::82e:from]; ARC_NA(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; MLMMJ_DEST(0.00)[freebsd-arm@freebsd.org]; DKIM_TRACE(0.00)[gmail.com:+]; TO_DN_NONE(0.00)[]; FREEMAIL_FROM(0.00)[gmail.com]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; RCVD_TLS_LAST(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: 4SdpCS06Vtz4RFy X-Spamd-Bar: + T24gMTEvMjYvMjMgMTc6NTIsIEt5bGUgRXZhbnMgd3JvdGU6DQo+IE9uIDExLzI2LzIzIDE2 OjA0LCBKYXNvbiBCYWNvbiB3cm90ZToNCj4+IE9uIDExLzI2LzIzIDEzOjIyLCBKb2UgQiB3 cm90ZToNCj4+Pg0KPj4+IEkga25vdyB0aGlzIGlzIGEgbG9uZ3Nob3QgYnV0IEknbSBnb2lu ZyB0byBhc2sgSSBrbm93IE1hY09TIGlzIGEgQlNEIA0KPj4+IGJ1dCB3ZSBhbGwga25vdyBp dCdzIHZlcnkgc3VnYXJjb2F0ZWQgYW5kIGRvZXNuJ3QgbG9vayBsaWtlIGEgQlNELg0KPj4+ DQo+Pj4gUXVlc3Rpb24gd2lsbCByZWFsIGZyZWVCU0QgZXZlciBjb21lIHRvIHRoZSBtMSBN YWMncy4gSSBnb3QgYSAxNiBpbmNoIA0KPj4+IG1icCB3aXRoIGdvb2Qgc3BlY3MganVzdCB0 YWtpbmcgdXAgc3BhY2UgcmlnaHQgbm93DQo+Pj4NCj4+PiBUaGFua3MNCj4+Pg0KPj4+IH4g Sm9lIEINCj4+DQo+PiBJIGFzc3VtZSB5b3UndmUgc2VlbiBodHRwczovL3dpa2kuZnJlZWJz ZC5vcmcvQXBwbGVTaWxpY29uLsKgIE5vdCBzdXJlIA0KPj4gaG93IHVwLXRvLWRhdGUgaXQg aXMuwqAgVGhlIHdpa2lzIHRlbmQgdG8gbGFnIGJlaGluZCByZWFsaXR5IGluIG15IA0KPj4g ZXhwZXJpZW5jZS4NCj4+DQo+IA0KPiBZZWFoLCB0aGlzIGlzIGEgYml0IG91dCBvZiBkYXRl LsKgIFNNUCBhbmQgd2F0Y2hkb2cgYml0cyBhcmUgZ29vZCwgYWxvbmcgDQo+IHdpdGggc29t ZSBzdWJzZXQgb2YgdGhlIFVTQiBwb3J0cyAoSU9NTVUgaXMgYSBXSVApLsKgIFdpdGggdGhl IGJyYW5jaCBJJ20gDQo+IHdvcmtpbmcgb24gcmlnaHQgbm93LCB3ZSBjYW4gZ28gZnVsbCBt dWx0aS11c2VyIG9uIGEgVVNCIHJvb3QuwqAgV29yaw0KPiBzdGFsbGVkIGZvciBhIGJpdCBi ZWNhdXNlIHRoZXJlIHdhcyBhIGdlbmVyYWwgZGlzYWdyZWVtZW50IHdpdGggaG93IHdlIA0K PiBpbnRlZ3JhdGVkIHBhcnRzIG9mIHRoZSBpbnRlcnJ1cHQgY29udHJvbCBpbnRvIHRoZSBp bnRlcnJ1cHQgZnJhbWV3b3JrLCANCj4gYnV0IEkndmUgYmVlbiBnaXZlbiBhIHZpc2lvbiBy ZWNlbnRseSBvZiBhIGNsZWFyIHBhdGggZm9yd2FyZCwgc28gDQo+IGhvcGVmdWxseSB3ZSBj YW4gbW92ZSBmb3J3YXJkIHdpdGggdGhhdCBhbmQgdW5ibG9jayB1cHN0cmVhbWluZyBzb21l IG9mIA0KPiB0aGUgb3RoZXIgYml0cy4NCj4gDQo+IFRoYW5rcywNCj4gDQo+IEt5bGUgRXZh bnMNCj4gDQoNClRoYXQncyBleGNpdGluZyBuZXdzLCB0aGFua3MgS3lsZSEgIEknbSBwZXJz b25hbGx5IGxvb2tpbmcgZm9yd2FyZCB0byANCnVzaW5nIE1hYyBNaW5pcyAvIFN0dWRpb3Mg YXMgSFBDIGNsdXN0ZXIgbm9kZXMuICBUaGV5IHdpbGwgYmUgYSANCmdhbWUtY2hhbmdlciBm b3Igc21hbGwgc2NhbGUgSFBDLCBhbGxvd2luZyBmb3IgdGhlIGZpcnN0IHRpbWUgc29tZSAN CnNlcmlvdXMgY29tcHV0aW5nIHBvd2VyIGluIGEgdHlwaWNhbCBvZmZpY2UgcmF0aGVyIHRo YW4gcmVxdWlyaW5nIGEgZGF0YSANCmNlbnRlci4NCg0KSSdsbCBiZSBnZXR0aW5nIGJhY2sg dG8gd29yayBvbiB0aGUgTFBKUyBzY2hlZHVsZXIgc29vbiwgc28gd2UgaGF2ZSBhbiANCmFs dGVybmF0aXZlIHRvIFNMVVJNLCB3aGljaCBoYXMgYmVjb21lIHRvbyBjb21wbGV4IGFuZCBM aW51eC1jZW50cmljLg0KDQotLSANCkxpZmUgaXMgYSBnYW1lLiAgUGxheSBoYXJkLiAgUGxh eSBmYWlyLiAgSGF2ZSBmdW4uDQoNCg== From nobody Tue Nov 28 11:31:32 2023 X-Original-To: freebsd-arm@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4SfgJx5L4Dz52vs7 for ; Tue, 28 Nov 2023 11:31:45 +0000 (UTC) (envelope-from titus@edc.ro) Received: from eatlas.ro (eatlas.ro [86.126.82.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 (2048 bits) client-digest SHA256) (Client CN "eatlas.ro", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4SfgJw1HGpz3H8r for ; Tue, 28 Nov 2023 11:31:43 +0000 (UTC) (envelope-from titus@edc.ro) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=edc.ro header.s=mail header.b=xrtXiIlN; spf=pass (mx1.freebsd.org: domain of titus@edc.ro designates 86.126.82.18 as permitted sender) smtp.mailfrom=titus@edc.ro; dmarc=none Received: from mail.edc.ro ([10.1.4.58]) by eatlas.ro (8.16.1/8.16.1) with ESMTPS id 3ASBVXs1000434 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NOT) for ; Tue, 28 Nov 2023 13:31:33 +0200 (EET) (envelope-from titus@edc.ro) Received: from tituss-imac.eatlas.local (eatlas.ro [86.126.82.18]) (authenticated bits=0) by mail.edc.ro (8.16.1/8.16.1) with ESMTPSA id 3ASBVWq4008840 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT) for ; Tue, 28 Nov 2023 13:31:32 +0200 (EET) (envelope-from titus@edc.ro) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=edc.ro; s=mail; t=1701171092; bh=6Rr8cK4jGo6xuqTgntY8c71uoHVSKazWdlRScdk+kmA=; h=From:Subject:Date:To; b=xrtXiIlNgf8XMLEJRoT1oLdvzyoXe8MxgEU8JcArq7p3gIZvz7kmjQkd3OzoRoX8b R1JbN8Jj+fnhotfcRK/XGPt+m9VjPSho7pzPNMcjQi47Qq7kY3GMEPfVbgDimbPKUz dfc+28d4C061EXXfgVTmY4EsPM4OJ9daI/lvXl78= From: titus Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable List-Id: Porting FreeBSD to ARM processors List-Archive: https://lists.freebsd.org/archives/freebsd-arm List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arm@freebsd.org Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.7\)) Subject: Generic AHCI fdt Message-Id: Date: Tue, 28 Nov 2023 13:31:32 +0200 To: freebsd-arm X-Mailer: Apple Mail (2.3608.120.23.2.7) X-Spam-Checker-Version: SpamAssassin 4.0.0 (2022-12-14) on ns.edc.ro X-Spamd-Result: default: False [-2.93 / 15.00]; NEURAL_HAM_MEDIUM(-0.98)[-0.985]; NEURAL_HAM_SHORT(-0.98)[-0.978]; NEURAL_HAM_LONG(-0.96)[-0.964]; MV_CASE(0.50)[]; R_SPF_ALLOW(-0.20)[+mx]; R_DKIM_ALLOW(-0.20)[edc.ro:s=mail]; MIME_GOOD(-0.10)[text/plain]; MLMMJ_DEST(0.00)[freebsd-arm@freebsd.org]; DKIM_TRACE(0.00)[edc.ro:+]; TO_DN_ALL(0.00)[]; ASN(0.00)[asn:8708, ipnet:86.120.0.0/13, country:RO]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; RCVD_VIA_SMTP_AUTH(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; MID_RHS_MATCH_FROM(0.00)[]; ARC_NA(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; FROM_HAS_DN(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-arm@freebsd.org]; TO_MATCH_ENVRCPT_ALL(0.00)[]; DMARC_NA(0.00)[edc.ro]; RCVD_TLS_ALL(0.00)[] X-Rspamd-Queue-Id: 4SfgJw1HGpz3H8r X-Spamd-Bar: -- Hi, I have extended the implementation of ahci_generic for fdt do be able to = use external phy=E2=80=99s, clocks, resets and per compatiblity string = quirks Would it be better to stuff it in ahci_generic or separate current = ahci_generic.c in 2 files one for fdt and one for acpi ? From nobody Tue Nov 28 15:10:02 2023 X-Original-To: freebsd-arm@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4Sfm8w4rHfz539pQ for ; Tue, 28 Nov 2023 15:10:08 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [50.1.20.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-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "www.zefox.com", Issuer "www.zefox.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Sfm8v5glYz3FH1 for ; Tue, 28 Nov 2023 15:10:07 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Authentication-Results: mx1.freebsd.org; dkim=none; spf=none (mx1.freebsd.org: domain of fbsd@www.zefox.net has no SPF policy when checking 50.1.20.27) smtp.mailfrom=fbsd@www.zefox.net; dmarc=none Received: from www.zefox.net (localhost [127.0.0.1]) by www.zefox.net (8.17.1/8.15.2) with ESMTPS id 3ASFA2TW073378 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO) for ; Tue, 28 Nov 2023 07:10:02 -0800 (PST) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.17.1/8.15.2/Submit) id 3ASFA23l073377 for freebsd-arm@freebsd.org; Tue, 28 Nov 2023 07:10:02 -0800 (PST) (envelope-from fbsd) Date: Tue, 28 Nov 2023 07:10:02 -0800 From: bob prohaska To: freebsd-arm@freebsd.org Subject: reboot hesitation on Pi3 running -current Message-ID: List-Id: Porting FreeBSD to ARM processors List-Archive: https://lists.freebsd.org/archives/freebsd-arm List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arm@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Spamd-Result: default: False [0.83 / 15.00]; AUTH_NA(1.00)[]; NEURAL_HAM_SHORT(-0.98)[-0.981]; NEURAL_HAM_LONG(-0.60)[-0.596]; NEURAL_SPAM_MEDIUM(0.50)[0.503]; MID_RHS_WWW(0.50)[]; WWW_DOT_DOMAIN(0.50)[]; MIME_GOOD(-0.10)[text/plain]; FROM_EQ_ENVFROM(0.00)[]; ASN(0.00)[asn:7065, ipnet:50.1.16.0/20, country:US]; R_DKIM_NA(0.00)[]; MLMMJ_DEST(0.00)[freebsd-arm@freebsd.org]; MIME_TRACE(0.00)[0:+]; R_SPF_NA(0.00)[no SPF record]; DMARC_NA(0.00)[zefox.net]; RCPT_COUNT_ONE(0.00)[1]; TO_DN_NONE(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; ARC_NA(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; FROM_HAS_DN(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-arm@freebsd.org]; TO_MATCH_ENVRCPT_ALL(0.00)[]; RCVD_TLS_LAST(0.00)[] X-Rspamd-Queue-Id: 4Sfm8v5glYz3FH1 X-Spamd-Bar: / A Pi3 running -current has taken to pausing during a shutdown -r in a strange way: It gets to: Hit [Enter] to boot immediately, or any other key for command prompt. Booting [/boot/kernel/kernel] in 5 second more detailed help. It then stops at the OK prompt: OK boot <---typing boot fails: unknown command <---this looks strange, the kernel should already be loaded OK boot kernel <---specifying kernel makes something happy Loading kernel... /boot/kernel/kernel text=0x2a8 text=0x95edb0 text=0x2a875c data=0x15acc8 data=0x0+0x37a000 syms=[0x8+0x158f88+0x8+0x182eee] The boot then proceeds as usual. No idea if this is significant, but it is somewhat odd. Thanks for reading, bob prohaska From nobody Tue Nov 28 15:20:03 2023 X-Original-To: freebsd-arm@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4SfmNj3pBwz53Fsh for ; Tue, 28 Nov 2023 15:20:21 +0000 (UTC) (envelope-from marklmi@yahoo.com) Received: from sonic309-20.consmr.mail.gq1.yahoo.com (sonic309-20.consmr.mail.gq1.yahoo.com [98.137.65.146]) (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) by mx1.freebsd.org (Postfix) with ESMTPS id 4SfmNj1D1hz3MBB for ; Tue, 28 Nov 2023 15:20:21 +0000 (UTC) (envelope-from marklmi@yahoo.com) Authentication-Results: mx1.freebsd.org; none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1701184819; bh=6vqjbV2zrKieVOVYq2I2YfbT1SFsuhdwFABeMEUlJ9k=; h=Subject:From:In-Reply-To:Date:Cc:References:To:From:Subject:Reply-To; b=HH04mYQhQFqsJgz401k4cuD9BFuQj4FUKgpp1QCYmuwVLvNGkt+UKIXC+deqOL85cKj7QcCIGFo4EJS5Ep1geF/DzOTTOM3ceCsk7YUvgZAG7KidG27qNNB1n0BEa9hIig4HwPEBzRBy3fur7Kit37yhWL5fK1B1doCyLZHV1Qr0B3XfYAsBI6CDsB4EenJXlTUhnl2o19/JvGbcjuSLaVni5fOXgan9e9foxD7FnmKGkQKzas/Q5779OfOthghz0yRTC4hHLebxVqjT074aO6aKeDNEtJ5UgDQTRPZ9J1N7uG/ckm4ScuZosvLeplqVZRhCZq+01CmQzg7L+HfuwA== X-SONIC-DKIM-SIGN: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1701184819; bh=PWFLFnvA9KA6s60C0+ZXErfir+BYlHEbBlQezIgsdt7=; h=X-Sonic-MF:Subject:From:Date:To:From:Subject; b=sIdgFyAc/R27IjpVNMni+qJxV65QRMvVQnZJB+80qW48/e5hRCq1Wl3x7AQTJCt/Rcutv7oWzX6RPqet3CMwNpMZ7AQ1JN5EIUNR6NE64Tfo+EbFg4WZeeJZ5FqlgHEdHkMv1yqa03AWMDC8EVTMoe/bsLjEMUjRuZklMTZDkj6UNi9uKVpAzOM6S6nYz0XttnQH+iGAkJQoKI8zEzBYDpk4L/nJC+AKEbgTNKta6C08yUFvi6wVjBqKnV2L6Rq959UbG0x5yN8QTEiqMjCHXSIdJ74KDqXhfu4H1YfDVbAo624ksg9RYpzdSL4LXd9z6FqtyrLBkHeGAK1i6MdBkw== X-YMail-OSG: GPQBC.0VM1kxVnLumxGQ6UYGPM40Wm4ApvBe1MCOrXdePoltvJYfW03zxaFkAbO rNxAVut4bCsWqkfBZ4Cmn17gL52fZgjtN9xNPIEKEGkHAHeNI9lF_RR7L8GxGhuBuNw9nW7yZJhW JDQ4Iukn2q4fwHfNQ0jh69KEdM98PR4HY6Bp6VOkwgDGMz42YzHlngc1WFlH5A6AeU5n2ruTCqtX osTholhdpGlVIc3wKYBx7DiMw9tjRCS7R1jrXtuoOakooX1bRUsj10FD_gfzJXGlgf5gfbyxetJg jI5gQ3oUz9miKsHbxQnmfVsodIWBY3ODTuiyxrfNlUBH6g4fR7fuBrgvQllzgx3Bsz5qFmDUwBVo .LeQl6F2Q13mL_nK8evpQUZQV7T310N1maf1VeWWzOeQ34iFdRiWr8_7V2rOp_roB9G.qD2XjF8L BBTxPQavAHkUL6gjyec2loL2FC5g_w0zuflD9md0.pRrXEAep5bJ9VVCAyXHZ2rOMB0ZEIIGkD4b UG_ILI3.q.Nfrs53LL0LjroAg..1cQA1lO0AZXhbpJjx6fPVnphn8suJaY8xC9Cn6KiB4q8aXqVv i.HRb_0mbQIgkmdHXAKf_mlxKCJ_x6DMKm2ipAMUM8saB5qx38TrtX.SyTwT.W__gAw1WblRS7Ba ylTBnkH.0OXkuUZ.Pch.fBFpS9WB_8XMF7bb60vQK7CZN4_vQ1rUrTAsMTSplnsHnSYi7xHC_ewV vXIo0woBkV5abuugpZHfFbUt69eznYDbvSrB6iIZ22ar_Febfg3KN42KvTCQ2Fc_Sq1OeCG6QfbI CsBX_0guOKA7TvRu4KvmnqHJWG_rMUO88isR3uFquZkjMrI_4IEwQwRoppouxz4tE6a81rj_b6Gs SFTzcsmbBsLInrGU6_7ca.HRS4q4EM.tp5sFt_ayJmAmn8Va_eBpcSatTu2S_ZAbBw1KVZ6vPyr4 c.zG7a7E9nl.LTcS41iPhT0EglqJWlWQKFG5Uw6ygCWR3YfMWFeH_RVJTKAqub6ek6aGu2hq8d9k hZzlikmslN3Olwzt40gxbyaxtemYFEVxnUhH5HhRyioGkJxVf.KEiOvZZIXxNM2M9jIG5HvG.q3N SgcQc8goa7vli.Fm1.Yvm1rLu0aqDNJn0NRHCInl44m9lFf8W8RYu2sI43.2i.GCflHaxWllO54L FIzXvz0ce_V9Mu9GSrznIbZkgGThpHNqRwK9LxzN7k5C5kOLpKtXLxfGn4s2M6fD6MElvk2Pjkzc PMuxs_B5FeJiyk88SRC5j3ipqQt5xtv04XcBKGrDpw4nZ6MGmyUOMhFzR6T7HasgCXPSmLuaAXIe pSggzLkeEJNZ23PT8YvcI.8Kp.xeOU2leP6gNWpjr_3e_O5WBbzpCAxJiQz.0zHeLV1CmEitQLpQ RodZw7uIPdHFaJlRoNpTzkgPFxUN8duA_dofRTdqQ.FhDDYq.ZuZpPeUPz8MIpI2SmA3JJPNTtPA SReXOYM8ebacJOPNvIH88oA.70hQ0m_ySldZTIexlgpoy2B708j5Ci3CycA3J_zJtQsw8HpZpZWg .8kzGpE7BNX2UyEVAs14EX6Gd3Z4eCCKGKVQiwWlZO8bF6jHeBYIHlSBPDygFnI89Wn8gkaYg7gR nuBemCivencmlD8qNYs.iUKjeuCjKN14DjRiC1avBhYdrwYgUsJIwo0uVhvzVMJxptDiPZQlYG0h fq3417rAJ5A9XlqzY7N113kqfnh9FmuNliYm.IdE7T7BuWjY82.Psr4iUxtRecp4ugp0KHy.tuxc pLH02PiTHCowqxGMuNpweU3Q3tkbJCG.ZGS4OEaxQPAMYaXveoD1N5Zk9394BwsWXqiN8aGraTpP eEh_715zsFybvn.YNf8ZwL7s2U2SL2puuEDzmTJC_BvpTEEOUuc8llJmaBaHaqXcr3HhH43I2QPx cyuk8Wwu9fMfe82TGpMJ7sne7os8.V7sNmkp8YAwHV.sP0rqqwRz7Nqgcx9rxwK8C8JW_mEB_edO RMqUfiWZZOPoFf.KrJz4mC7EWmPeB3TRNzl2O21IRfsCL0HvU04pAp2.Y89Xu5emavqeOZeAGWIl cxHGNhqfpnqORyb2ohg9y0uAal45XMDYtjVJbMgQMV2hwOWszs0UftbW7O1kpEyi6riGOjScVh56 ABbNw1YKUOLH2Jmxeu46Qow.1FeBM6gACiyKciwpOAWegN.Hvg1rS7pa6lj8.I3h_w55hNa6Amq2 e6A99tmmQKeZEn_.K1g3iy6sWz8QhLVCvaBdTsL8V3pndMoMKSrApg2CVI7jbSEd41UCg X-Sonic-MF: X-Sonic-ID: b14520da-cc1e-4ceb-9655-62ee6982e328 Received: from sonic.gate.mail.ne1.yahoo.com by sonic309.consmr.mail.gq1.yahoo.com with HTTP; Tue, 28 Nov 2023 15:20:19 +0000 Received: by hermes--production-gq1-5cf8f76c44-zkczr (Yahoo Inc. Hermes SMTP Server) with ESMTPA ID 9c9244f28e8970fea99af2242f038d3e; Tue, 28 Nov 2023 15:20:14 +0000 (UTC) Content-Type: text/plain; charset=us-ascii List-Id: Porting FreeBSD to ARM processors List-Archive: https://lists.freebsd.org/archives/freebsd-arm List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arm@freebsd.org Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.200.91.1.1\)) Subject: Re: reboot hesitation on Pi3 running -current From: Mark Millard In-Reply-To: Date: Tue, 28 Nov 2023 07:20:03 -0800 Cc: freebsd-arm Content-Transfer-Encoding: quoted-printable Message-Id: <4078F04C-B4AA-4029-B260-2A075A8832DA@yahoo.com> References: To: bob prohaska X-Mailer: Apple Mail (2.3774.200.91.1.1) X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:36647, ipnet:98.137.64.0/20, country:US] X-Rspamd-Queue-Id: 4SfmNj1D1hz3MBB On Nov 28, 2023, at 07:10, bob prohaska wrote: > A Pi3 running -current has taken to pausing during a shutdown -r in a = strange way: > It gets to:=20 >=20 > Hit [Enter] to boot immediately, or any other key for command prompt. > Booting [/boot/kernel/kernel] in 5 second more detailed help. >=20 > It then stops at the OK prompt: >=20 > OK boot <---typing boot fails: >=20 > unknown command <---this looks strange, the kernel should already be = loaded A possibility here is garbage control characters, say before the "boot". YOu might want to type just to the first OK prompt and see if you ever still get "unknown command" once you do type just "boot" (and ). The fact that the countdown stopped at 5 (or other early value) suggests such extra text at that point. > OK boot kernel <---specifying kernel makes something happy=20 > Loading kernel... > /boot/kernel/kernel text=3D0x2a8 text=3D0x95edb0 text=3D0x2a875c = data=3D0x15acc8 data=3D0x0+0x37a000 syms=3D[0x8+0x158f88+0x8+0x182eee] >=20 > The boot then proceeds as usual. >=20 > No idea if this is significant, but it is somewhat odd. =3D=3D=3D Mark Millard marklmi at yahoo.com From nobody Tue Nov 28 16:15:30 2023 X-Original-To: freebsd-arm@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4SfncN1f7Pz529Md for ; Tue, 28 Nov 2023 16:15:32 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [50.1.20.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-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "www.zefox.com", Issuer "www.zefox.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4SfncM6pmBz3TqX for ; Tue, 28 Nov 2023 16:15:31 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Authentication-Results: mx1.freebsd.org; none Received: from www.zefox.net (localhost [127.0.0.1]) by www.zefox.net (8.17.1/8.15.2) with ESMTPS id 3ASGFVBo073611 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Tue, 28 Nov 2023 08:15:31 -0800 (PST) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.17.1/8.15.2/Submit) id 3ASGFVmQ073610; Tue, 28 Nov 2023 08:15:31 -0800 (PST) (envelope-from fbsd) Date: Tue, 28 Nov 2023 08:15:30 -0800 From: bob prohaska To: Mark Millard Cc: freebsd-arm Subject: Re: reboot hesitation on Pi3 running -current Message-ID: References: <4078F04C-B4AA-4029-B260-2A075A8832DA@yahoo.com> List-Id: Porting FreeBSD to ARM processors List-Archive: https://lists.freebsd.org/archives/freebsd-arm List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arm@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4078F04C-B4AA-4029-B260-2A075A8832DA@yahoo.com> X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:7065, ipnet:50.1.16.0/20, country:US] X-Rspamd-Queue-Id: 4SfncM6pmBz3TqX On Tue, Nov 28, 2023 at 07:20:03AM -0800, Mark Millard wrote: > On Nov 28, 2023, at 07:10, bob prohaska wrote: > > > A Pi3 running -current has taken to pausing during a shutdown -r in a strange way: > > It gets to: > > > > Hit [Enter] to boot immediately, or any other key for command prompt. > > Booting [/boot/kernel/kernel] in 5 second more detailed help. > > > > It then stops at the OK prompt: > > > > OK boot <---typing boot fails: > > > > unknown command <---this looks strange, the kernel should already be loaded > > A possibility here is garbage control characters, say before > the "boot". YOu might want to type just to the first OK > prompt and see if you ever still get "unknown command" once you > do type just "boot" (and ). IIRC I've done that in the past with the same result, but memory is hazy and an attempt at a second shutdown -r came back up without hesitation. Another build/install cycle is running now, I'll be more careful next time. > > The fact that the countdown stopped at 5 (or other early value) > suggests such extra text at that point. > Rubbish on the serial console is a common occurence, but it usually shows up when the USB end is taken down and brought back up. In this case the USB end remained up throughout the reboot cycle, no stray characters were visible. Thanks for writing! bob prohaska From nobody Tue Nov 28 17:05:59 2023 X-Original-To: freebsd-arm@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4Sfpks2wWZz52Dhw for ; Tue, 28 Nov 2023 17:06:13 +0000 (UTC) (envelope-from sr@genyosha.net) Received: from ns0.genyosha.net (ns0.genyosha.net [50.39.243.220]) (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 "float.home.genyosha.net", Issuer "float.home.genyosha.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Sfpkr4H5nz3bgT for ; Tue, 28 Nov 2023 17:06:12 +0000 (UTC) (envelope-from sr@genyosha.net) Authentication-Results: mx1.freebsd.org; dkim=none; spf=pass (mx1.freebsd.org: domain of sr@genyosha.net designates 50.39.243.220 as permitted sender) smtp.mailfrom=sr@genyosha.net; dmarc=none Received: from dragon.home.genyosha.net (ops0.genyosha.net [50.39.243.219]) by ns0.genyosha.net (8.17.1/8.17.1) with ESMTPS id 3ASH64Gc007046 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for ; Tue, 28 Nov 2023 09:06:04 -0800 (PST) (envelope-from sr@genyosha.net) Received: from dragon.home.genyosha.net (localhost [127.0.0.1]) by dragon.home.genyosha.net (8.14.7/8.14.7) with ESMTP id 3ASH5xs0026902 for ; Tue, 28 Nov 2023 09:05:59 -0800 Received: (from sr@localhost) by dragon.home.genyosha.net (8.14.7/8.14.7/Submit) id 3ASH5x1T026901 for freebsd-arm@freebsd.org; Tue, 28 Nov 2023 09:05:59 -0800 Date: Tue, 28 Nov 2023 09:05:59 -0800 From: Steve Rikli To: freebsd-arm Subject: Re: reboot hesitation on Pi3 running -current Message-ID: References: <4078F04C-B4AA-4029-B260-2A075A8832DA@yahoo.com> List-Id: Porting FreeBSD to ARM processors List-Archive: https://lists.freebsd.org/archives/freebsd-arm List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arm@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Greylist: inspected by milter-greylist-4.6.4 (ns0.genyosha.net [50.39.243.220]); Tue, 28 Nov 2023 09:06:04 -0800 (PST) for IP:'50.39.243.219' DOMAIN:'ops0.genyosha.net' HELO:'dragon.home.genyosha.net' FROM:'sr@genyosha.net' RCPT:'' X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.6.4 (ns0.genyosha.net [50.39.243.220]); Tue, 28 Nov 2023 09:06:04 -0800 (PST) X-Spamd-Result: default: False [0.04 / 15.00]; NEURAL_SPAM_SHORT(1.00)[1.000]; NEURAL_HAM_LONG(-0.77)[-0.769]; R_SPF_ALLOW(-0.20)[+mx]; NEURAL_SPAM_MEDIUM(0.11)[0.111]; MIME_GOOD(-0.10)[text/plain]; MLMMJ_DEST(0.00)[freebsd-arm@freebsd.org]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; TO_DN_ALL(0.00)[]; MIME_TRACE(0.00)[0:+]; MID_RHS_MATCH_FROMTLD(0.00)[]; ARC_NA(0.00)[]; ASN(0.00)[asn:20055, ipnet:50.39.128.0/17, country:US]; TO_MATCH_ENVRCPT_ALL(0.00)[]; FROM_HAS_DN(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; PREVIOUSLY_DELIVERED(0.00)[freebsd-arm@freebsd.org]; RCPT_COUNT_ONE(0.00)[1]; DMARC_NA(0.00)[genyosha.net]; RCVD_TLS_LAST(0.00)[] X-Rspamd-Queue-Id: 4Sfpkr4H5nz3bgT X-Spamd-Bar: / On Tue, Nov 28, 2023 at 08:15:30AM -0800, bob prohaska wrote: > On Tue, Nov 28, 2023 at 07:20:03AM -0800, Mark Millard wrote: > > On Nov 28, 2023, at 07:10, bob prohaska wrote: > > > > > A Pi3 running -current has taken to pausing during a shutdown -r in a strange way: > > > It gets to: > > > > > > Hit [Enter] to boot immediately, or any other key for command prompt. > > > Booting [/boot/kernel/kernel] in 5 second more detailed help. > > > > > > It then stops at the OK prompt: > > > > > > OK boot <---typing boot fails: > > > > > > unknown command <---this looks strange, the kernel should already be loaded > > > > A possibility here is garbage control characters, say before > > the "boot". YOu might want to type just to the first OK > > prompt and see if you ever still get "unknown command" once you > > do type just "boot" (and ). > > IIRC I've done that in the past with the same result, but memory is hazy > and an attempt at a second shutdown -r came back up without hesitation. > > Another build/install cycle is running now, I'll be more careful next time. > > > The fact that the countdown stopped at 5 (or other early value) > > suggests such extra text at that point. > > Rubbish on the serial console is a common occurence, but it usually > shows up when the USB end is taken down and brought back up. In this > case the USB end remained up throughout the reboot cycle, no stray > characters were visible. > > Thanks for writing! This topic has come up before here, I believe. I can confirm the same or very similar behavior on rpi4, and there's no USB-serial to disconnect on the remote end, rather an actual serial console server which is always-on. Unfortunately it's not consistent behavior, i.e. sometimes the reboot proceeds uninterrupted. Sometimes typing 'boot' proceeds normally, sometimes typing 'boot' errors and then typing it again proceeds as normal. I too have been thinking it's spurious chars on the serial console at various points, but I've yet to find a common behavior or consistent method to reproduce. This doesn't happen on my other serial consoles, FreeBSD or Linux. I also don't think it happened early on when this rpi4 was running raspbian for a brief time, but I didn't play with that setup very long. So far I believe it's avoidable by not watching the serial console during reboot, not necessary (I think) to disconnect the cable. But obviously that defeats the purpose of the serial console vs. a blind reboot. I plan to upgrade my rpi4 to 14.0 just to see if anything changes. Iirc from the relnotes, one of the changes in new release is 115200 is the new default for serial communications, and I have some hope that maybe some hard-to-find hard-coded 9600 may have been thwarting those of us running with different speed infrastructure and console. Since bob is running -current on his rpi3 though, my hope is probably a longshot. Cheers, sr. From nobody Tue Nov 28 20:00:08 2023 X-Original-To: freebsd-arm@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4SftbZ1G57z52TF9 for ; Tue, 28 Nov 2023 20:00:10 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [50.1.20.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-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "www.zefox.com", Issuer "www.zefox.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4SftbY3r1Cz4Zts for ; Tue, 28 Nov 2023 20:00:09 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Authentication-Results: mx1.freebsd.org; none Received: from www.zefox.net (localhost [127.0.0.1]) by www.zefox.net (8.17.1/8.15.2) with ESMTPS id 3ASK09wG074405 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Tue, 28 Nov 2023 12:00:09 -0800 (PST) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.17.1/8.15.2/Submit) id 3ASK08ZN074404; Tue, 28 Nov 2023 12:00:08 -0800 (PST) (envelope-from fbsd) Date: Tue, 28 Nov 2023 12:00:08 -0800 From: bob prohaska To: Steve Rikli Cc: freebsd-arm Subject: Re: reboot hesitation on Pi3 running -current Message-ID: References: <4078F04C-B4AA-4029-B260-2A075A8832DA@yahoo.com> List-Id: Porting FreeBSD to ARM processors List-Archive: https://lists.freebsd.org/archives/freebsd-arm List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arm@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:7065, ipnet:50.1.16.0/20, country:US] X-Rspamd-Queue-Id: 4SftbY3r1Cz4Zts On Tue, Nov 28, 2023 at 09:05:59AM -0800, Steve Rikli wrote: > On Tue, Nov 28, 2023 at 08:15:30AM -0800, bob prohaska wrote: > > On Tue, Nov 28, 2023 at 07:20:03AM -0800, Mark Millard wrote: > > > On Nov 28, 2023, at 07:10, bob prohaska wrote: > > > > > > > A Pi3 running -current has taken to pausing during a shutdown -r in a strange way: > > > > It gets to: > > > > > > > > Hit [Enter] to boot immediately, or any other key for command prompt. > > > > Booting [/boot/kernel/kernel] in 5 second more detailed help. > > > > > > > > It then stops at the OK prompt: > > > > > > > > OK boot <---typing boot fails: > > > > > > > > unknown command <---this looks strange, the kernel should already be loaded > > > > > > A possibility here is garbage control characters, say before > > > the "boot". YOu might want to type just to the first OK > > > prompt and see if you ever still get "unknown command" once you > > > do type just "boot" (and ). > > > > IIRC I've done that in the past with the same result, but memory is hazy > > and an attempt at a second shutdown -r came back up without hesitation. > > > > Another build/install cycle is running now, I'll be more careful next time. > > > > > The fact that the countdown stopped at 5 (or other early value) > > > suggests such extra text at that point. > > > > Rubbish on the serial console is a common occurence, but it usually > > shows up when the USB end is taken down and brought back up. In this > > case the USB end remained up throughout the reboot cycle, no stray > > characters were visible. > > > > Thanks for writing! > > This topic has come up before here, I believe. > > I can confirm the same or very similar behavior on rpi4, and there's no > USB-serial to disconnect on the remote end, rather an actual serial > console server which is always-on. > That's a significant (I think) observation. I couldn't tell where the stray characters were originating and suspected the USB-serial adapter. Your experience suggests very strongly the trouble is local to the serial UART on the Pi or maybe wiring problems. Is it possible that the serial port of the monitoring devices occasionally echos output from the Pi's console back to the Pi? Seems to me it shouldn't, but sometimes I see fragments of a login prompt among the rubbish. > Unfortunately it's not consistent behavior, i.e. sometimes the reboot > proceeds uninterrupted. Sometimes typing 'boot' proceeds normally, > sometimes typing 'boot' errors and then typing it again proceeds as > normal. Does it sometimes reboot hands-off? Mine does, at least occasionally. > > I too have been thinking it's spurious chars on the serial console at > various points, but I've yet to find a common behavior or consistent > method to reproduce. This doesn't happen on my other serial consoles, > FreeBSD or Linux. I also don't think it happened early on when this > rpi4 was running raspbian for a brief time, but I didn't play with > that setup very long. > > So far I believe it's avoidable by not watching the serial console > during reboot, not necessary (I think) to disconnect the cable. But > obviously that defeats the purpose of the serial console vs. a blind > reboot. Hopefully "not watching" means disconnecting Rx and Tx from the GPIO pins. If it means not looking at the display it's a whole 'nother story! 8-) bob prohaska > > I plan to upgrade my rpi4 to 14.0 just to see if anything changes. Iirc > from the relnotes, one of the changes in new release is 115200 is the > new default for serial communications, and I have some hope that maybe > some hard-to-find hard-coded 9600 may have been thwarting those of us > running with different speed infrastructure and console. > > Since bob is running -current on his rpi3 though, my hope is probably > a longshot. > > Cheers, > sr. > From nobody Tue Nov 28 20:27:20 2023 X-Original-To: freebsd-arm@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4SfvC42xxmz52VsR for ; Tue, 28 Nov 2023 20:27:28 +0000 (UTC) (envelope-from sr@genyosha.net) Received: from ns0.genyosha.net (ns0.genyosha.net [50.39.243.220]) (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 "float.home.genyosha.net", Issuer "float.home.genyosha.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4SfvC40Cz4z4dMt for ; Tue, 28 Nov 2023 20:27:27 +0000 (UTC) (envelope-from sr@genyosha.net) Authentication-Results: mx1.freebsd.org; none Received: from dragon.home.genyosha.net (ops0.genyosha.net [50.39.243.219]) by ns0.genyosha.net (8.17.1/8.17.1) with ESMTPS id 3ASKRQnp007984 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 28 Nov 2023 12:27:26 -0800 (PST) (envelope-from sr@genyosha.net) Received: from dragon.home.genyosha.net (localhost [127.0.0.1]) by dragon.home.genyosha.net (8.14.7/8.14.7) with ESMTP id 3ASKRLx9028094; Tue, 28 Nov 2023 12:27:21 -0800 Received: (from sr@localhost) by dragon.home.genyosha.net (8.14.7/8.14.7/Submit) id 3ASKRKQa028093; Tue, 28 Nov 2023 12:27:20 -0800 Date: Tue, 28 Nov 2023 12:27:20 -0800 From: Steve Rikli To: bob prohaska Cc: freebsd-arm Subject: Re: reboot hesitation on Pi3 running -current Message-ID: References: <4078F04C-B4AA-4029-B260-2A075A8832DA@yahoo.com> List-Id: Porting FreeBSD to ARM processors List-Archive: https://lists.freebsd.org/archives/freebsd-arm List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arm@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Greylist: inspected by milter-greylist-4.6.4 (ns0.genyosha.net [50.39.243.220]); Tue, 28 Nov 2023 12:27:26 -0800 (PST) for IP:'50.39.243.219' DOMAIN:'ops0.genyosha.net' HELO:'dragon.home.genyosha.net' FROM:'sr@genyosha.net' RCPT:'' X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.6.4 (ns0.genyosha.net [50.39.243.220]); Tue, 28 Nov 2023 12:27:26 -0800 (PST) X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:20055, ipnet:50.39.128.0/17, country:US] X-Rspamd-Queue-Id: 4SfvC40Cz4z4dMt On Tue, Nov 28, 2023 at 12:00:08PM -0800, bob prohaska wrote: > On Tue, Nov 28, 2023 at 09:05:59AM -0800, Steve Rikli wrote: > > On Tue, Nov 28, 2023 at 08:15:30AM -0800, bob prohaska wrote: > > > On Tue, Nov 28, 2023 at 07:20:03AM -0800, Mark Millard wrote: > > > > On Nov 28, 2023, at 07:10, bob prohaska wrote: > > > > > > > > > A Pi3 running -current has taken to pausing during a shutdown > > > > > -r in a strange way: It gets to: > > > > > > > > > > Hit [Enter] to boot immediately, or any other key for command > > > > > prompt. Booting [/boot/kernel/kernel] in 5 second more > > > > > detailed help. > > > > > > > > > > It then stops at the OK prompt: > > > > > > > > > > OK boot <---typing boot fails: > > > > > > > > > > unknown command <---this looks strange, the kernel should > > > > > already be loaded > > > > > > > > A possibility here is garbage control characters, say before > > > > the "boot". YOu might want to type just to the first OK > > > > prompt and see if you ever still get "unknown command" once you > > > > do type just "boot" (and ). > > > > > > IIRC I've done that in the past with the same result, but memory > > > is hazy and an attempt at a second shutdown -r came back up > > > without hesitation. > > > > > > Another build/install cycle is running now, I'll be more careful > > > next time. > > > > > > > The fact that the countdown stopped at 5 (or other early value) > > > > suggests such extra text at that point. > > > > > > Rubbish on the serial console is a common occurence, but it usually > > > shows up when the USB end is taken down and brought back up. In this > > > case the USB end remained up throughout the reboot cycle, no stray > > > characters were visible. > > > > This topic has come up before here, I believe. > > > > I can confirm the same or very similar behavior on rpi4, and there's no > > USB-serial to disconnect on the remote end, rather an actual serial > > console server which is always-on. > > That's a significant (I think) observation. I couldn't tell where the > stray characters were originating and suspected the USB-serial > adapter. Your experience suggests very strongly the trouble is local > to the serial UART on the Pi or maybe wiring problems. I tend to agree. No USB-serial adapters involved in my setup. Wrt "wiring problem", fwiw I've tried multiple cables and db9 hoods, with both full-pins and 3-wire, no difference. All work as expected on other systems (NUC, various x86 PC, the occasional network gear etc.). > Is it possible that the serial port of the monitoring devices occasionally > echos output from the Pi's console back to the Pi? Seems to me it shouldn't, > but sometimes I see fragments of a login prompt among the rubbish. I imagine it's possible but I doubt it's happening. I've swapped ports on the serial console server as well JIC, again no change, and no other systems or devices exhibit behavior like this. > > Unfortunately it's not consistent behavior, i.e. sometimes the reboot > > proceeds uninterrupted. Sometimes typing 'boot' proceeds normally, > > sometimes typing 'boot' errors and then typing it again proceeds as > > normal. > > Does it sometimes reboot hands-off? Mine does, at least occasionally. Yes, sorry, that's what I meant by "sometimes reboot proceeds uninterrupted". > > I too have been thinking it's spurious chars on the serial console at > > various points, but I've yet to find a common behavior or consistent > > method to reproduce. This doesn't happen on my other serial consoles, > > FreeBSD or Linux. I also don't think it happened early on when this > > rpi4 was running raspbian for a brief time, but I didn't play with > > that setup very long. > > > > So far I believe it's avoidable by not watching the serial console > > during reboot, not necessary (I think) to disconnect the cable. But > > obviously that defeats the purpose of the serial console vs. a blind > > reboot. > > Hopefully "not watching" means disconnecting Rx and Tx from the GPIO > pins. If it means not looking at the display it's a whole 'nother story! > > 8-) Nothing is ever physically disconnected from the rpi4, if that's what you mean. Fyi my rpi4 serial console is via a "Serial Hat" which ultimately connects the appropriate GPIO pins to a db9 connector accessible outside the case, which is in-turn connected to my serial console server. "Not watching" in this context means I do not have an active connection to the serial console server port which communicates with the rpi4 db9 serial port. Somewhat analagous to not running tip/cu/minicom from your laptop or whatever system you use to connect to the rpi4 GPIO pins. Another note JIC: there are no keyboard, mouse, HDMI, or USB devices connected to any of the rpi4 ports. Only power, the serial console and a network cable. In that regard it is a neat little headless server, but unfortunately I don't really want to use it in production due to this issue. sr. From nobody Tue Nov 28 20:35:34 2023 X-Original-To: freebsd-arm@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4SfvNn11SDz52WYG for ; Tue, 28 Nov 2023 20:35:53 +0000 (UTC) (envelope-from marklmi@yahoo.com) Received: from sonic306-20.consmr.mail.gq1.yahoo.com (sonic306-20.consmr.mail.gq1.yahoo.com [98.137.68.83]) (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) by mx1.freebsd.org (Postfix) with ESMTPS id 4SfvNm5VnTz4fZF for ; Tue, 28 Nov 2023 20:35:52 +0000 (UTC) (envelope-from marklmi@yahoo.com) Authentication-Results: mx1.freebsd.org; none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1701203750; bh=/yiicQUWe26+h7N9czHchFdV+ltybLz7RLWU2Cipcb0=; h=Subject:From:In-Reply-To:Date:Cc:References:To:From:Subject:Reply-To; b=qB6jzSSkDk88SAiJ7y/rf3pi+QC6VfqAEAqnXoOckpNWwxsGA0oAcTHuu1ZHm6OZpmAEo5vSJDK4JXNLmRE0SihWneBP21dHru7/tyTJ6psvtN/TbDt1ad1iKo5L3ejvR7W6mzP//L7wqVkcDA7OAmJweVr4Wg6+jncInt0u3F4LLgqQoS4Nk6MG4nshuEkr3AfGWbtJz1psgkVsl+0EiCpXeFphxGfuHHow3U6pXkkpatfJqg7vFVQqfqSHQMbUVzLabjcgFCtNhDTp40yh9Ye/cUDBlKiYkGEqHDdtlZr1gVuixRypJMUPBKXPv9LNSHHM1Ha3cyLQAoy0V7MaOA== X-SONIC-DKIM-SIGN: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1701203750; bh=VOudaPSts0vHxhkH6zCD7r0R8HFCQZNrr2MuL3cKmiL=; h=X-Sonic-MF:Subject:From:Date:To:From:Subject; b=dQKGuePgG03Nz9oP+DEGGUxJxf8y29i4IvLoOmyhJGe9h1ugfXRX/aCzH5/XxIWtO73FyttRgRQ/qxqQzopXdacZOZesgW9DC4avDAgagbHcHF0IPrrF+J4tBx+QPaNBeoFh+yzKn0ONtiHrsaDj7ZERMT6uVK2mfm5V5cSENe0gH6rHqmbbc8UXzuPDP3FRG9pYADzKgYnQz2mIs0icaYPTZ8mBdTEkUAJYqreg7hHB29cNF/s9glZ5fSYU4UJ9VQ/tnx7RLAKmoCI2EXlEI59xpAFXYUynY1G+jD+j8t6KosYeU0PHz3T9nyMzyEZMD3xqXbXMFnSCOQ2KVdLJBQ== X-YMail-OSG: ItqbxLMVM1nngji.pscmtUWhPZe4JRY7ZRFQUxy0xMbfuKuaK3UpEW9bVK8ZGjQ E8snx9YlEjjsX.5qxuFoG0Fbs4JafqA5Mnf0ZJjoFPsJKKYXZRtKot3SmpCp7DnryuXF_DcpdxwE NZ7mw0kFjuM7CfV8GEW8050aJOpF8G0LmxFTaxAib4i5shXzuEP01pohSC6hBRPXbc7j0QOpCoOZ foO46MRPm0ri7u2aQ6nP6oGeuZJuA8prhu3qpoa4ZEctj5HgH6WJw4gyqZn70I7Mm_Q7dgodeFe. tMO0qkfMSEf.y2Uso9IULV5wy0uJywS2hjSUDHkybDkmfp95zdpHeIB7RmIt2yvdIxeYqNWBMuah MyWO811yEepIrlRWCDiovgExFDZfDJOzUsWXhOaF_cZgCuJweCSQq7WUQgmLfRxOHJj1Ykncw2Mh wQ4w7.PCWJ8HipYedpNkroWja_fvEQVOZUGcQasH4pDGYJh5NtULVHU8PFuH56Uh7GPze2RYENOu 3JeCCGoiRVI.nnQicHxCU3IDn.3qdAhNsdU3qg1MuZ7yvTQqJbzZ8ffARhpDjI7iwhejVNUexKGJ P7PkJ48lNKL9w0wgKpUUTpgQP7Xfwx4SbhPx2y5UyspfEEqoidjW46m32QbpRdLuPLFcxaoXWH1P 8dHPeKn3L353KoajuEqXtIE.sA.XR61Ld9GX9dNDQbaPM5s39lTJaV2krGIcuVkui3e7lFuuFR4P HSGND3jCB1_E.kQ4zIE0ITEdUEcXIUbiRGlG_zy9eJ4W_yxzR9spuO3gm07juq.BRNf80Uk_RB6o laTcpLZEIeoZFrrgbPCz_1dTjNn07BMdpkQ0h.LSlhH8aLJoxViBw8tS9YKCTxyLSommzLVeT9IF kEIE39.Y1zvp7YOhpgx0OKRRj1wcGy7CRylwjL_aypgnTPJTEDo2yyyy9u0TkbaWH0P8viPRUjTe 1IMzO9Q0bZ4nTL7Ndm4YA6gwAkBVg9pgltNMO9UXcY76_TR3UsPIxWSHjMRwnESo3I3hJnDe.Yfn JTCSZobTtPPCwFTohMiEpoVBqQrMlBuXmD3u56tk7wO1SlxABUgEbCWxaCWojcQRKmdhJOWNgH8N Jck2vr4II9LkUBB5SIU80xciyTwiwmiN3Yn62sIPcK6iB.L95Hk4jbcwoXKgHW0U774Mk7Y_uFrL G0.vfqVvOHJbBFf6i3UZdgRUYo9YRFoUnEML0aOKldOVjd7V.IviMMc6WYksBjpy2kshWD3G7rSB WqD.pF.1jyD45eqnAoCfyGwDefUgfO8gZ3YQ899AbxBUS_hQbYKt8M7ZpCMCDK8a21gYy2hhTDXD dvbqOVvfbbgCMI98goq_7cRDjaFoRCgWp.E2dEfb1SEOFIgNa.SzIzqjpFCJQGTFYBrJZUvw9dkd lDncdi8k_R2rcevsSaZlnBD9hd6ouMiOxNN4vC2KqB0wxbNKx1bHjgodGF6MbmyatjnxFn2R7RMF 3UaOCABilKYKJ4wN3GSGokbAIFCWxgmmwPNLc.yrmmayN5irDAovtaymhqEdCPjbPHKIufYOLceP 9AlmY0LBTdrS4K4BdjZgSNx5Anqg308dMHNPxgMGiLIQUrDK0eetNkQKll.nWwQOyAiSINLJOOaX qLD2hx_Wl8S3HxvJcm77WajEutRbQe5Jq8QcErgqXe8B10LcTHcqKLrrvyCvgghgrqMi4bSI8ARH ZtVUlb0IINUIfhdrrPpwCaalZIxM5rdyPFxumxZmEC04.sJ77nks2CsktMxBimqoIGR6g2RmrAEf ItVX6kRhnslusdWVZ2NkGSDV4zmGS1iy.mk8iuuZlDUZUFaKzLJ8DPXLwx7xOAK7Ht9ZmcYPHd5k V9s3niApgH6t19m5QfN0etywODO9kUvnQ7v0Q44GSPKznbvJKL8y_n4Qbzae_zV5qJ9JCbxb_8QE mJ_cPYbWF6UeBFzR9mBgk4_EKubggoeUqocN4q70N1gvzInASsnN2J45GcymH.iH1NBivZ8Xn9Ur i91FGfwRS6VV14uZl0POj.aY6wfMBELthlY73fr5.iJWGUk69Y8d8ulIGJi96AWHBbNRWiQ3_QUb dEwfOFF_vy1WaXuF8EVmEAsl.GnDUjlO7JPaff9ZRAlDs4wWgVJYZ4sfHyGIKne8LvO6rv3PJWwO L5js3i0ZFVVJqc8ASqKIZJ9sSXnKHss3n_upAed6s8AJT1PpgwBBVYb1m3uAXYtzzU4hA.iW1H7p XhnWaR0wbxwaL_fjKzAJ2yaIF64sO..NNsqPhyUphFo.PNXp71s2bzpcbDfmr.mBcybtEAQ9pAEG QH4P9lQLn X-Sonic-MF: X-Sonic-ID: b8f907ca-b8bb-4989-ab27-b6dd50b21a6b Received: from sonic.gate.mail.ne1.yahoo.com by sonic306.consmr.mail.gq1.yahoo.com with HTTP; Tue, 28 Nov 2023 20:35:50 +0000 Received: by hermes--production-gq1-5cf8f76c44-dxf8l (Yahoo Inc. Hermes SMTP Server) with ESMTPA ID 0b98670507f6f262ccbbee2f5f64e005; Tue, 28 Nov 2023 20:35:45 +0000 (UTC) Content-Type: text/plain; charset=us-ascii List-Id: Porting FreeBSD to ARM processors List-Archive: https://lists.freebsd.org/archives/freebsd-arm List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arm@freebsd.org Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.200.91.1.1\)) Subject: Re: reboot hesitation on Pi3 running -current From: Mark Millard In-Reply-To: Date: Tue, 28 Nov 2023 12:35:34 -0800 Cc: freebsd-arm Content-Transfer-Encoding: quoted-printable Message-Id: <301571AE-130B-4BF7-B703-9458CF524F46@yahoo.com> References: <4078F04C-B4AA-4029-B260-2A075A8832DA@yahoo.com> To: Steve Rikli , bob prohaska X-Mailer: Apple Mail (2.3774.200.91.1.1) X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:36647, ipnet:98.137.64.0/20, country:US] X-Rspamd-Queue-Id: 4SfvNm5VnTz4fZF On Nov 28, 2023, at 12:27, Steve Rikli wrote: > On Tue, Nov 28, 2023 at 12:00:08PM -0800, bob prohaska wrote: >> On Tue, Nov 28, 2023 at 09:05:59AM -0800, Steve Rikli wrote: >>> On Tue, Nov 28, 2023 at 08:15:30AM -0800, bob prohaska wrote: >>>> On Tue, Nov 28, 2023 at 07:20:03AM -0800, Mark Millard wrote: >>>>> On Nov 28, 2023, at 07:10, bob prohaska = wrote: >>>>>=20 >>>>>> A Pi3 running -current has taken to pausing during a shutdown >>>>>> -r in a strange way: It gets to:=20 >>>>>>=20 >>>>>> Hit [Enter] to boot immediately, or any other key for command >>>>>> prompt. Booting [/boot/kernel/kernel] in 5 second more >>>>>> detailed help. >>>>>>=20 >>>>>> It then stops at the OK prompt: >>>>>>=20 >>>>>> OK boot <---typing boot fails: >>>>>>=20 >>>>>> unknown command <---this looks strange, the kernel should >>>>>> already be loaded >>>>>=20 >>>>> A possibility here is garbage control characters, say before >>>>> the "boot". YOu might want to type just to the first OK >>>>> prompt and see if you ever still get "unknown command" once you >>>>> do type just "boot" (and ). >>>>=20 >>>> IIRC I've done that in the past with the same result, but memory >>>> is hazy and an attempt at a second shutdown -r came back up >>>> without hesitation. >>>>=20 >>>> Another build/install cycle is running now, I'll be more careful >>>> next time. >>>>=20 >>>>> The fact that the countdown stopped at 5 (or other early value) >>>>> suggests such extra text at that point. >>>>=20 >>>> Rubbish on the serial console is a common occurence, but it usually >>>> shows up when the USB end is taken down and brought back up. In = this >>>> case the USB end remained up throughout the reboot cycle, no stray=20= >>>> characters were visible. >>>=20 >>> This topic has come up before here, I believe. >>>=20 >>> I can confirm the same or very similar behavior on rpi4, and there's = no >>> USB-serial to disconnect on the remote end, rather an actual serial >>> console server which is always-on. >>=20 >> That's a significant (I think) observation. I couldn't tell where the >> stray characters were originating and suspected the USB-serial >> adapter. Your experience suggests very strongly the trouble is local >> to the serial UART on the Pi or maybe wiring problems.=20 >=20 > I tend to agree. No USB-serial adapters involved in my setup. Wrt > "wiring problem", fwiw I've tried multiple cables and db9 hoods, with > both full-pins and 3-wire, no difference. All work as expected on = other > systems (NUC, various x86 PC, the occasional network gear etc.). >=20 >> Is it possible that the serial port of the monitoring devices = occasionally >> echos output from the Pi's console back to the Pi? Seems to me it = shouldn't, >> but sometimes I see fragments of a login prompt among the rubbish.=20 >=20 > I imagine it's possible but I doubt it's happening. I've swapped ports = on > the serial console server as well JIC, again no change, and no other = systems > or devices exhibit behavior like this. >=20 >>> Unfortunately it's not consistent behavior, i.e. sometimes the = reboot >>> proceeds uninterrupted. Sometimes typing 'boot' proceeds normally, >>> sometimes typing 'boot' errors and then typing it again proceeds as >>> normal. >>=20 >> Does it sometimes reboot hands-off? Mine does, at least occasionally. >=20 > Yes, sorry, that's what I meant by "sometimes reboot proceeds = uninterrupted". >=20 >>> I too have been thinking it's spurious chars on the serial console = at >>> various points, but I've yet to find a common behavior or consistent >>> method to reproduce. This doesn't happen on my other serial = consoles, >>> FreeBSD or Linux. I also don't think it happened early on when this >>> rpi4 was running raspbian for a brief time, but I didn't play with >>> that setup very long. >>>=20 >>> So far I believe it's avoidable by not watching the serial console >>> during reboot, not necessary (I think) to disconnect the cable. But >>> obviously that defeats the purpose of the serial console vs. a blind >>> reboot. >>=20 >> Hopefully "not watching" means disconnecting Rx and Tx from the GPIO >> pins. If it means not looking at the display it's a whole 'nother = story! >>=20 >> 8-) >=20 > Nothing is ever physically disconnected from the rpi4, if that's what = you > mean. Fyi my rpi4 serial console is via a "Serial Hat" which = ultimately > connects the appropriate GPIO pins to a db9 connector accessible = outside > the case, which is in-turn connected to my serial console server. >=20 > "Not watching" in this context means I do not have an active = connection > to the serial console server port which communicates with the rpi4 db9 > serial port. >=20 > Somewhat analagous to not running tip/cu/minicom from your laptop or > whatever system you use to connect to the rpi4 GPIO pins. >=20 > Another note JIC: there are no keyboard, mouse, HDMI, or USB devices > connected to any of the rpi4 ports. Only power, the serial console and > a network cable. In that regard it is a neat little headless server, > but unfortunately I don't really want to use it in production due to > this issue. I'm going to remind of the known issue with U-Boot on the RPi*'s sometimes leading to odd serial connection behavior for the transition from U-Boot based UEFI handling the serial connection to the FreeBSD UEFI loader handling it. =3D=3D=3D Mark Millard marklmi at yahoo.com From nobody Tue Nov 28 20:47:53 2023 X-Original-To: freebsd-arm@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4Sfvg00dRyz52XZb for ; Tue, 28 Nov 2023 20:48:12 +0000 (UTC) (envelope-from marklmi@yahoo.com) Received: from sonic308-55.consmr.mail.gq1.yahoo.com (sonic308-55.consmr.mail.gq1.yahoo.com [98.137.68.31]) (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) by mx1.freebsd.org (Postfix) with ESMTPS id 4Sfvfy73v9z3C14 for ; Tue, 28 Nov 2023 20:48:10 +0000 (UTC) (envelope-from marklmi@yahoo.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=yahoo.com header.s=s2048 header.b=KX3FM1j0; spf=pass (mx1.freebsd.org: domain of marklmi@yahoo.com designates 98.137.68.31 as permitted sender) smtp.mailfrom=marklmi@yahoo.com; dmarc=pass (policy=reject) header.from=yahoo.com DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1701204488; bh=1h88Cg4Z/AA9da2EZJ/TSaqC6AKdgPTIzNvQcUQrZvY=; h=Subject:From:In-Reply-To:Date:Cc:References:To:From:Subject:Reply-To; b=KX3FM1j048qYbBzaVwCqEqlLbsfPO7/RZBWT9Jd8Ac1XkyFpa2cRyHkDPWmv9zlyGCAYUSJaqRp7ItXARUxf/ffXBrwiNU/T7WILG5a9OaWkf3ACACQbCuZ8cwa1W1NScWp4IBPYqThEKst9FQPqiPiIWK3ehILZR3PtTT0DuLdllLYIY0CRd//WeFadc39+7fxha4K3PPRqiPu9dAUcVi1Z5fbMujNlkKegwruyMq9/wjFoBYKlj9/IWyztZU1b/ucBHz/zJ12NgfIqGLDui6FYdyRtlmxujhqdEDQ1nIM7Dk1gnCvxyBLD3lpkM4mNx65915aStxYD9Qvrbr25vA== X-SONIC-DKIM-SIGN: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1701204488; bh=h3+ULfJp8bII8AquUlsJPX7NfsBjbeAHynV7kqZ8Wck=; h=X-Sonic-MF:Subject:From:Date:To:From:Subject; b=mei2VA8fjzoHoHcTTJm67AuKp00AsDNrwc0MBNXD9XBuIl3ML0RRTnmf5FI4qXcPGBNKo7/waA3IUj3/IBsdXeO0HcWWEbNniM5E1++ymWi9vRct0Dg3mT2k04K3aVuAjgJVyCxeOVkLjOxxXhkYIPT5TRWeM1ZhnmWEXSSEjymBjOceQPgXVBj78U3MNRUmT04OC1xMfKbLgSui6Qd2Vs4UDpoffYNJd+JidxBPUtlVvKI4er9WvSA5vVElJYWhqwHwv0RTGyqDgVQ2V1vC/EAZp5kBDFqUicaRbsgd3AhUx0Y4eRRxpxH1RZSx1DsKqSsGFhveUnQ7lXz/e/7u2Q== X-YMail-OSG: Z1QjWqwVM1msHPiXr2NzpGuMladE4i_ugh1bhqwPz7nYmd4Ic0eRuoEU4k9b4cL gERjlBFxUBATzAEX3Lka0YeP4EWJhP5vkiYtYnVflqnGF4rZao6RokrTnfNJuNd4hEmpLCCTFBVd GUg0_3.sEmPKlZYUJiFiHI3Z8tBL_1DfdUtfzXMPKqI6m3CHsbw0qvQNZygGa9K_XTGmu9Ktosov PPFKPelCd4xg18QUgraJ.VbTqA_z.0bFx8jEAejPalEGp9KGv6XRa8xTPabqr0BnfcCOFWS0.PpQ TI6TbEwwkr9UYrXO8xklp1ac2ps_GWorCnH9KIyOSymvSCddNPQXk1Suk1y3yWO6dc95q_0CWI_n 2B_BKb5TOBekjRwoT86WxsU3X1CzWKHvojndVDUSxS6GFeNTNKzS4IHL_bNN.F6vbKUa4GWIiWzq _qHLAJEJSMax4QXsUEO3oz.B5pmwVPMdMyg80_FQgJdv9SrLOrsSka93hZujoTbYsYaAq04x37oM 8THiwB2U78.NwR4z2pvJczOMDd4cxMXqnS_VKC29tuzk8Ypk1N6WWvPZ9NLnHxe2LIOOJNrAIyyz ZRlScwU8dxdWgeK_UNakO3JiZCaQYkz5FwoZ0_6Vvoz1ui42veV49srHkxLDxxQYaXJ.nOgHFIKc ZPzDht43W3bn8kHNzVUVRRaohyvTNSFIOMXsUONbDQrhb8IP.XhYH8IMqSw10nk.fvASrkuPY6b3 MTm3BcTfaNGhhgzAG4L8cixABfuxJSX1X0iPy7c5vmLddcGRi5pgprLiy7Q99hZugHnxSJfiuV0H Pnfnw5tL2XDhzOmwDfgQ4gTvycQZ1Vb9n0jioygnzbjAj2H1Im5y7.915dYQXmuceWd46Q4Jek4b PkVdDQfKqMNvV.jbTcf.1kzG0_JpJ_KdjBOsrcj6JpLA90.8VsgkrI7LGq5fTjDFBKA3t1TWX54r rT_M.tlxg6CrFjdMAWg6UeDgcXcW5R4lWl1VGfgEn8CFjAftagSDEBcO2x_DhzThEPwm_Ve2y3SE IVilmJ_jJiRNhGWsSjJNu4o5XSQZ5UsEL_SQqYL3PBq_CB.9zv1leHUKYLpY.zA17P2Psk3YtUtc HsOUuQdB7Qp6ML2.wIDi2i2yCEaxXaaJBriMMyIBbZtqyHssqeh7SM2mG.hJf0AHXnnjb0ZHqSAD UIisk9PLDB1BJ6SsWZhe4_szMv_W9mtLJAJpCofR0HJD.9_YEU3Xj0PJDRpeXAm3Xky8ZwoWf14Q VvIKXOhJyEPz_NQzL5a1DPPxLLILAsz_wSaYDhE42sTPREAsbBCaeRNge6lQZImq9jLqjRLvV8vq plx3fA3Fl7xgPzZ64ByrFwnFddl3em8NhWG5XZoauNVWgL0cus.pJI2fl7R5jSKgWE8Y0G6o_lw1 iHKHl5SxnXcE0bt_TiIQSlxVaXKt9z.5_rhyXLS0rCPRwm3w3uKIht1gDeHYUoDWW.eyubqjg5Nw AEdUM7eE1.WTneaHZLKjBPUCtiXBazRIu0XnsGSn4fZNW6RMQ0IoSsd4.jG0d3PT5AGP.hOjUw5D vttrdSQWZHGsUfnKws8Muzkk.vTmHDCZzsmTL8nmA8fyVFLQaIIWKNP9p1Dnw8cMZe68Jov7dk04 1v3TJ1zJ.7fkmw12pE8n.svI49GmgxfD1q0hqw6BxHD3iQZzfnCsUDyRVyvBVnVrt596FNZBGld. j8EM9.eh3he2Faabyqs9heVdJgPJGFmO9vKCUsJakRqNKv1zyU5SiAURi_aIUs6Z3HhdoWHZjsiP GM7Y6Q3fdx43IA1OiR48Fc3WNtOTMOChY1pCffVnQiWv3gdc26lwp89HrFithkqSCWM8c2Cdmum9 hbb_7uVZPg0LDf_Jwy7j.dovQ1fzmayvk4Yq_uaMQ.g_AsBj9YCJiJrUtDCaRPvG6VUf39BIU4mH M2YNEYj34FGOnfCop5UBMpxhibOn5E0Xv4fPHEkrgE6Hn0oBNrqBNGkcBawrsubJnMSis256PnV6 .QYp5eLBoIEM5MO8Duso0DTu6_ZvE4.DMnFmpK3pVtlmsLkW4oMeT5wu_enoGR9dAxNraKcwpTRF _1kSM0KsLfK3Nk2w2jAz88Cvq7lZF7c9EiCKDgGUorTNFlVrfUw3bz3TjCfBnAIVxrysziSk14Z3 na5Gr1UnpsCq46mZvwWBs0JHzHm56i4CTFm6wos28h40C7gxgjGwyx6kodmHxNkVH9_qteVR0zIj 1YmSPTTp6sJ0Kz3ntRLJcEP7Ew_5BFM_.SId2pKX_KQBRSf2.SPD0W6tg41k_ACTrS_.rq9sikk7 Ea4ajjBLXPB0- X-Sonic-MF: X-Sonic-ID: 1f329027-b970-42dc-9318-8f42a4f3e0c0 Received: from sonic.gate.mail.ne1.yahoo.com by sonic308.consmr.mail.gq1.yahoo.com with HTTP; Tue, 28 Nov 2023 20:48:08 +0000 Received: by hermes--production-gq1-5cf8f76c44-dxf8l (Yahoo Inc. Hermes SMTP Server) with ESMTPA ID 70da7e043b12d8ab1225eda66812be01; Tue, 28 Nov 2023 20:48:04 +0000 (UTC) Content-Type: text/plain; charset=us-ascii List-Id: Porting FreeBSD to ARM processors List-Archive: https://lists.freebsd.org/archives/freebsd-arm List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arm@freebsd.org Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.200.91.1.1\)) Subject: Re: reboot hesitation on Pi3 running -current From: Mark Millard In-Reply-To: <301571AE-130B-4BF7-B703-9458CF524F46@yahoo.com> Date: Tue, 28 Nov 2023 12:47:53 -0800 Cc: freebsd-arm Content-Transfer-Encoding: quoted-printable Message-Id: <9E47467E-4147-4E08-899A-94D59A1A75F6@yahoo.com> References: <4078F04C-B4AA-4029-B260-2A075A8832DA@yahoo.com> <301571AE-130B-4BF7-B703-9458CF524F46@yahoo.com> To: Steve Rikli , bob prohaska X-Mailer: Apple Mail (2.3774.200.91.1.1) X-Spamd-Result: default: False [-1.31 / 15.00]; NEURAL_HAM_SHORT(-0.98)[-0.980]; NEURAL_SPAM_LONG(0.80)[0.803]; NEURAL_HAM_MEDIUM(-0.63)[-0.634]; DMARC_POLICY_ALLOW(-0.50)[yahoo.com,reject]; MV_CASE(0.50)[]; R_DKIM_ALLOW(-0.20)[yahoo.com:s=s2048]; R_SPF_ALLOW(-0.20)[+ptr:yahoo.com]; MIME_GOOD(-0.10)[text/plain]; RCPT_COUNT_THREE(0.00)[3]; FROM_HAS_DN(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[98.137.68.31:from]; TO_MATCH_ENVRCPT_SOME(0.00)[]; MLMMJ_DEST(0.00)[freebsd-arm@freebsd.org]; ARC_NA(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; RWL_MAILSPIKE_POSSIBLE(0.00)[98.137.68.31:from]; DKIM_TRACE(0.00)[yahoo.com:+]; TO_DN_ALL(0.00)[]; FREEMAIL_FROM(0.00)[yahoo.com]; DWL_DNSWL_NONE(0.00)[yahoo.com:dkim]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:36647, ipnet:98.137.64.0/20, country:US]; FREEMAIL_ENVFROM(0.00)[yahoo.com]; RCVD_COUNT_TWO(0.00)[2] X-Rspamd-Queue-Id: 4Sfvfy73v9z3C14 X-Spamd-Bar: - On Nov 28, 2023, at 12:35, Mark Millard wrote: > On Nov 28, 2023, at 12:27, Steve Rikli wrote: >=20 >> On Tue, Nov 28, 2023 at 12:00:08PM -0800, bob prohaska wrote: >>> On Tue, Nov 28, 2023 at 09:05:59AM -0800, Steve Rikli wrote: >>>> On Tue, Nov 28, 2023 at 08:15:30AM -0800, bob prohaska wrote: >>>>> On Tue, Nov 28, 2023 at 07:20:03AM -0800, Mark Millard wrote: >>>>>> On Nov 28, 2023, at 07:10, bob prohaska = wrote: >>>>>>=20 >>>>>>> A Pi3 running -current has taken to pausing during a shutdown >>>>>>> -r in a strange way: It gets to:=20 >>>>>>>=20 >>>>>>> Hit [Enter] to boot immediately, or any other key for command >>>>>>> prompt. Booting [/boot/kernel/kernel] in 5 second more >>>>>>> detailed help. >>>>>>>=20 >>>>>>> It then stops at the OK prompt: >>>>>>>=20 >>>>>>> OK boot <---typing boot fails: >>>>>>>=20 >>>>>>> unknown command <---this looks strange, the kernel should >>>>>>> already be loaded >>>>>>=20 >>>>>> A possibility here is garbage control characters, say before >>>>>> the "boot". YOu might want to type just to the first OK >>>>>> prompt and see if you ever still get "unknown command" once you >>>>>> do type just "boot" (and ). >>>>>=20 >>>>> IIRC I've done that in the past with the same result, but memory >>>>> is hazy and an attempt at a second shutdown -r came back up >>>>> without hesitation. >>>>>=20 >>>>> Another build/install cycle is running now, I'll be more careful >>>>> next time. >>>>>=20 >>>>>> The fact that the countdown stopped at 5 (or other early value) >>>>>> suggests such extra text at that point. >>>>>=20 >>>>> Rubbish on the serial console is a common occurence, but it = usually >>>>> shows up when the USB end is taken down and brought back up. In = this >>>>> case the USB end remained up throughout the reboot cycle, no stray=20= >>>>> characters were visible. >>>>=20 >>>> This topic has come up before here, I believe. >>>>=20 >>>> I can confirm the same or very similar behavior on rpi4, and = there's no >>>> USB-serial to disconnect on the remote end, rather an actual serial >>>> console server which is always-on. >>>=20 >>> That's a significant (I think) observation. I couldn't tell where = the >>> stray characters were originating and suspected the USB-serial >>> adapter. Your experience suggests very strongly the trouble is local >>> to the serial UART on the Pi or maybe wiring problems.=20 >>=20 >> I tend to agree. No USB-serial adapters involved in my setup. Wrt >> "wiring problem", fwiw I've tried multiple cables and db9 hoods, with >> both full-pins and 3-wire, no difference. All work as expected on = other >> systems (NUC, various x86 PC, the occasional network gear etc.). >>=20 >>> Is it possible that the serial port of the monitoring devices = occasionally >>> echos output from the Pi's console back to the Pi? Seems to me it = shouldn't, >>> but sometimes I see fragments of a login prompt among the rubbish.=20= >>=20 >> I imagine it's possible but I doubt it's happening. I've swapped = ports on >> the serial console server as well JIC, again no change, and no other = systems >> or devices exhibit behavior like this. >>=20 >>>> Unfortunately it's not consistent behavior, i.e. sometimes the = reboot >>>> proceeds uninterrupted. Sometimes typing 'boot' proceeds normally, >>>> sometimes typing 'boot' errors and then typing it again proceeds as >>>> normal. >>>=20 >>> Does it sometimes reboot hands-off? Mine does, at least = occasionally. >>=20 >> Yes, sorry, that's what I meant by "sometimes reboot proceeds = uninterrupted". >>=20 >>>> I too have been thinking it's spurious chars on the serial console = at >>>> various points, but I've yet to find a common behavior or = consistent >>>> method to reproduce. This doesn't happen on my other serial = consoles, >>>> FreeBSD or Linux. I also don't think it happened early on when this >>>> rpi4 was running raspbian for a brief time, but I didn't play with >>>> that setup very long. >>>>=20 >>>> So far I believe it's avoidable by not watching the serial console >>>> during reboot, not necessary (I think) to disconnect the cable. But >>>> obviously that defeats the purpose of the serial console vs. a = blind >>>> reboot. >>>=20 >>> Hopefully "not watching" means disconnecting Rx and Tx from the GPIO >>> pins. If it means not looking at the display it's a whole 'nother = story! >>>=20 >>> 8-) >>=20 >> Nothing is ever physically disconnected from the rpi4, if that's what = you >> mean. Fyi my rpi4 serial console is via a "Serial Hat" which = ultimately >> connects the appropriate GPIO pins to a db9 connector accessible = outside >> the case, which is in-turn connected to my serial console server. >>=20 >> "Not watching" in this context means I do not have an active = connection >> to the serial console server port which communicates with the rpi4 = db9 >> serial port. >>=20 >> Somewhat analagous to not running tip/cu/minicom from your laptop or >> whatever system you use to connect to the rpi4 GPIO pins. >>=20 >> Another note JIC: there are no keyboard, mouse, HDMI, or USB devices >> connected to any of the rpi4 ports. Only power, the serial console = and >> a network cable. In that regard it is a neat little headless server, >> but unfortunately I don't really want to use it in production due to >> this issue. >=20 > I'm going to remind of the known issue with U-Boot on the RPi*'s > sometimes leading to odd serial connection behavior for the > transition from U-Boot based UEFI handling the serial connection > to the FreeBSD UEFI loader handling it. >=20 I found some of the old text that referenced one of the examples of a U-Boot -> Loader text oddity. Here it the 2023-mid-April text: QUOTE But I can report that the prior [6n (Query Cursor Position) before the FreeBSD loader's OK prompt is during U-Boot activity: part of the escpe sequences just after: Device 0: Vendor: OWC Rev: 0 Prod: Envoy Pro mini =20 Type: Hard Disk Capacity: 228936.5 MB =3D 223.5 GB (468862128 x 512) ... is now current device Scanning usb 0:1... This suggests that U-Boot failed to read/clear some of the Report Cursor Position text --and that the loader accepts what it finds already present (probably so that typing ahead of time would work). So: Looks to me like a probable U-Boot issue for which a FreeBSD workaround to ignore text would have other consequences (lack of effective typeahead for the loader prompt). END QUOTE =3D=3D=3D Mark Millard marklmi at yahoo.com From nobody Wed Nov 29 21:00:06 2023 X-Original-To: freebsd-arm@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4SgWtW3HTvz52FYr for ; Wed, 29 Nov 2023 21:00:19 +0000 (UTC) (envelope-from jcb2023az@gmail.com) Received: from mail-pl1-x62c.google.com (mail-pl1-x62c.google.com [IPv6:2607:f8b0:4864:20::62c]) (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 4SgWtV1hPJz4gP6 for ; Wed, 29 Nov 2023 21:00:18 +0000 (UTC) (envelope-from jcb2023az@gmail.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20230601 header.b=bfDRdF9h; spf=pass (mx1.freebsd.org: domain of jcb2023az@gmail.com designates 2607:f8b0:4864:20::62c as permitted sender) smtp.mailfrom=jcb2023az@gmail.com; dmarc=pass (policy=none) header.from=gmail.com Received: by mail-pl1-x62c.google.com with SMTP id d9443c01a7336-1cfb2176150so2207785ad.3 for ; Wed, 29 Nov 2023 13:00:18 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1701291616; x=1701896416; darn=freebsd.org; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:from:to:cc:subject:date:message-id:reply-to; bh=/mukOGlxC3LYxJuG6/I12QTS5P0os7+j3WhPqo2W/Rw=; b=bfDRdF9h68opCA5toqLvtvvJfHLIzaQ/J7lV/K4nh/h2gfcIY2H87zwQGVdroOxZUe AYg8hDTcnvh73SeKy+GOZtt+r0eGFlCte07jfuYNDmzlC0/Ht4JBUGMQUfucBQNThIjE 0b8zLxx1JLFgVrcd/XTxAp9aClmMjHDYdyOIBy19dSwSkc1UWc+EDVpplsNL3FqUDrND ZZF/eUE2uxsN0uNGLN561h+ARn5Nazz/+B1bf2hIge9ZvNxyZcEHE37y8+yaQO5qzam8 iaZZjWDx7seLu9ddU4XvKn4IXmu50//qSXT4hXlOBuoNmdm/n4CkwsjIeBvOWja+5Bnr Ro4g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1701291616; x=1701896416; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=/mukOGlxC3LYxJuG6/I12QTS5P0os7+j3WhPqo2W/Rw=; b=PYO38nmKlehMtk5ZrjhhbuCrO974LcatE+FfY3nuUZ26Ua3H+Crmqzsk5hz2dFEvPH K4wmPuF5Y99HeaDGH70+swRPG7e1mwUNco80qOoRuIwikT09ox8ONdWURSTfX1BsOR1K xZAE8SY3q6uWDUUTRrDRa1yMPPgoAxpKItoqyuZ8HjLnG1gaZnuWUikq+zAlwp/3cOLb mAcpJYB3m3rrzqcv940r5OAf1SW8W6JdgvR77H2TgjfcGJLF8RpnMBJYFCGKDWC538Xg mX/sdx7sStKPCGp/i6rB9oTao6F8rgHUEN9r6GXfNb5ArOBRGJEuCqiq3ZIQg+rcB0hA T86w== X-Gm-Message-State: AOJu0YxLwxlgGSHUx/tE1R+WqN/Jsje5/wvSffmPjsK9HBfTX80trqw3 jCSCAMorrCHqwB2KP0yIL2s= X-Google-Smtp-Source: AGHT+IH7MuDRxbNVEBwxN9CEzCwI1kOaq+8rV5NPanDFX21g/Ff5OS2z1I0AeFtdEHRkIyc1C3cj1w== X-Received: by 2002:a17:902:c94c:b0:1cf:b130:e9ae with SMTP id i12-20020a170902c94c00b001cfb130e9aemr19891529pla.62.1701291616450; Wed, 29 Nov 2023 13:00:16 -0800 (PST) Received: from freebsd2 (c-73-116-164-136.hsd1.ca.comcast.net. [73.116.164.136]) by smtp.gmail.com with ESMTPSA id u11-20020a170902e80b00b001bf11cf2e21sm12610752plg.210.2023.11.29.13.00.15 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 29 Nov 2023 13:00:16 -0800 (PST) Date: Wed, 29 Nov 2023 13:00:06 -0800 From: Joe B To: Jason Bacon Cc: freebsd-arm@freebsd.org Subject: Re: Freebsd on M1 Macs Message-ID: References: <7a13c63d-a50b-429c-a481-0693e9faaf6b@gmail.com> <1536d845-9073-4f9b-96f6-fa9647536c00@gmail.com> List-Id: Porting FreeBSD to ARM processors List-Archive: https://lists.freebsd.org/archives/freebsd-arm List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arm@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Disposition: inline In-Reply-To: <1536d845-9073-4f9b-96f6-fa9647536c00@gmail.com> X-Spamd-Result: default: False [-3.50 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-1.000]; MID_RHS_NOT_FQDN(0.50)[]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20230601]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36]; MIME_GOOD(-0.10)[text/plain]; FROM_HAS_DN(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-arm@freebsd.org]; MLMMJ_DEST(0.00)[freebsd-arm@freebsd.org]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::62c:from]; ARC_NA(0.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; FREEMAIL_ENVFROM(0.00)[gmail.com]; DKIM_TRACE(0.00)[gmail.com:+]; FREEMAIL_FROM(0.00)[gmail.com]; TO_DN_SOME(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim]; RCPT_COUNT_TWO(0.00)[2]; FROM_EQ_ENVFROM(0.00)[]; FREEMAIL_TO(0.00)[gmail.com]; MIME_TRACE(0.00)[0:+]; RCVD_TLS_LAST(0.00)[]; RCVD_COUNT_TWO(0.00)[2] X-Rspamd-Queue-Id: 4SgWtV1hPJz4gP6 X-Spamd-Bar: --- On 26.11.2023 16:04, Jason Bacon wrote: >On 11/26/23 13:22, Joe B wrote: >> >>I know this is a longshot but I'm going to ask I know MacOS is a BSD >>but we all know it's very sugarcoated and doesn't look like a BSD. >> >>Question will real freeBSD ever come to the m1 Mac's. I got a 16 >>inch mbp with good specs just taking up space right now >> >>Thanks >> >>~ Joe B > >I assume you've seen https://wiki.freebsd.org/AppleSilicon. Not sure >how up-to-date it is. The wikis tend to lag behind reality in my >experience. > >I have run FreeBSD under UTM (Qemu with a GUI). It worked OK, but I >wasn't able to get better than 800x600 graphics, and it seemed to >cause the host macOS to drop network connections. Sorry for not getting back right away been really busy with holidays etc.. Yea the wiki is very far behind. I think they are talking about intel Macs and not m1's or m2's I'll wait, enjoying freebsd on a regular intel laptop Thanks ~ Joe B