From owner-freebsd-arm@freebsd.org Mon May 11 22:41:39 2020 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 670702D929D for ; Mon, 11 May 2020 22:41:39 +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) server-signature RSA-PSS (4096 bits) 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 49LbX204Nrz4KYS for ; Mon, 11 May 2020 22:41:37 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (localhost [127.0.0.1]) by www.zefox.net (8.15.2/8.15.2) with ESMTPS id 04BMfVho041343 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Mon, 11 May 2020 15:41:31 -0700 (PDT) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.15.2/8.15.2/Submit) id 04BMfUom041342; Mon, 11 May 2020 15:41:30 -0700 (PDT) (envelope-from fbsd) Date: Mon, 11 May 2020 15:41:30 -0700 From: bob prohaska To: Mark Millard Cc: freebsd-arm@freebsd.org, bob prohaska Subject: Re: Curious buildworld stoppage on RPi3B running 12.1-stable. Message-ID: <20200511224130.GA41230@www.zefox.net> References: <20200508180252.GA29832@www.zefox.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Rspamd-Queue-Id: 49LbX204Nrz4KYS X-Spamd-Bar: ++ Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=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 X-Spamd-Result: default: False [2.14 / 15.00]; ARC_NA(0.00)[]; WWW_DOT_DOMAIN(0.50)[]; RCVD_TLS_ALL(0.00)[]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; TO_DN_SOME(0.00)[]; IP_SCORE(0.05)[ip: (0.21), ipnet: 50.1.16.0/20(0.11), asn: 7065(-0.03), country: US(-0.05)]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[zefox.net]; AUTH_NA(1.00)[]; NEURAL_SPAM_MEDIUM(0.27)[0.268,0]; NEURAL_HAM_LONG(-0.08)[-0.081,0]; TO_MATCH_ENVRCPT_SOME(0.00)[]; R_SPF_NA(0.00)[]; FREEMAIL_TO(0.00)[yahoo.com]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:7065, ipnet:50.1.16.0/20, country:US]; MID_RHS_MATCH_FROM(0.00)[]; MID_RHS_WWW(0.50)[]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 May 2020 22:41:39 -0000 On Fri, May 08, 2020 at 03:08:54PM -0700, Mark Millard wrote: > On 2020-May-8, at 11:02, bob prohaska wrote: > > > Here's an example of a curious hang on a Pi3 during -j4 buildworld. > > The machine uses a 37GB mechanical USB disk running 12.1 r360689. > > > > /boot/loader.conf contains > > kern.cam.boot_delay="20000" > > vm.pageout_oom_seq="4096" > > vm.pfault_oom_attempts="-1" > > Two attempts to reproduce the buildworld hang on successive revisions of 12.1 (now at r360872) failed. Buildworld ran to completion in about 27 hours, which is about as fast as it ever ran, at least since the introduction of clang 9. The compile did dwindle to a single thread, but the thread continued to make progress and eventually four threads replaced it. Swap activity looked different, remaining high (~1GB) until buildworld completed. Formerly swap use became insignificant once the "building libraries" stage was over. The "swap_pager_getswapspace(24): failed" messages were still seen, but they stopped relatively early in buildworld. Near as I can tell they're innocuous, even if they look threatening. The tempest is back in the teapot 8-) > > Top reports: > > > > last pid: 84778; load averages: 0.00, 0.47, 1.35 up 0+19:11:52 09:43:58 > > 55 processes: 1 running, 54 sleeping > > CPU: 0.0% user, 0.0% nice, 0.7% system, 0.0% interrupt, 99.3% idle > > Mem: 243M Active, 26M Inact, 13M Laundry, 171M Wired, 98M Buf, 453M Free > > Swap: 2263M Total, 698M Used, 1565M Free, 30% Inuse, 696K In > > 453 MiByte Free, 698MiByte Swap/paging space used, and, see > below, 263 MiByte RESident for c++ --on a machine with 1 GiByte > of RAM with 171 MiByte Wired. The c++ RESident is 20 MiByte or > so more than the 243 MiByte Active figure. > > > PID USERNAME THR PRI NICE SIZE RES STATE C TIME WCPU COMMAND > > 82615 root 1 20 0 726M 263M swread 3 8:43 0.46% c++ > > 1025 bob 1 20 0 13M 1052K CPU0 0 2:47 0.16% top > > 1020 bob 1 20 0 19M 800K select 1 0:18 0.02% sshd > > 66244 root 1 20 0 11M 228K select 0 0:03 0.00% make > > 656 root 1 20 0 10M 244K select 0 0:00 0.00% devd > > 82405 root 1 20 0 17M 2460K select 0 0:25 0.00% make > > 27467 root 1 20 0 10M 228K select 0 0:11 0.00% make > > 27499 root 1 20 0 11M 232K select 0 0:07 0.00% make > > 40948 root 1 20 0 11M 228K select 0 0:06 0.00% make > > 928 root 1 20 0 16M 1004K select 0 0:05 0.00% sendmail > > 66255 root 1 20 0 14M 236K select 1 0:04 0.00% make > > 73291 root 1 20 0 10M 224K select 1 0:02 0.00% make > > 932 root 1 20 0 11M 340K nanslp 3 0:01 0.00% cron > > 727 root 1 20 0 11M 664K select 3 0:01 0.00% syslogd > > > > The buildworld output log file has stopped updating: > > > > -rw-r--r-- 1 root wheel 18178806 May 8 06:34 buildworld.log > > bob@nemesis:/usr/src % ls -l *.log > > -rw-r--r-- 1 root wheel 18345625 May 8 08:17 buildworld.log > > bob@nemesis:/usr/src % ls -l *.log > > -rw-r--r-- 1 root wheel 18532738 May 8 09:34 buildworld.log > > bob@nemesis:/usr/src % ls -l *.log > > -rw-r--r-- 1 root wheel 18532738 May 8 09:34 buildworld.log > > bob@nemesis:/usr/src % ls -l *.log > > -rw-r--r-- 1 root wheel 18532738 May 8 09:34 buildworld.log > > bob@nemesis:/usr/src % ls -l *.log > > -rw-r--r-- 1 root wheel 18532738 May 8 09:34 buildworld.log > > bob@nemesis:/usr/src % > > At this point clock time is 09:46, so it's been stuck 8 minutes. > > See later below about how long loading from swap/paging > space might be taking based on the below gstat information > and the earlier top information. > > > Gstat reports > > dT: 1.010s w: 1.000s > > L(q) ops/s r/s kBps ms/r w/s kBps ms/w %busy Name > > 0 0 0 0 0.0 0 0 0.0 0.0| mmcsd0 > > 1 80 80 321 12.4 0 0 0.0 99.4| da0 > > 0 0 0 0 0.0 0 0 0.0 0.0| mmcsd0s1 > > 0 0 0 0 0.0 0 0 0.0 0.0| mmcsd0s2 > > 0 0 0 0 0.0 0 0 0.0 0.0| diskid/DISK-9B9A5304 > > 0 0 0 0 0.0 0 0 0.0 0.0| msdosfs/MSDOSBOOT > > 0 0 0 0 0.0 0 0 0.0 0.0| mmcsd0s2a > > 0 0 0 0 0.0 0 0 0.0 0.0| mmcsd0s2b > > 0 0 0 0 0.0 0 0 0.0 0.0| diskid/DISK-9B9A5304s1 > > 0 0 0 0 0.0 0 0 0.0 0.0| diskid/DISK-9B9A5304s2 > > 0 0 0 0 0.0 0 0 0.0 0.0| ufsid/5bbd5a23da8b6195 > > 0 0 0 0 0.0 0 0 0.0 0.0| ufs/rootfs > > 0 0 0 0 0.0 0 0 0.0 0.0| diskid/DISK-9B9A5304s2a > > 0 0 0 0 0.0 0 0 0.0 0.0| diskid/DISK-9B9A5304s2b > > 0 0 0 0 0.0 0 0 0.0 0.0| da0s1 > > 1 80 80 321 12.4 0 0 0.0 99.5| da0s2 > > 0 0 0 0 0.0 0 0 0.0 0.0| da0s2a > > 1 80 80 321 12.4 0 0 0.0 99.5| da0s2b > > bob@nemesis:~ % > > Note the lack of write activity and top also is reported > showing: swread . Sort of like it is mostly doing a large > reload of something that had been mostly paged out earlier. > I was struck by the lack of any activity to da0s2a. The machine wasn't waiting for anything _except_ swap. > This is combined with that top output showing: 453M Free . > Was there a time earlier with far less free? > Yes, swapping had commenced hours earlier. > Also: top only shows one c++ to match up with your -j4 . This > suggests possibly a period of time when other things have not > started, pending needing what that c++ is building. Or it just > finished a parallel job but has not yet started another. > Somewhat earlier there might have been more than one thing > active. > Four threads started, gradually dwindling to a single thread by the time I noticed. After disturbing the machine by starting the gstat script the remaining thread became more active and eventually was joined by additional threads. > Can you find out what the c++ is compiling during this period? It was part of llvm, though I neglected to record what. I planned to observe more carefully on a second experiment, but failed. > that might allow figuring out if it is something that normally > sends some time has the only job despite -j4 . > > > It looks as if the swap device is saturated, but swap is not exhausted. > > You later mention swap_pager_getswapspace errors, leading to the > question if there was a period when swap (or its supporting RAM > data structure space) had been exhausted. Were those the only > messages in such earlier time frames? > Yes, they appeared in a flurry in the first half (timewise) of buildworld. Then no further console output. > As for being "saturated": > > At 321 KB/s (the example in the gstat output), if it was loading > something large, such as 512 MiBytes, just basically reading that > much material at a mean of such a rate would be over 25 minutes: > > 512*1024*1024_bytes * (1sec/(321*1024_bytes)) * (1minute/(60sec)) > > (Not that I know the 512 MiByte is realistic or that the 321 > KiBYtes/sec is a realistic mean rate.) This just gives an idea > what might be involved and that being beyond seconds or even a > small number of minutes for the general time scale may well be > possible. > > Extensive paging/swapping can vastly slow things down. > That is a startling realization. > > The machine isn't hung; ssh sessions are responsive, the serial console > > refreshes the login prompt when the Enter key is hit. > > > > Also, there are no _current_ errors on the serial console. However, there > > a quite a number of swap_pager_getswapspace(32): failed messages, which > > stopped some considerable time earlier. Buildworld didn't seem affected by them. > > I'm not sure what can be said about the status of the machine > after swap_pager_getswapspace failures are reported that do not > have matching OOM kills involved. It may be that pages stayed > resident that otherwise would have paged out and that other > tradeoffs lead to slow-downs compared to having been able to > free some RAM for other uses. (No deadlock happened, however.) > > My expectation here is that you did run out of free swap/paging > space space for a while. (It may be that internal data structures > for managing swap/paging space use are the limit hit, instead of > disk space, for all I know.) You did not indicate how big the > swap/paging partition is. > It's 2263M. > You did not mention if booting is suggesting kern.maxswzone > adjustments --or if you have done something to control that > context to not use the default. > No gripes from the kernel. > > Perhaps strangest of all, starting up a gstat script to log system > > activity seems to slowly revive buildworld. %idle gradually drops to > > a few percent. > > Did you look to see if it was still just the one c++ process (PID > 82615) for the -j4 ? > Once PID 82615 got back near 100% it was joined by others. > Other things may also have changed, not just you starting a gstat > script. This sort of judgement requires examining/monitoring the > context for a time. > > > If the gstat script is started before buildworld > > the stall doesn't seem to happen and buildworld finishes in about 27 > > hours, which is as good as it gets. > > Are all the comparisons of from-scratch buildworld buildkernel > activity and otherwise controlled to be very similar contexts? > The experiments start with a cleanupscript: make -j8 cleandir > cleandir.log && make -j8 cleandir > cleandir.log && rm -rf /usr/obj/usr/ && rm *.log (probably redundant, kept out of habit) Then a buildscript make -j4 -DNO_CLEAN buildworld > buildworld.log && make -j4 buildkernel > buildkernel.log Finally, the installscript: make -j4 installworld > installworld.log && make -j4 installkernel > installkernel.log > > Earlier tests letting the machine run undisturbed without the gastat > > script running suggests it'll eventually finish buildworld in around > > 36 hours. > > Also has the question of how well guaranteed is the > degree of similarity for the compared contexts? > > > This vaguely echoes an incident long ago where Xorg was unusably slow > > until a small job was started in the background, at which point it > > became responsive. Can't readily imagine a connection, though. > > Definitely changes what the scheduler has to do. That likely has > other non-obvious consequences when pushing the system near its > limits. > > > It's rather counterintituve that giving the machine more work to do > > should make it work faster....If anybody can suggest what's going > > on I'd most curious. I could try poking around in the debugger if > > someone can offer guidance. On my own I'm clueless. > > === > Mark Millard Thanks to all (especially Mark) who read this far! bob prohaska From owner-freebsd-arm@freebsd.org Mon May 11 23:34:33 2020 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id BD4AD2DAD5A for ; Mon, 11 May 2020 23:34:33 +0000 (UTC) (envelope-from marklmi@yahoo.com) Received: from sonic313-20.consmr.mail.gq1.yahoo.com (sonic313-20.consmr.mail.gq1.yahoo.com [98.137.65.83]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 49Lcj427SFz4P6D for ; Mon, 11 May 2020 23:34:32 +0000 (UTC) (envelope-from marklmi@yahoo.com) X-YMail-OSG: bCLKlN4VM1kX4cyFkFWpJbyW4SfZ9zrmIslDLfhtUhEuZP8yW67zhqM1Sqvcqx. gMraj4edrS5oex_yCJjw8Kq40.Yqgh.ItbyIT162mnmjMUDp8Lt_HqxcQvPS4MmE4o1_PHxur0Ey gXJBqS22n8Mcrrn_HgKeYB_yb1y9a_thp4xL2xIagMm3WVZu07_xJUA882cAs4NpMyXFkP7fnrmw NMnGnvOwqucBE1xm9tvSlXw84tM1zxd7s93CE_t_8PkzA8UOWuc8We6yjRpddSMN8fnkTKCtRYs4 59SgcgJPdOfaPLsmS.L7OtHkQZki2tmrf2DufdFXEyDxlKNjRUjw4ljoJJmoBBdiBohsem1M6qXf PXSIquNgtXXwY0x6Q6FYCQqsD1oFUg5HCje64swFYdEokxIFPVXpf3AUjBJ3AEjS.9JlqFQiy4Yl oGc21XXwKF43XFt9IGzompJXZDV8f2slCVI8qvUQM0YP.YnWX3TUp9YJYmJuZTPYvedCTTp2.gLZ EahFGnof23L5nHIPSa1amok5ODmIHwfgDpb_y1UPXQCn1nx9aHSNnPGOvfANlH3TMxz0OLvyZkSb AFs_hfCqPCbjW8bsielLFBz.CY3Ake6kyScg4fZ17_Iosy_0LZTiGycvisHeAnRfbPEFq6JcVpAz XsbO8hCaxoLDKY9IWa.Xc4.Q1EnVnyenlV0AfhR6_M3pWYs9ha6XdPOKj20mQkiRUP_5Y3XZKRCN JXdh0Pn4GCF30YQNbqt97RLpJJbbBw4WcAEnaKb9ivJBKzUPHqd4I5eowilYYYe7VB_6_V9Rpvqj CGsdPA1GnoxUu6IwGk14bFH0XICqvOkZGZkpz1iLjtQSjnYSASbxECQ3YDu37OxGC9wv4foOb_6G SlCoepqoIZQFyvJpmslqiYFgjBddvXqHqA24ckVrQrZaZOa.RlfwRPv8tAF6LFkNcwWnmo36j8SA _No2oWxEIhLbvjPV_p2vhPFsPUSHsTpM7e8BnKh2kcAQmUs_lMnbJwbEevI7MRSACXCtygV_bHSU S00Mswk0feCYx1o479VLrAi4NrSpCxrk5jK9w7OHidrN3nYcpRxLKnEmcd34_dGs6BqMuJwIHJvd 4wbI44SZGDd0rUOEb2YQfHvIQn7wvyDPpxZCN53YTPWBXg06aAcQ9MNBnooWOZ49LTm.Rso.CSMh qE_vyEcIjItVlcYyc_TAavTL2BwekSEborfUnHMH0xPRf2d_mBJ9CesKyZKEui24b_vBE0dryVQu y1b8ijwcrkqKJv7n3cf6egMb3wuikORqqUwDwJ8oxizSXWRUP8TpMVN0iCwMBnv3KaSPEij7Ya_L W8lqEsWqMCO3_UvXH_DTSFR633Hg8soUSVRLWiY1SQtrJj7_Q9x4V8Exsddeo9FttQouzpr1aDjN e1IuKcYtljIs5MIpi6fONhtNVV7HgKEilYBI_fVN507c6pd6RsslUnTVHsaiJ Received: from sonic.gate.mail.ne1.yahoo.com by sonic313.consmr.mail.gq1.yahoo.com with HTTP; Mon, 11 May 2020 23:34:29 +0000 Received: by smtp421.mail.ne1.yahoo.com (VZM Hermes SMTP Server) with ESMTPA ID c747c855cc85669484da741856bf045c; Mon, 11 May 2020 23:34:26 +0000 (UTC) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.80.23.2.2\)) Subject: Re: Curious buildworld stoppage on RPi3B running 12.1-stable. From: Mark Millard In-Reply-To: <20200511224130.GA41230@www.zefox.net> Date: Mon, 11 May 2020 16:34:25 -0700 Cc: freebsd-arm@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: References: <20200508180252.GA29832@www.zefox.net> <20200511224130.GA41230@www.zefox.net> To: bob prohaska X-Mailer: Apple Mail (2.3608.80.23.2.2) X-Rspamd-Queue-Id: 49Lcj427SFz4P6D X-Spamd-Bar: -- X-Spamd-Result: default: False [-2.31 / 15.00]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ptr:yahoo.com]; FREEMAIL_FROM(0.00)[yahoo.com]; MV_CASE(0.50)[]; DKIM_TRACE(0.00)[yahoo.com:+]; RCPT_COUNT_TWO(0.00)[2]; DMARC_POLICY_ALLOW(-0.50)[yahoo.com,reject]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; RCVD_TLS_LAST(0.00)[]; FREEMAIL_ENVFROM(0.00)[yahoo.com]; ASN(0.00)[asn:36647, ipnet:98.137.64.0/21, country:US]; MID_RHS_MATCH_FROM(0.00)[]; DWL_DNSWL_NONE(0.00)[yahoo.com.dwl.dnswl.org : 127.0.5.0]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.82)[-0.825,0]; R_DKIM_ALLOW(-0.20)[yahoo.com:s=s2048]; FROM_HAS_DN(0.00)[]; NEURAL_HAM_LONG(-0.98)[-0.981,0]; MIME_GOOD(-0.10)[text/plain]; IP_SCORE(0.00)[ip: (1.23), ipnet: 98.137.64.0/21(0.83), asn: 36647(0.66), country: US(-0.05)]; IP_SCORE_FREEMAIL(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[83.65.137.98.list.dnswl.org : 127.0.5.0]; RWL_MAILSPIKE_POSSIBLE(0.00)[83.65.137.98.rep.mailspike.net : 127.0.0.17]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 May 2020 23:34:33 -0000 On 2020-May-11, at 15:41, bob prohaska wrote: > On Fri, May 08, 2020 at 03:08:54PM -0700, Mark Millard wrote: >> On 2020-May-8, at 11:02, bob prohaska wrote: >>=20 >>> Here's an example of a curious hang on a Pi3 during -j4 buildworld. >>> The machine uses a 37GB mechanical USB disk running 12.1 r360689. >>>=20 >>> /boot/loader.conf contains >>> kern.cam.boot_delay=3D"20000" >>> vm.pageout_oom_seq=3D"4096" >>> vm.pfault_oom_attempts=3D"-1" >>>=20 >=20 > Two attempts to reproduce the buildworld hang on successive revisions=20= > of 12.1 (now at r360872) failed. Buildworld ran to completion in about=20= > 27 hours, which is about as fast as it ever ran, at least since the > introduction of clang 9. The compile did dwindle to a single thread, > but the thread continued to make progress and eventually four threads=20= > replaced it. >=20 > Swap activity looked different, remaining high (~1GB) until=20 > buildworld completed. Formerly swap use became insignificant once > the "building libraries" stage was over.=20 >=20 > The "swap_pager_getswapspace(24): failed" messages were still seen, > but they stopped relatively early in buildworld. Near as I can tell > they're innocuous, even if they look threatening.=20 The settings that you use to help prevent OOM's likely contribute to why things managed to continue without having to restart them manually (avoiding OOM kills). But those messages probably also mean that such builds are more likely to deadlock from having run out of usable swap/paging space. They may suggest that backing off the -jN setting to use a smaller N would be appropriate, say to -j3 from what you have described. > The tempest is back in the teapot 8-) >=20 >>> Top reports: >>>=20 >>> last pid: 84778; load averages: 0.00, 0.47, 1.35 = up 0+19:11:52 09:43:58 >>> 55 processes: 1 running, 54 sleeping >>> CPU: 0.0% user, 0.0% nice, 0.7% system, 0.0% interrupt, 99.3% = idle >>> Mem: 243M Active, 26M Inact, 13M Laundry, 171M Wired, 98M Buf, 453M = Free >>> Swap: 2263M Total, 698M Used, 1565M Free, 30% Inuse, 696K In >>=20 >> 453 MiByte Free, 698MiByte Swap/paging space used, and, see >> below, 263 MiByte RESident for c++ --on a machine with 1 GiByte >> of RAM with 171 MiByte Wired. The c++ RESident is 20 MiByte or >> so more than the 243 MiByte Active figure. >>=20 >>> PID USERNAME THR PRI NICE SIZE RES STATE C TIME WCPU = COMMAND >>> 82615 root 1 20 0 726M 263M swread 3 8:43 = 0.46% c++ >>> 1025 bob 1 20 0 13M 1052K CPU0 0 2:47 = 0.16% top >>> 1020 bob 1 20 0 19M 800K select 1 0:18 = 0.02% sshd >>> 66244 root 1 20 0 11M 228K select 0 0:03 = 0.00% make >>> 656 root 1 20 0 10M 244K select 0 0:00 0.00% = devd >>> 82405 root 1 20 0 17M 2460K select 0 0:25 = 0.00% make >>> 27467 root 1 20 0 10M 228K select 0 0:11 = 0.00% make >>> 27499 root 1 20 0 11M 232K select 0 0:07 = 0.00% make >>> 40948 root 1 20 0 11M 228K select 0 0:06 = 0.00% make >>> 928 root 1 20 0 16M 1004K select 0 0:05 0.00% = sendmail >>> 66255 root 1 20 0 14M 236K select 1 0:04 = 0.00% make >>> 73291 root 1 20 0 10M 224K select 1 0:02 = 0.00% make >>> 932 root 1 20 0 11M 340K nanslp 3 0:01 0.00% = cron >>> 727 root 1 20 0 11M 664K select 3 0:01 0.00% = syslogd >>>=20 >>> The buildworld output log file has stopped updating: >>>=20 >>> -rw-r--r-- 1 root wheel 18178806 May 8 06:34 buildworld.log >>> bob@nemesis:/usr/src % ls -l *.log >>> -rw-r--r-- 1 root wheel 18345625 May 8 08:17 buildworld.log >>> bob@nemesis:/usr/src % ls -l *.log >>> -rw-r--r-- 1 root wheel 18532738 May 8 09:34 buildworld.log >>> bob@nemesis:/usr/src % ls -l *.log >>> -rw-r--r-- 1 root wheel 18532738 May 8 09:34 buildworld.log >>> bob@nemesis:/usr/src % ls -l *.log >>> -rw-r--r-- 1 root wheel 18532738 May 8 09:34 buildworld.log >>> bob@nemesis:/usr/src % ls -l *.log >>> -rw-r--r-- 1 root wheel 18532738 May 8 09:34 buildworld.log >>> bob@nemesis:/usr/src %=20 >>> At this point clock time is 09:46, so it's been stuck 8 minutes. >>=20 >> See later below about how long loading from swap/paging >> space might be taking based on the below gstat information >> and the earlier top information. >>=20 >>> Gstat reports >>> dT: 1.010s w: 1.000s >>> L(q) ops/s r/s kBps ms/r w/s kBps ms/w %busy Name >>> 0 0 0 0 0.0 0 0 0.0 0.0| mmcsd0 >>> 1 80 80 321 12.4 0 0 0.0 99.4| da0 >>> 0 0 0 0 0.0 0 0 0.0 0.0| = mmcsd0s1 >>> 0 0 0 0 0.0 0 0 0.0 0.0| = mmcsd0s2 >>> 0 0 0 0 0.0 0 0 0.0 0.0| = diskid/DISK-9B9A5304 >>> 0 0 0 0 0.0 0 0 0.0 0.0| = msdosfs/MSDOSBOOT >>> 0 0 0 0 0.0 0 0 0.0 0.0| = mmcsd0s2a >>> 0 0 0 0 0.0 0 0 0.0 0.0| = mmcsd0s2b >>> 0 0 0 0 0.0 0 0 0.0 0.0| = diskid/DISK-9B9A5304s1 >>> 0 0 0 0 0.0 0 0 0.0 0.0| = diskid/DISK-9B9A5304s2 >>> 0 0 0 0 0.0 0 0 0.0 0.0| = ufsid/5bbd5a23da8b6195 >>> 0 0 0 0 0.0 0 0 0.0 0.0| = ufs/rootfs >>> 0 0 0 0 0.0 0 0 0.0 0.0| = diskid/DISK-9B9A5304s2a >>> 0 0 0 0 0.0 0 0 0.0 0.0| = diskid/DISK-9B9A5304s2b >>> 0 0 0 0 0.0 0 0 0.0 0.0| da0s1 >>> 1 80 80 321 12.4 0 0 0.0 99.5| da0s2 >>> 0 0 0 0 0.0 0 0 0.0 0.0| da0s2a >>> 1 80 80 321 12.4 0 0 0.0 99.5| da0s2b >>> bob@nemesis:~ %=20 >>=20 >> Note the lack of write activity and top also is reported >> showing: swread . Sort of like it is mostly doing a large >> reload of something that had been mostly paged out earlier. >>=20 > I was struck by the lack of any activity to da0s2a. The > machine wasn't waiting for anything _except_ swap. >=20 >> This is combined with that top output showing: 453M Free . >> Was there a time earlier with far less free? >>=20 > Yes, swapping had commenced hours earlier. >=20 >> Also: top only shows one c++ to match up with your -j4 . This >> suggests possibly a period of time when other things have not >> started, pending needing what that c++ is building. Or it just >> finished a parallel job but has not yet started another. >> Somewhat earlier there might have been more than one thing >> active. >>=20 > Four threads started, gradually dwindling to a single thread > by the time I noticed. After disturbing the machine by starting > the gstat script the remaining thread became more active and > eventually was joined by additional threads.=20 >=20 >> Can you find out what the c++ is compiling during this period? > It was part of llvm, though I neglected to record what. I planned > to observe more carefully on a second experiment, but failed. >=20 >> that might allow figuring out if it is something that normally >> sends some time has the only job despite -j4 . >>=20 >>> It looks as if the swap device is saturated, but swap is not = exhausted. >>=20 >> You later mention swap_pager_getswapspace errors, leading to the >> question if there was a period when swap (or its supporting RAM >> data structure space) had been exhausted. Were those the only >> messages in such earlier time frames? >>=20 > Yes, they appeared in a flurry in the first half (timewise) of > buildworld. Then no further console output.=20 >=20 >> As for being "saturated": >>=20 >> At 321 KB/s (the example in the gstat output), if it was loading >> something large, such as 512 MiBytes, just basically reading that >> much material at a mean of such a rate would be over 25 minutes: >>=20 >> 512*1024*1024_bytes * (1sec/(321*1024_bytes)) * (1minute/(60sec)) >>=20 >> (Not that I know the 512 MiByte is realistic or that the 321 >> KiBYtes/sec is a realistic mean rate.) This just gives an idea >> what might be involved and that being beyond seconds or even a >> small number of minutes for the general time scale may well be >> possible. >>=20 >> Extensive paging/swapping can vastly slow things down. >>=20 > That is a startling realization.=20 Since paging tends to be small, random reads, and spinning hard drives have seek times that contribute to overall time and slow the mean transfer rate compared to sequential and the like, hard drives tend to show such behavior. (No claim hard drives are the only media with slow small random read/write behavior.) >>> The machine isn't hung; ssh sessions are responsive, the serial = console >>> refreshes the login prompt when the Enter key is hit.=20 >>>=20 >>> Also, there are no _current_ errors on the serial console. However, = there >>> a quite a number of swap_pager_getswapspace(32): failed messages, = which >>> stopped some considerable time earlier. Buildworld didn't seem = affected by them.=20 >>=20 >> I'm not sure what can be said about the status of the machine >> after swap_pager_getswapspace failures are reported that do not >> have matching OOM kills involved. It may be that pages stayed >> resident that otherwise would have paged out and that other >> tradeoffs lead to slow-downs compared to having been able to >> free some RAM for other uses. (No deadlock happened, however.) >>=20 >> My expectation here is that you did run out of free swap/paging >> space space for a while. (It may be that internal data structures >> for managing swap/paging space use are the limit hit, instead of >> disk space, for all I know.) You did not indicate how big the >> swap/paging partition is. >>=20 > It's 2263M. =20 Yea, you did report that before: it was in the top output. I just did not notice at the right point. Sorry. >> You did not mention if booting is suggesting kern.maxswzone >> adjustments --or if you have done something to control that >> context to not use the default. >>=20 > No gripes from the kernel.=20 Yep: booted as aarch64, that should be the case. >>> Perhaps strangest of all, starting up a gstat script to log system >>> activity seems to slowly revive buildworld. %idle gradually drops to=20= >>> a few percent. >>=20 >> Did you look to see if it was still just the one c++ process (PID >> 82615) for the -j4 ? >>=20 > Once PID 82615 got back near 100% it was joined by others. =20 So 82615 did not exit first. Interesting. It sounds like 82615 spent lots of time hitting page faults and reading pages back in from the swapping/paging space, without making much progress between the page faults --until it finally had enough loaded. This looks to have delayed other activity that was pending. Again, this may suggest that a smaller -jN is appropriate for the builds in this context, say -j3 or possibly even -j2. >> Other things may also have changed, not just you starting a gstat >> script. This sort of judgement requires examining/monitoring the >> context for a time. >>=20 >>> If the gstat script is started before buildworld=20 >>> the stall doesn't seem to happen and buildworld finishes in about 27 >>> hours, which is as good as it gets. =20 >>=20 >> Are all the comparisons of from-scratch buildworld buildkernel >> activity and otherwise controlled to be very similar contexts? >>=20 > The experiments start with a cleanupscript: > make -j8 cleandir > cleandir.log && make -j8 cleandir > cleandir.log = && rm -rf /usr/obj/usr/ && rm *.log > (probably redundant, kept out of habit) >=20 > Then a buildscript > make -j4 -DNO_CLEAN buildworld > buildworld.log && make -j4 = buildkernel > buildkernel.log >=20 > Finally, the installscript: > make -j4 installworld > installworld.log && make -j4 installkernel > = installkernel.log Looks to be a from-scratch build each time. > . . . =3D=3D=3D Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) From owner-freebsd-arm@freebsd.org Tue May 12 08:59:50 2020 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id A36432E7014 for ; Tue, 12 May 2020 08:59:50 +0000 (UTC) (envelope-from mgamsjager@gmail.com) Received: from mail-yb1-xb44.google.com (mail-yb1-xb44.google.com [IPv6:2607:f8b0:4864:20::b44]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 49LsFK4k64z3Qwl for ; Tue, 12 May 2020 08:59:49 +0000 (UTC) (envelope-from mgamsjager@gmail.com) Received: by mail-yb1-xb44.google.com with SMTP id f5so6593562ybo.4 for ; Tue, 12 May 2020 01:59:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=Ds7p6l0JLugcqnGRvwuHtdrLrML7XU/5vsIFx3iaIIM=; b=eisns+z4U1iORZTXIAam9ZvbczBq7iXlZfOTGECPHOF8QryfE+5AH9810EIOeDHHqb kMs3rZP8K1JmBmZ33GuTwr+iIzx1n3FBMZqGamJrNexw9ciG5+yGILCUcy17KcYXiBOO 8VTjJUOgbwIqw3ByJvcvgCHsG6mOk8iTRVhc7cwBFA10d1BpHbgdt0h7aWDsyDhwZq3V bgRhUdAs1+qjfC2NpMtoC7t+Qs+vErwqyeaCyGgEQAeN5aXC0juJ/0nRBS6RCCIt3EMl iXtFMQZ9UsTbxBmHWf8NN8QRkaY0NEZaUwRw31pkprri2l7oKntI15lxfFGigvVscnAQ IsKQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=Ds7p6l0JLugcqnGRvwuHtdrLrML7XU/5vsIFx3iaIIM=; b=MJ0NfZHMalHkXDLRjntD3HTD+D0jR6SypMUclJfZ8IBYq/3RRiQWl7KgoBprtZxeiy wzTYEwVTnHFhkYCoZdtx1/LT2YEBcO1mrXY1wKaklqpJW5UZxO20B4jQnEpCwiAuI/G1 1oXfKFZxX4D/ei47d4qXBJoTKZ5DQvnELILjqS3/hIQNTC4huVI+/3gbHfGztQuCo+d2 MO76xLdZC66zo2QPOJGeDnMUXF5YgOasHfEMJb+4MArhd3c1KJzOhOIhJVb6RC5YVHgQ 8DjJLGCeN8gx8iE21uedGe+8U1n0V6z0Y4JpZ8YwjkYMuyZVEDBj9++w7nFZD0hAAzT7 aPTg== X-Gm-Message-State: AGi0PubnEmlF5ZnhSBCaI0ujKVRGxO+yzNFlbULV+XhUOpawUGjGejpf iJSn1Z90f5jKJJCVyfGVFUKWdPmqD4zNLeQmrT2Cl9KlwYw= X-Google-Smtp-Source: APiQypJCA1lCeQ3aFUWjt8CayWFCe7c60W+GpeRPgZfIZDl1onZtdOKkavl3K+HpyS0MaLtTdmgoTN76P5GUEUcctbs= X-Received: by 2002:a25:1c44:: with SMTP id c65mr34780218ybc.518.1589273987942; Tue, 12 May 2020 01:59:47 -0700 (PDT) MIME-Version: 1.0 From: Matthias Gamsjager Date: Tue, 12 May 2020 10:59:21 +0200 Message-ID: Subject: AWS Graviton2 To: freebsd-arm@freebsd.org X-Rspamd-Queue-Id: 49LsFK4k64z3Qwl X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=eisns+z4; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of mgamsjager@gmail.com designates 2607:f8b0:4864:20::b44 as permitted sender) smtp.mailfrom=mgamsjager@gmail.com X-Spamd-Result: default: False [-3.00 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36]; FREEMAIL_FROM(0.00)[gmail.com]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-arm@freebsd.org]; TO_DN_NONE(0.00)[]; IP_SCORE_FREEMAIL(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; IP_SCORE(0.00)[ip: (0.60), ipnet: 2607:f8b0::/32(-0.33), asn: 15169(-0.42), country: US(-0.05)]; TO_MATCH_ENVRCPT_ALL(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; RCVD_IN_DNSWL_NONE(0.00)[4.4.b.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.b.8.f.7.0.6.2.list.dnswl.org : 127.0.5.0]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com.dwl.dnswl.org : 127.0.5.0] Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.33 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 May 2020 08:59:50 -0000 Hi, so in other ARM news. Finally the new AWS M6g instances are available for public. And FreeBSD 12.1-STABLE r359985 is doing just fine on it. Did a buildworld on a 16 core 64GB instance and finished without any issues. -------------------------------------------------------------- >>> World build completed on Tue May 12 08:51:58 UTC 2020 >>> World built in 2259 seconds, ncpu: 16, make -j16 -------------------------------------------------------------- 27399.492u 1224.646s 37:39.66 1266.7% 51659+3589k 9455+144650io 2757pf+0w dmesg for anyone that is interested: Copyright (c) 1992-2020 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 12.1-STABLE r359985 GENERIC arm64 FreeBSD clang version 9.0.1 (git@github.com:llvm/llvm-project.git c1a0a213378a458fbea1a5c77b315c7dce08fd05) (based on LLVM 9.0.1) VT: init without driver. Starting CPU 1 (100) Starting CPU 2 (200) Starting CPU 3 (300) Starting CPU 4 (400) Starting CPU 5 (500) Starting CPU 6 (600) Starting CPU 7 (700) Starting CPU 8 (800) Starting CPU 9 (900) Starting CPU 10 (a00) Starting CPU 11 (b00) Starting CPU 12 (c00) Starting CPU 13 (d00) Starting CPU 14 (e00) Starting CPU 15 (f00) FreeBSD/SMP: Multiprocessor System Detected: 16 CPUs arc4random: no preloaded entropy cache random: entropy device external interface MAP 7c2e0000 mode 2 pages 272 MAP 7f6d0000 mode 2 pages 144 MAP 7f780000 mode 2 pages 272 MAP 9010000 mode 0 pages 1 kbd0 at kbdmux0 efirtc0: efirtc0: registered as a time-of-day clock, resolution 1.000000s acpi0: acpi0: Power Button (fixed) acpi0: Sleep Button (fixed) psci0: on acpi0 gic0: iomem 0x10000000-0x1001ffff,0x10200000-0x1ffeffff on acpi0 its0: on gic0 generic_timer0: irq 33,34,35 on acpi0 Timecounter "ARM MPCore Timecounter" frequency 121875000 Hz quality 1000 Event timer "ARM MPCore Eventtimer" frequency 121875000 Hz quality 1000 cpu0: on acpi0 pcib0: on acpi0 pci0: on pcib0 pci0: at device 1.0 (no driver attached) pci0: at device 2.0 (no driver attached) pci0: at device 3.0 (no driver attached) nvme0: mem 0x80114000-0x80117fff irq 36 at device 4.0 on pci0 ena0: mem 0x80110000-0x80113fff,0x80000000-0x800fffff,0x80100000-0x8010ffff irq 37 at device 5.0 on pci0 ena0: Elastic Network Adapter (ENA)ena v0.8.4 ena0: initalize 8 io queues ena0: Ethernet address: 06:b5:73:70:b3:4e pci0: at device 6.0 (no driver attached) pci0: at device 7.0 (no driver attached) pci0: at device 8.0 (no driver attached) pci0: at device 9.0 (no driver attached) pci0: at device 10.0 (no driver attached) pci0: at device 11.0 (no driver attached) pci0: at device 12.0 (no driver attached) pci0: at device 13.0 (no driver attached) pci0: at device 14.0 (no driver attached) pci0: at device 15.0 (no driver attached) pci0: at device 16.0 (no driver attached) pci0: at device 17.0 (no driver attached) pci0: at device 18.0 (no driver attached) pci0: at device 19.0 (no driver attached) pci0: at device 20.0 (no driver attached) pci0: at device 21.0 (no driver attached) pci0: at device 22.0 (no driver attached) pci0: at device 23.0 (no driver attached) pci0: at device 24.0 (no driver attached) pci0: at device 25.0 (no driver attached) pci0: at device 26.0 (no driver attached) pci0: at device 27.0 (no driver attached) pci0: at device 28.0 (no driver attached) pci0: at device 29.0 (no driver attached) pci0: at device 30.0 (no driver attached) pci0: at device 31.0 (no driver attached) acpi_button0: on acpi0 acpi0: Could not update all GPEs: AE_NOT_CONFIGURED cryptosoft0: device_attach: arm64_cpu0 attach returned 22 device_attach: arm64_cpu1 attach returned 22 device_attach: arm64_cpu2 attach returned 22 device_attach: arm64_cpu3 attach returned 22 device_attach: arm64_cpu4 attach returned 22 device_attach: arm64_cpu5 attach returned 22 device_attach: arm64_cpu6 attach returned 22 device_attach: arm64_cpu7 attach returned 22 device_attach: arm64_cpu8 attach returned 22 device_attach: arm64_cpu9 attach returned 22 device_attach: arm64_cpu10 attach returned 22 device_attach: arm64_cpu11 attach returned 22 device_attach: arm64_cpu12 attach returned 22 device_attach: arm64_cpu13 attach returned 22 device_attach: arm64_cpu14 attach returned 22 device_attach: arm64_cpu15 attach returned 22 Timecounters tick every 1.000 msec ena0: link is UP ena0: link state changed to UP nvme0: temperature threshold not supported Release APs...arc4random: no preloaded entropy cache nda0 at nvme0 bus 0 scbus0 target 0 lun 1 Trying to mount root from ufs:/dev/ufs/rootfs [rw]... nda0: done CPU 0: ARM Unknown Processor r3p1 affinity: 0 0 nda0: nvme version 1.0 x0 (max x0) lanes PCIe Gen0 (max Gen0) link Instruction Set Attributes 0 = nda0: 20480MB (41943040 512 byte sectors) Instruction Set Attributes 1 = Processor Features 0 = Processor Features 1 = <0x20> Memory Model Features 0 = <4k Granule,64k Granule,16k Granule,S/NS Mem,MixedEndian,16bit ASID,256TB PA> Memory Model Features 1 = Memory Model Features 2 = <32b CCIDX,48b VA,UAO,CnP> Debug Features 0 = Debug Features 1 = <0> Auxiliary Features 0 = <0> Auxiliary Features 1 = <0> CPU 1: ARM Unknown Processor r3p1 affinity: 1 0 CPU 2: ARM Unknown Processor r3p1 affinity: 2 0 CPU 3: ARM Unknown Processor r3p1 affinity: 3 0 CPU 4: ARM Unknown Processor r3p1 affinity: 4 0 CPU 5: ARM Unknown Processor r3p1 affinity: 5 0 CPU 6: ARM Unknown Processor r3p1 affinity: 6 0 CPU 7: ARM Unknown Processor r3p1 affinity: 7 0 CPU 8: ARM Unknown Processor r3p1 affinity: 8 0 CPU 9: ARM Unknown Processor r3p1 affinity: 9 0 CPU 10: ARM Unknown Processor r3p1 affinity: 10 0 CPU 11: ARM Unknown Processor r3p1 affinity: 11 0 CPU 12: ARM Unknown Processor r3p1 affinity: 12 0 CPU 13: ARM Unknown Processor r3p1 affinity: 13 0 CPU 14: ARM Unknown Processor r3p1 affinity: 14 0 CPU 15: ARM Unknown Processor r3p1 affinity: 15 0 arc4random: no preloaded entropy cache arc4random: no preloaded entropy cache arc4random: no preloaded entropy cache arc4random: no preloaded entropy cache arc4random: no preloaded entropy cache arc4random: no preloaded entropy cache arc4random: no preloaded entropy cache arc4random: no preloaded entropy cache arc4random: no preloaded entropy cache random: read_random_uio unblock wait random: read_random_uio unblock wait random: read_random_uio unblock wait random: unblocking device. arc4random: no preloaded entropy cache arc4random: no preloaded entropy cache arc4random: no preloaded entropy cache arc4random: no preloaded entropy cache arc4random: no preloaded entropy cache arc4random: no preloaded entropy cache lo0: link state changed to UP ena0: device is going UP ena0: device is going DOWN ena0: device is going UP Security policy loaded: MAC/ntpd (mac_ntpd) From owner-freebsd-arm@freebsd.org Wed May 13 03:10:47 2020 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 983962E54EC for ; Wed, 13 May 2020 03:10:47 +0000 (UTC) (envelope-from 010001720c0356cd-cd3a5d5b-ed11-4110-ac2b-1039edfffb78-000000@amazonses.com) Received: from a8-237.smtp-out.amazonses.com (a8-237.smtp-out.amazonses.com [54.240.8.237]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 49MKS62H37z4QQb for ; Wed, 13 May 2020 03:10:46 +0000 (UTC) (envelope-from 010001720c0356cd-cd3a5d5b-ed11-4110-ac2b-1039edfffb78-000000@amazonses.com) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple; s=ae7m2yrxjw65l2cqdpjxuucyrvy564tn; d=tarsnap.com; t=1589339445; h=From:Subject:To:Message-ID:Date:MIME-Version:Content-Type:Content-Transfer-Encoding; bh=JdARlG3o2m0ND4iZ7UgI1H2Ofh2WFgWM7kFSDZpJggA=; b=HxasFxJUyQcbgDXiYOOh9o8czzljWrnL6EfA2hJGOhNQWSc8DCjrmHB/J2/RoFqj hMEFJF7/jPCgkc2fh/cjkgRYyCE6os5DjKnswWt+1ASijrJR/GKFSsXKmJgD5KSlW6Y PD0Jes0zeCpD09vJFoWXgFh/DhiBmRKGUHNz9iU0= DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple; s=224i4yxa5dv7c2xz3womw6peuasteono; d=amazonses.com; t=1589339445; h=From:Subject:To:Message-ID:Date:MIME-Version:Content-Type:Content-Transfer-Encoding:Feedback-ID; bh=JdARlG3o2m0ND4iZ7UgI1H2Ofh2WFgWM7kFSDZpJggA=; b=YGg2YF+XDypamAn97yK24mbzc6kQq6pVc7BDLjxAeIFtebfl0b/bCF1PE8HhBLgO nbeOxIpOCpL73RZ4pzsi9OUdRqs8e2YQHC1eCLGLVN1anrLrnygnv1cJuCiYvHRp++8 P4/5vzi9AvuCldT6phsyuP8HS6Iskzu+4p7y64u8= From: Colin Percival Subject: Re: AWS Graviton2 To: freebsd-arm@freebsd.org Autocrypt: addr=cperciva@tarsnap.com; prefer-encrypt=mutual; keydata= mQGhBElrAAcRBACDfDys4ZtK+ErCJ1HAzYeteKpm3OEsvT/49AjUTLihkF79HhIKrCQU+1KC zv7BwHCMLb6hq30As9L7iFKG7n5QFLFC4Te/VcITUnWHMG/c3ViLOfJGvi+9/nOEHaM1dVJY D6tEp5yM1nHmVQpo9932j4KGuGFR0LhOK5IHXOSfGwCgxSFDPdgxe2OEjWxjGgY+oV3EafcD +JROXCTjlcQiG/OguQH4Vks3mhHfFnEppLxTkDuYgHZQiUtpcT9ssH5khgqoTyMar05OUdAj ZIhNbWDh4LgTj+7ZmvLhXT5Zxw8LX9d7T36aTB8XDQSenDqEtinMWOb0TCBBLbsB8EFG1WTT ESbZci9jJS5yhtktuZoY/eM8uXMD/3k4FWFO80VRRkELSp+XSy/VlSQjyi/rhl2nQq/oOA9F oJbDaB0yq9VNhxP+uFBzBWSqeIX0t1ZWLtNfVFr4TRP5hihI5ICrg/0OpqgisKsU2NFe9xyO hyJLYmfD8ebpDJ/9k30C7Iju9pVrwLm1QgS4S2fqJRcR+U4WbjvP7CgStCVDb2xpbiBQZXJj aXZhbCA8Y3BlcmNpdmFAdGFyc25hcC5jb20+iGEEExECACEFAklrALYCGwMHCwkIBwMCAQQV AggDBBYCAwECHgECF4AACgkQOM7KaQxqam6/igCgn+z2k3V5ggNppmWrZstt1U2lugsAoL7L wS9V9yLtil3oWmHtwpUqYruEuQINBElrAAcQCAD3ZLMIsP4CIDoJORg+YY0lqLVBgcnF7pFb 4Uy2+KvdWofN+DKH61rZLjgXXkNE9M4EQC1B4lGttBP8IY2gs41y3AUogGdyFbidq99rCBz7 LTsgARHwFxZoaHmXyiZLEU1QZuMqwPZV1mCviRhN5E3rRqYNXVcrnXAAuhBpvNyj/ntHvcDN 2/m+ochiuBYueU4kX3lHya7sOj+mTsndcWmQ9soOUyr8O0r/BG088bMn4qqtUw4dl5/pglXk jbl7uOOPinKf0WVd2r6M0wLPJCD4NPHrCWRLLLAjwfjrtoSRvXxDbXhCdgGBa72+K8eYLzVs hgq7tJOoBWzjVK6XRxR7AAMGB/9Mo3iJ2DxqDecd02KCB5BsFDICbJGhPltU7FwrtbC7djSb XUrwsEVLHi4st4cbdGNCWCrp0BRezXZKohKnNAPFOTK++ZfgeKxrV2sJod+Q9RILF86tQ4XF 7A7Yme5hy92t/WgiU4vc/fWbgP8gV/19f8nunaT2E9NSa70mZFjZNu4iuwThoUUO5CV3Wo0Y UISsnRK8XD1+LR3A2qVyLiFRwh/miC1hgLFCTGCQ3GLxZeZzIpYSlGdQJ0L5lixW5ZQD9r1I 8i/8zhE6qRFAM0upUMI3Gt1Oq2w03DiXrZU0Fu/R8Rm8rlnkQKA+95mRTUq1xL5P5NZIi4gJ Z569OPMFiEkEGBECAAkFAklrAAcCGwwACgkQOM7KaQxqam41igCfbaldnFTu5uAdrnrghESv EI3CAo8AoLkNMks1pThl2BJNRm4CtTK9xZeH Message-ID: <010001720c0356cd-cd3a5d5b-ed11-4110-ac2b-1039edfffb78-000000@email.amazonses.com> Date: Wed, 13 May 2020 03:10:45 +0000 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:68.0) Gecko/20100101 Thunderbird/68.4.2 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-SES-Outgoing: 2020.05.13-54.240.8.237 Feedback-ID: 1.us-east-1.Lv9FVjaNvvR5llaqfLoOVbo2VxOELl7cjN0AOyXnPlk=:AmazonSES X-Rspamd-Queue-Id: 49MKS62H37z4QQb X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; dkim=pass header.d=tarsnap.com header.s=ae7m2yrxjw65l2cqdpjxuucyrvy564tn header.b=HxasFxJU; dkim=pass header.d=amazonses.com header.s=224i4yxa5dv7c2xz3womw6peuasteono header.b=YGg2YF+X; dmarc=none; spf=pass (mx1.freebsd.org: domain of 010001720c0356cd-cd3a5d5b-ed11-4110-ac2b-1039edfffb78-000000@amazonses.com designates 54.240.8.237 as permitted sender) smtp.mailfrom=010001720c0356cd-cd3a5d5b-ed11-4110-ac2b-1039edfffb78-000000@amazonses.com X-Spamd-Result: default: False [-0.71 / 15.00]; ARC_NA(0.00)[]; FAKE_REPLY(1.00)[]; R_DKIM_ALLOW(-0.20)[tarsnap.com:s=ae7m2yrxjw65l2cqdpjxuucyrvy564tn,amazonses.com:s=224i4yxa5dv7c2xz3womw6peuasteono]; NEURAL_HAM_MEDIUM(-1.00)[-0.995,0]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:54.240.0.0/18:c]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; TO_DN_NONE(0.00)[]; DMARC_NA(0.00)[tarsnap.com]; RCPT_COUNT_ONE(0.00)[1]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; IP_SCORE(-2.01)[ip: (-2.41), ipnet: 54.240.8.0/21(-4.60), asn: 14618(-3.01), country: US(-0.05)]; DKIM_TRACE(0.00)[tarsnap.com:+,amazonses.com:+]; RCVD_IN_DNSWL_NONE(0.00)[237.8.240.54.list.dnswl.org : 127.0.15.0]; FORGED_SENDER(0.30)[cperciva@tarsnap.com,010001720c0356cd-cd3a5d5b-ed11-4110-ac2b-1039edfffb78-000000@amazonses.com]; RCVD_COUNT_ZERO(0.00)[0]; MIME_TRACE(0.00)[0:+]; RWL_MAILSPIKE_VERYGOOD(0.00)[237.8.240.54.rep.mailspike.net : 127.0.0.19]; ASN(0.00)[asn:14618, ipnet:54.240.8.0/21, country:US]; FROM_NEQ_ENVFROM(0.00)[cperciva@tarsnap.com,010001720c0356cd-cd3a5d5b-ed11-4110-ac2b-1039edfffb78-000000@amazonses.com]; FORGED_MUA_THUNDERBIRD_MSGID_UNKNOWN(2.50)[] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 May 2020 03:10:47 -0000 Matthias Gamsjager wrote: > so in other ARM news. Finally the new AWS M6g instances are available for > public. > > And FreeBSD 12.1-STABLE r359985 is doing just fine on it. FreeBSD 12.1-RELEASE should mostly work. The known issues are: 1. When a instance "shutdown" request is made to the EC2 API, a signal is sent to ARM64 EC2 instances via a PL061 controller -- which we don't have a driver for. As a result, FreeBSD doesn't respond to the shutdown request and EC2 eventually forcibly halts the instance (with predictable results of unclean filesystems etc). There is a review open for a driver (code contribution from Amazon!) but there will be other work needed as well: https://reviews.freebsd.org/D24065 2. When an EBS volume is attached to an EC2 instance, an ACPI Notify is sent alerting the instance to the "hotplug" event. We handle these on x86, but right now we're not doing anything with these on arm64. 3. While FreeBSD boots on "normal" Graviton 2 instances, we don't currently boot on "bare metal" instances. Jared McNeill was able to make NetBSD work on these but I'm not sure exactly what was involved except that the words "PCIe host controller" come up. I don't know nearly enough about these low-level architectural details to work on these issues, but if anyone here is interested in working on them I'll be happy to help however I can. -- Colin Percival Security Officer Emeritus, FreeBSD | The power to serve Founder, Tarsnap | www.tarsnap.com | Online backups for the truly paranoid From owner-freebsd-arm@freebsd.org Thu May 14 13:34:57 2020 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id B1D1A2F2380 for ; Thu, 14 May 2020 13:34:57 +0000 (UTC) (envelope-from pkk@spth.de) Received: from mout.kundenserver.de (mout.kundenserver.de [212.227.17.24]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.kundenserver.de", Issuer "TeleSec ServerPass Class 2 CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 49NCFr3phgz4LDq for ; Thu, 14 May 2020 13:34:56 +0000 (UTC) (envelope-from pkk@spth.de) Received: from [192.168.178.36] ([77.189.89.215]) by mrelayeu.kundenserver.de (mreue107 [212.227.15.183]) with ESMTPSA (Nemesis) id 1MvJjz-1jHQ6u0ZkH-00rHy3 for ; Thu, 14 May 2020 15:34:53 +0200 To: freebsd-arm@freebsd.org From: Philipp Klaus Krause Subject: Recommended arm hardware (mostly for compilation)? Autocrypt: addr=pkk@spth.de; prefer-encrypt=mutual; keydata= mQGiBD+wIQ0RBAD5IkcgQQIAPO93xBBvviI0htuoaeb++GqG51BImx+rnWIS+1z+r3y5jQU5 IRYS8eDC3eR5PFtde/f7/3zxaJIB0bgXB1eMPot5CaN7mpUySVNh9bzH/UP7rVH0Ut7Bx/CI 7EXxhvYE23F/TAf+gS4flFqQ/GdK+MME+dg8J5nFbwCg92xq6iuAvyz7vSho9qbKHsCD3AkE AMbuLLBvk4mPvs19aRGZvT/pows1uzkeNq8fpmzvryb4UxUbU89qlNzA2Bg8ztVZGX9x5drb C4tFE29ZFAHn2bojx2ADxG85+2as8yfcz6sPG4HMzeTtugzPGCeRAXaSknZHsw6AC6LrtsEU sjEZMElfvu8uU4dthfhXOIDVNRHmA/446GsHRLosDHFuDjHpBQJPJSBnFDyRSCge2Q0gup96 GGhNc7KkYeIB8Dh7dCN3h5RYXflVTspxmgANUa+RFpL4pynsF16rtkfeh0UR8uLdoaGwMChw GyWIdRhX8MLQ8v3WHPCUrB/1f5xhRypQgF0/c8y4w5BarGQXy7AM0PljBbQxUGhpbGlwcCBL cmF1c2UgKFN0YW5kYXJkc2NobMO8c3NlbCkgPHBra0BzcHRoLmRlPohbBBMRAgAbBQI/sCEN BgsJCAcDAgMVAgMDFgIBAh4BAheAAAoJEG7VFfsbKC6a31wAni0szX2x9jjNqqch2fE5zOkd IJsSAKCuZaayyxtHPb6rpQtbDMUTS7rXe7kCDQQ/sCFjEAgAknletShOrS5UeFH6V09TksPL 5w8S1SaQThvdberD74Uaq5Weoeu5fCzeDlhRvTC+wQFxL5W2wdM3ZhqRpZIri7X3ab/WUsqv 0FCK8LB9HfioafjNg7uQbyUannvyBkj4WAfHrTDgDbNw8EJMehab9MUeCUZEkhXrk9b3rp3r /uoic1pymK0aZX+wUfayXGANAAk75HAruEWxpGObjcJ587tTOsfDAFnJlXKXLVXuqJDSraym ankbEfyX1CmfhetYn+s1fCpAHX/GOIQPEG2BCdeLdy8ApN0l6MIrRkJKbBnvnc8HsUI7Elfu huemyI/Nvhxk5+tuOS5kZBIyZKe8CwADBQf+InHwn00dafe8XNod9jRsHgCqE259ocEiL0Zs rw3NfwbckR6YVGtoovHna6I3+o4F4GPS/869WFw/w1HGGsa9t6SRjWeoH221bxYc+aTstGbA hd9OuDXnXFi9Mokh34cXQexvrVYjfOdbAl9TRezPBRygzr6XvUdUtIpZjZhW0WSdhdF67Obl F+S9kCX7v3Q0kSqnjzk05Qs5kHyaE+7BKiGQhvCz51J++CTCc/g16eOVVabHNLalAEInq1jn jAB15+JxDcA3HFup7+sHkkscAEQPPi8aNnWR32su0w9hfE1qQkvyHhOiPX2GVhm/Lt0C1vGr ZCB9Bve3r8M+Z7uMaohGBBgRAgAGBQI/sCFjAAoJEG7VFfsbKC6aQ4oAnibaEjyIlrRMTmyL K76lqhloK0EPAKCQsgCELscmeJnxyjV1zZt6AJ6ctQ== Message-ID: <1b109252-3232-05c4-e1e0-2fea4739583d@spth.de> Date: Thu, 14 May 2020 15:34:52 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.7.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit X-Provags-ID: V03:K1:d/JptSmHq8GnyCXFoT/jNILNsugIqgmEx2cAz9o19AN1dFY3u8F ujeRWsvn66ocDsFgWuNxndCWlrQK7Hn/c5GhFW3Zji3+IF9L6u2hAbFypGL5wcs+AHJLVNc v34zaZhzyPoGB2KjEVLaa2dgWZ8/MYW33Pin6wqM2duW679+SREGFdNebbmClk87xtuiTvX 0/5ywHsfYLHXypG2ekTVA== X-Spam-Flag: NO X-UI-Out-Filterresults: notjunk:1;V03:K0:K8Mf53mUAZQ=:gnQIK3T8NaFIYyy5HtRU56 bx7vk+wOH+WarKuiOCOnuv88lQdSkckiN4mH8yYvjxZ0wtIDBN0mtJGp3PzeITN/U7EoS/cEC k8cRslU4bslRNLKLmMiH/vQ+lSlRAX9eiMkOfeUaiWxothjLgcI/gWmHODQLAbmj5oM/wawM8 f6OzWSvOSKef3a8DU0BkvqfnGJBczOSboXcAycWhrUj+znIMmjUSoc0Z7Jwv13IzQzpLVGM75 77HVUOKijgOiZ1odJ6WQTY9Tcd1lhY/7I/DKSVr4hO6fRwxgrV8vf8uZgshQII4LgZKYHjNFg HOTqAtkEFegBwyNtYxEYK8/B+9XJCcXKX5j7KiqWus4ecLK/7ZOMPQrnWTNi74W1OO2yFWY/C z9neYiGrNs+T5AW+ZVzj6U0w/Mq6p0nl24HRKks4QuU7YQu+Eh7mKkq5DV9jWPCZ0OUu2QaYN yJQ222xR8JnIaUlw4mCvyYZ+IRLwIrDO5rwrzC/SP3+1qBTYZEq+LBP/+X0elH6rbjr+kOoJA QJCEcox38hdTXfKBjhgSr1ZnLN3vE231gqpS1edcpD+eyKoQDTEBCRsoISt2equQo6J0lYT1O XzzEzOS173Cs+ZkVTJsYZN12jcDI5WIigFovROD4Fjk5rpJbK2b3Rr6FwtgN71WadLnrm2c+U p2o0yRNivkDGMOT0QJULqvwJvUoCaIKRR28zYAXak7HY77O39UDwjlaEGb3lZpbdOJz0VHipU xjAb0J9NOX3Maztroc2+KaZQ6bTATAVgMkm/zhZxV0xMWSIwO4ddsIC5qAX6k0K+r7Cw2bZOU yuibySyP6WJUhkwESAiWGHt9W+fVWHeAn3m5uM+7tkmwN5khlI= X-Rspamd-Queue-Id: 49NCFr3phgz4LDq X-Spamd-Bar: +++ Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of pkk@spth.de has no SPF policy when checking 212.227.17.24) smtp.mailfrom=pkk@spth.de X-Spamd-Result: default: False [3.33 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; RECEIVED_SPAMHAUS_PBL(0.00)[215.89.189.77.khpj7ygk5idzvmvt5x4ziurxhy.zen.dq.spamhaus.net : 127.0.0.10]; FROM_HAS_DN(0.00)[]; RWL_MAILSPIKE_GOOD(0.00)[24.17.227.212.rep.mailspike.net : 127.0.0.18]; TO_MATCH_ENVRCPT_ALL(0.00)[]; IP_SCORE(0.05)[ip: (-0.52), ipnet: 212.227.0.0/16(-1.20), asn: 8560(2.00), country: DE(-0.02)]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-arm@freebsd.org]; TO_DN_NONE(0.00)[]; AUTH_NA(1.00)[]; RCPT_COUNT_ONE(0.00)[1]; NEURAL_SPAM_MEDIUM(0.41)[0.412,0]; MIME_TRACE(0.00)[0:+]; NEURAL_SPAM_LONG(0.97)[0.968,0]; RCVD_IN_DNSWL_NONE(0.00)[24.17.227.212.list.dnswl.org : 127.0.5.0]; R_SPF_NA(0.00)[]; DMARC_NA(0.00)[spth.de]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; SUBJECT_ENDS_QUESTION(1.00)[]; ASN(0.00)[asn:8560, ipnet:212.227.0.0/16, country:DE]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_TLS_ALL(0.00)[]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 May 2020 13:34:57 -0000 I'm considering to add a FreeBSD arm machine to the Small Device C Compiler (SDCC) compile farm. The goal would be to have another arm machine in the farm (for redundancy in case we need to drop the current GNU/Linux arm machine, which ) and a FreeBSD machine (to allow us to promote FreeBSD to an officially supported platform for SDCC). Its task would be daily compilation of SDCC snapshots and running regression tests (i.e. mostly compiling small test programs with SDCC and running the binaries on emulators). Can you recommend some hardware? A RasPi 3B would probably a bit too weak (I have one and tried FreeBSD 12 on it; the 1GB RAM limit is an issue for this task - in particular it makes parallel compilation impossible); there currently is some RasPi running GNU/Linux in the farm and it barely keeps up with the load. So I'm looking for something with sufficient RAM that is likely to be well-supported by FreeBSD for some years. So far, I've considered: RasPi 4B - hardware seems ok, though FreeBSD support is apaprently lacking due to lack of documentation (how does OpenBSD manage?), and only 4 GB of RAM. RockPro64 - hardware seems okay, though only 4 GB of RAM. I've read on this list thaat the big/little cores aren't handled well by FreeBSD. Pine H64 - small RAM (3GB), rather new. MACCHIATObin - a bit on the expensive side, but still okay and has a RAM slot. Which of these is likely to work out-of-the-box in the FreeBSD 13 release? Any recommendations on which hardware to get? From owner-freebsd-arm@freebsd.org Thu May 14 13:43:07 2020 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id AB3992F27CF for ; Thu, 14 May 2020 13:43:07 +0000 (UTC) (envelope-from ganbold@gmail.com) Received: from mail-qt1-x82a.google.com (mail-qt1-x82a.google.com [IPv6:2607:f8b0:4864:20::82a]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 49NCRG5ZLcz4Lqq for ; Thu, 14 May 2020 13:43:06 +0000 (UTC) (envelope-from ganbold@gmail.com) Received: by mail-qt1-x82a.google.com with SMTP id 4so2844675qtb.4 for ; Thu, 14 May 2020 06:43:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=y2TDCQb78Hx4EtoRZeHvYovpIcAvqJDKKjnPuXL6/6M=; b=oPBNpLkVRwZOjJYj0S+sxJXh695nviWlA/F2BAfxXemQ+O/UGwcsUdrN1Idtoj+o9k TOwte4BMZzjlidFJT4fRRuARRgV+ugCHxKyzzeSl1eQvQ/5KNs7KMy4xsL2VpaQtaOoe jszEK7r0XtCNPK7t6+cwxUzAX3jg4x3Ee2mzXRh/YLC0cD2fYAhBu8lTJIB4BibKajC6 9o3naX1YXx2AtfbOnQshlW4N4j7ksi2aGaYv/qq5oHls/S/9p0jc6wtexPm85obg1D5O vRoVh/iOjTPxzX5GTJZ6x6JC1EDpeQeDIdQxOuLAuS0ryyMHMVIcSDIleTkC6u08OeUl rtMw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=y2TDCQb78Hx4EtoRZeHvYovpIcAvqJDKKjnPuXL6/6M=; b=DmafvbFlGX8fLh2+3l8JN///Byd6tT3PxdB3In2rhUTKkTTFazgBpM2TRs+C94EKwL oM46KXuKL7ilnAxnf8ONhGk+WpdYYWLbgsnFaPQu9jv6+QVJG0R6CsOf5063cgHM6mPx RP5nm9r8X4ZPveW8YKkVZ7nzQMcPmoumAKR5kY5LPHulAgXz7h9HARUko5nQMlcRan34 v+yXQZOCe+2H4nVr1drW7eLbDzhtFVgHzcODmtb+Cpr6HhHupDn638yAUfBhHspIz3NE e22mG5ufng9EBkZZFb5hH+O4nTwK/mYGAmFUh/UMwC4/tZczdYoS+O4OIvLkcI08RBim 8WBw== X-Gm-Message-State: AOAM531eH+sfIX0BpEJlcyB49r0hNcSYIrgAtefeiikUz2kKAB+WoKud PPfghIkMy8Kfi6gbzrx9W9vX+L28UQLyJEkfDjERqw== X-Google-Smtp-Source: ABdhPJw7hZ8COXkQTFoIgth0usaUyUrDcy8KkGloZ0092XWJBb6TO0LFy+sAHyi9QIis9eSU0roKWyQO+YSta2GwxCI= X-Received: by 2002:aed:3b54:: with SMTP id q20mr4549250qte.362.1589463785767; Thu, 14 May 2020 06:43:05 -0700 (PDT) MIME-Version: 1.0 References: <1b109252-3232-05c4-e1e0-2fea4739583d@spth.de> In-Reply-To: <1b109252-3232-05c4-e1e0-2fea4739583d@spth.de> From: Ganbold Tsagaankhuu Date: Thu, 14 May 2020 21:42:52 +0800 Message-ID: Subject: Re: Recommended arm hardware (mostly for compilation)? To: Philipp Klaus Krause Cc: freebsd-arm X-Rspamd-Queue-Id: 49NCRG5ZLcz4Lqq X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20161025 header.b=oPBNpLkV; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of ganbold@gmail.com designates 2607:f8b0:4864:20::82a as permitted sender) smtp.mailfrom=ganbold@gmail.com X-Spamd-Result: default: False [-1.00 / 15.00]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36:c]; FREEMAIL_FROM(0.00)[gmail.com]; URI_COUNT_ODD(1.00)[3]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; RCPT_COUNT_TWO(0.00)[2]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; FROM_EQ_ENVFROM(0.00)[]; IP_SCORE(0.00)[ip: (-9.33), ipnet: 2607:f8b0::/32(-0.33), asn: 15169(-0.42), country: US(-0.05)]; MIME_TRACE(0.00)[0:+,1:+,2:~]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; DWL_DNSWL_NONE(0.00)[gmail.com.dwl.dnswl.org : 127.0.5.0]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-0.996,0]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; FROM_HAS_DN(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-arm@freebsd.org]; IP_SCORE_FREEMAIL(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[a.2.8.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.b.8.f.7.0.6.2.list.dnswl.org : 127.0.5.0]; SUBJECT_ENDS_QUESTION(1.00)[]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[] Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.33 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 May 2020 13:43:07 -0000 On Thu, May 14, 2020, 21:35 Philipp Klaus Krause wrote: > I'm considering to add a FreeBSD arm machine to the Small Device C > Compiler (SDCC) compile farm. The goal would be to have another arm > machine in the farm (for redundancy in case we need to drop the current > GNU/Linux arm machine, which ) and a FreeBSD machine (to allow us to > promote FreeBSD to an officially supported platform for SDCC). Its task > would be daily compilation of SDCC snapshots and running regression > tests (i.e. mostly compiling small test programs with SDCC and running > the binaries on emulators). > > Can you recommend some hardware? > > A RasPi 3B would probably a bit too weak (I have one and tried FreeBSD > 12 on it; the 1GB RAM limit is an issue for this task - in particular it > makes parallel compilation impossible); there currently is some RasPi > running GNU/Linux in the farm and it barely keeps up with the load. > > So I'm looking for something with sufficient RAM that is likely to be > well-supported by FreeBSD for some years. > > So far, I've considered: > > RasPi 4B - hardware seems ok, though FreeBSD support is apaprently > lacking due to lack of documentation (how does OpenBSD manage?), and > only 4 GB of RAM. > > RockPro64 - hardware seems okay, though only 4 GB of RAM. I've read on > this list thaat the big/little cores aren't handled well by FreeBSD. > RK3399 board with nvme disk and with little core is working fine, and it is probably the cheapest option in my opinion. Ganbold > Pine H64 - small RAM (3GB), rather new. > > MACCHIATObin - a bit on the expensive side, but still okay and has a RAM > slot. > > Which of these is likely to work out-of-the-box in the FreeBSD 13 > release? Any recommendations on which hardware to get? > _______________________________________________ > freebsd-arm@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-arm > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" > From owner-freebsd-arm@freebsd.org Thu May 14 14:04:44 2020 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 81F562F2E5F for ; Thu, 14 May 2020 14:04:44 +0000 (UTC) (envelope-from greg@unrelenting.technology) Received: from out1.migadu.com (out1.migadu.com [91.121.223.63]) (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 49NCwB1S5Tz4MmM for ; Thu, 14 May 2020 14:04:41 +0000 (UTC) (envelope-from greg@unrelenting.technology) Date: Thu, 14 May 2020 14:04:31 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=unrelenting.technology; s=default; t=1589465073; 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=oRu5JBIdxMaRMoOGF04k/7bh6qGdA4awMdmMJLWenck=; b=C+otxMyOqtBD8Yz3cqLMvyV/WLlKSIICm3W1BqswGL8C4mfauLfmX6tdkhbXcs9adMZ35Y dnEdJXIAXM1UbTbcaOVjjO2s601+47uEqSCFfcmglYXLNd39Dq0+7WqbUOxjSTRr6mnMHw oT/cQSuBwOFpwfMUOKXY1PnANdsVuzI= X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers. From: myfreeweb To: freebsd-arm@freebsd.org, Philipp Klaus Krause Subject: Re: Recommended arm hardware (mostly for compilation)? In-Reply-To: <1b109252-3232-05c4-e1e0-2fea4739583d@spth.de> References: <1b109252-3232-05c4-e1e0-2fea4739583d@spth.de> Message-ID: <47A5AF8A-1EB9-4721-94D5-B0A0A6FFF69B@unrelenting.technology> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Spam-Score: 0.90 X-Rspamd-Queue-Id: 49NCwB1S5Tz4MmM X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=unrelenting.technology header.s=default header.b=C+otxMyO; dmarc=pass (policy=none) header.from=unrelenting.technology; spf=pass (mx1.freebsd.org: domain of greg@unrelenting.technology designates 91.121.223.63 as permitted sender) smtp.mailfrom=greg@unrelenting.technology X-Spamd-Result: default: False [-3.88 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[unrelenting.technology:s=default]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:91.121.223.63]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; IP_SCORE(-1.88)[ip: (-9.77), ipnet: 91.121.0.0/16(-1.61), asn: 16276(1.98), country: FR(-0.00)]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[unrelenting.technology:+]; RCPT_COUNT_TWO(0.00)[2]; DMARC_POLICY_ALLOW(-0.50)[unrelenting.technology,none]; RCVD_COUNT_ZERO(0.00)[0]; FROM_EQ_ENVFROM(0.00)[]; SUBJECT_ENDS_QUESTION(1.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:16276, ipnet:91.121.0.0/16, country:FR]; MID_RHS_MATCH_FROM(0.00)[] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 May 2020 14:04:44 -0000 On May 14, 2020 1:34:52 PM UTC, Philipp Klaus Krause wrote= : >Can you recommend some hardware?=20 AWS EC2 m6g instances :) >RockPro64 - hardware seems okay, though only 4 GB of RAM=2E I've read on >this list thaat the big/little cores aren't handled well by FreeBSD=2E There's no smart scheduler setting that would keep the big cores occupied = as much as possible for max performance, yes=2E But if you don't need more parallelism than 2 cores, you can just cpuset y= our workload to the big cores=2E >MACCHIATObin - a bit on the expensive side, but still okay and has a RAM >slot=2E It's great, it's the cheapest arm64 "Actual PC" you can get=2E From owner-freebsd-arm@freebsd.org Thu May 14 14:33:20 2020 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 82AD72F396C for ; Thu, 14 May 2020 14:33:20 +0000 (UTC) (envelope-from maciphone2@googlemail.com) Received: from mail-wr1-x42d.google.com (mail-wr1-x42d.google.com [IPv6:2a00:1450:4864:20::42d]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 49NDY82QLLz4PwP for ; Thu, 14 May 2020 14:33:16 +0000 (UTC) (envelope-from maciphone2@googlemail.com) Received: by mail-wr1-x42d.google.com with SMTP id y3so4451041wrt.1 for ; Thu, 14 May 2020 07:33:16 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:content-transfer-encoding:mime-version :subject:date:references:to:in-reply-to:message-id; bh=nL7JjvkdSfvRIS9FyKFF8x/Pct+mnrtx6uJLrbLB8y0=; b=hUsvY6MjbUzgEVODxZ3AcVUX1yVL4N3bHW7j+YyBPM/+GsT+oMLlRYBuQTTk39LWUJ eoazIonlkTrdOMk3j9McBp5WOY9hS65+99uLbl+e125mS2yTN/8CjNuBZhQkZyhw60sE zKZPlQzq5ww9jetd9KBuPqLINCMM3BGp9Cy/E7rC2jn+jeKuMWTkAJNhSjlST2RT4oB8 ufdVYhbv7PFdqlkpbyHICQjcWyP3XzMezqvjgdYGXKbudV1kULHSZZExaAd2gvMayAR0 KiXOo7jAzxSF1JAMMb8/PzWdENxNCJGKScFEKvf0x7I82DdfYXdyx9YcCX80lFEY0w3z ETrg== X-Gm-Message-State: AOAM530lVt2N9cfOrG0r64AIQjzpHw63EHMa4rRIsiYPWuly/2PcoMYT gKb4kt8z/IU4+yiZfgJ+yvDT8LmE X-Google-Smtp-Source: ABdhPJxe7CyTxeV6nDJqswShDAJdoLxLjIAXNPfklB8Qgm07SWuoBYJFZeRaN0woHDcweldrrCnarg== X-Received: by 2002:adf:e582:: with SMTP id l2mr6216786wrm.392.1589466794145; Thu, 14 May 2020 07:33:14 -0700 (PDT) Received: from [192.168.1.167] ([46.114.104.254]) by smtp.googlemail.com with ESMTPSA id 60sm4405900wrp.92.2020.05.14.07.33.12 for (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Thu, 14 May 2020 07:33:12 -0700 (PDT) From: =?utf-8?Q?Klaus_K=C3=BCchemann?= Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.80.23.2.2\)) Subject: Re: Recommended arm hardware (mostly for compilation)? Date: Thu, 14 May 2020 16:33:11 +0200 References: <1b109252-3232-05c4-e1e0-2fea4739583d@spth.de> <47A5AF8A-1EB9-4721-94D5-B0A0A6FFF69B@unrelenting.technology> To: freebsd-arm@freebsd.org In-Reply-To: <47A5AF8A-1EB9-4721-94D5-B0A0A6FFF69B@unrelenting.technology> Message-Id: <9E10C464-474F-489A-A667-B263A64E78F2@googlemail.com> X-Mailer: Apple Mail (2.3608.80.23.2.2) X-Rspamd-Queue-Id: 49NDY82QLLz4PwP X-Spamd-Bar: - X-Spamd-Result: default: False [-1.50 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36]; FREEMAIL_FROM(0.00)[googlemail.com]; TO_DN_NONE(0.00)[]; MV_CASE(0.50)[]; RCVD_COUNT_THREE(0.00)[3]; DKIM_TRACE(0.00)[googlemail.com:+]; DMARC_POLICY_ALLOW(-0.50)[googlemail.com,quarantine]; RECEIVED_SPAMHAUS_PBL(0.00)[254.104.114.46.khpj7ygk5idzvmvt5x4ziurxhy.zen.dq.spamhaus.net : 127.0.0.11]; FROM_EQ_ENVFROM(0.00)[]; SUBJECT_ENDS_QUESTION(1.00)[]; FREEMAIL_ENVFROM(0.00)[googlemail.com]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; MID_RHS_MATCH_FROM(0.00)[]; DWL_DNSWL_NONE(0.00)[googlemail.com.dwl.dnswl.org : 127.0.5.0]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-0.999,0]; R_DKIM_ALLOW(-0.20)[googlemail.com:s=20161025]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-arm@freebsd.org]; IP_SCORE_FREEMAIL(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; MIME_TRACE(0.00)[0:+]; RCVD_IN_DNSWL_NONE(0.00)[d.2.4.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.5.4.1.0.0.a.2.list.dnswl.org : 127.0.5.0]; RBL_BLOCKLISTDE_FAIL(0.00)[d.2.4.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.5.4.1.0.0.a.2.bl.blocklist.de:server fail]; IP_SCORE(0.00)[ip: (-8.68), ipnet: 2a00:1450::/32(-2.27), asn: 15169(-0.42), country: US(-0.05)]; RCVD_TLS_ALL(0.00)[] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 May 2020 14:33:20 -0000 > Am 14.05.2020 um 16:04 schrieb myfreeweb = : >=20 >=20 >=20 > On May 14, 2020 1:34:52 PM UTC, Philipp Klaus Krause = wrote: >> Can you recommend some hardware?=20 >=20 > AWS EC2 m6g instances :) >=20 >> RockPro64 - hardware seems okay, though only 4 GB of RAM. I've read = on >> this list thaat the big/little cores aren't handled well by FreeBSD. >=20 > There's no smart scheduler setting that would keep the big cores = occupied as much as possible for max performance, yes. > But if you don't need more parallelism than 2 cores, you can just = cpuset your workload to the big cores. >=20 >> MACCHIATObin - a bit on the expensive side, but still okay and has a = RAM >> slot. >=20 > It's great, it's the cheapest arm64 "Actual PC" you can get. > _______________________________________________ > freebsd-arm@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-arm > To unsubscribe, send any mail to = "freebsd-arm-unsubscribe@freebsd.org=E2=80=9C If someone=E2=80=99s looking for horsepower between those options, = consider the LX2K from SolidRun, while current support for FreeBSD is unknown to me .=20 From owner-freebsd-arm@freebsd.org Thu May 14 14:56:56 2020 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 1ECEF2F4300 for ; Thu, 14 May 2020 14:56:56 +0000 (UTC) (envelope-from maciphone2@googlemail.com) Received: from mail-wr1-x433.google.com (mail-wr1-x433.google.com [IPv6:2a00:1450:4864:20::433]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 49NF4Q3kL7z4R9P for ; Thu, 14 May 2020 14:56:54 +0000 (UTC) (envelope-from maciphone2@googlemail.com) Received: by mail-wr1-x433.google.com with SMTP id s8so4528956wrt.9 for ; Thu, 14 May 2020 07:56:54 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:content-transfer-encoding:mime-version :subject:date:references:to:in-reply-to:message-id; bh=2U+a5TrEyswKoS59/CMi6Cn31g/nIYEMUBdWEoErn5E=; b=h3ei6O0KkU1bjbzAwOm41wby7u7TY0qFcVToR5crW16n7XUmW49uUaKH0yWCVOYeOf yfVahxNTwJSJQBeO7l+V6Z0JuYgtCzpyjNzFmzQD4nfJ0QmI+vNrNh/7kek48p2UIkX4 hboVkP/6FP2ec8kTe553zBjRATGaSsQQXKCips5dvbCHRMvuP9gNxKQLXe8p6v2ZFkHz QCHFaMGRMlxQyNowULYNeKtpePptEKJ2LPL2/+l16Aj1EeWG5ZxDVuSChRdy42BcDvcz UpXGnJs+lgRjeKL31eZsqcKsH0+6+F9pig79KziyShAyNmk3QUfvz3C9HP+hFAA6jIhS oLuA== X-Gm-Message-State: AOAM531kTZO4FP98nhy7kC5pXH4KA90eCjj5Ck+Bm8nXkRZXMctZnQvR DHrBh0Y3tzwC4uC/KtAOtcMtCFWn X-Google-Smtp-Source: ABdhPJyvtU1BpIAeLbqRKETcDOuoDtdpLoHfSXyUhqPGyqpUbZcEb8qRrnwdLZ24w5IlsSso7baCPw== X-Received: by 2002:a5d:6284:: with SMTP id k4mr6261055wru.40.1589468211833; Thu, 14 May 2020 07:56:51 -0700 (PDT) Received: from [192.168.1.167] ([46.114.104.254]) by smtp.googlemail.com with ESMTPSA id v5sm4202003wrr.93.2020.05.14.07.56.50 for (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Thu, 14 May 2020 07:56:51 -0700 (PDT) From: =?utf-8?Q?Klaus_K=C3=BCchemann?= Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.80.23.2.2\)) Subject: Re: Recommended arm hardware (mostly for compilation)? Date: Thu, 14 May 2020 16:56:49 +0200 References: <1b109252-3232-05c4-e1e0-2fea4739583d@spth.de> <47A5AF8A-1EB9-4721-94D5-B0A0A6FFF69B@unrelenting.technology> <9E10C464-474F-489A-A667-B263A64E78F2@googlemail.com> To: freebsd-arm@freebsd.org In-Reply-To: <9E10C464-474F-489A-A667-B263A64E78F2@googlemail.com> Message-Id: <3FE63A9F-FD74-4CD0-B2BE-D9DF76530155@googlemail.com> X-Mailer: Apple Mail (2.3608.80.23.2.2) X-Rspamd-Queue-Id: 49NF4Q3kL7z4R9P X-Spamd-Bar: - X-Spamd-Result: default: False [-1.50 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36]; FREEMAIL_FROM(0.00)[googlemail.com]; TO_DN_NONE(0.00)[]; MV_CASE(0.50)[]; RCVD_COUNT_THREE(0.00)[3]; DKIM_TRACE(0.00)[googlemail.com:+]; DMARC_POLICY_ALLOW(-0.50)[googlemail.com,quarantine]; RECEIVED_SPAMHAUS_PBL(0.00)[254.104.114.46.khpj7ygk5idzvmvt5x4ziurxhy.zen.dq.spamhaus.net : 127.0.0.11]; FROM_EQ_ENVFROM(0.00)[]; SUBJECT_ENDS_QUESTION(1.00)[]; FREEMAIL_ENVFROM(0.00)[googlemail.com]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; MID_RHS_MATCH_FROM(0.00)[]; DWL_DNSWL_NONE(0.00)[googlemail.com.dwl.dnswl.org : 127.0.5.0]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[googlemail.com:s=20161025]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-arm@freebsd.org]; IP_SCORE_FREEMAIL(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; MIME_TRACE(0.00)[0:+]; RCVD_IN_DNSWL_NONE(0.00)[3.3.4.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.5.4.1.0.0.a.2.list.dnswl.org : 127.0.5.0]; IP_SCORE(0.00)[ip: (-9.03), ipnet: 2a00:1450::/32(-2.27), asn: 15169(-0.42), country: US(-0.05)]; RCVD_TLS_ALL(0.00)[] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 May 2020 14:56:56 -0000 > If someone=E2=80=99s looking for horsepower between those options, = consider the LX2K from SolidRun, > while current support for FreeBSD is unknown to me .=20 >=20 >=20 =E2=80=A6 forgot to mention 24-coreA-53 Socionext SC0FQAA-B-000 ( = pricerange $466.- w/o RAM) From owner-freebsd-arm@freebsd.org Thu May 14 15:31:11 2020 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 189912F4CF9 for ; Thu, 14 May 2020 15:31:11 +0000 (UTC) (envelope-from dan.kotowski@a9development.com) Received: from mail1.protonmail.ch (mail1.protonmail.ch [185.70.40.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "protonmail.com", Issuer "SwissSign Server Gold CA 2014 - G22" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 49NFqx6sgHz4SZW for ; Thu, 14 May 2020 15:31:09 +0000 (UTC) (envelope-from dan.kotowski@a9development.com) Date: Thu, 14 May 2020 15:30:57 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=a9development.com; s=protonmail; t=1589470263; bh=ofhYdT5PIQbH4QeQ55jX59xV1p53hpCljKyISYDZyAU=; h=Date:To:From:Cc:Reply-To:Subject:In-Reply-To:References:From; b=vvqo/lXJSg56xXSTzKQsIXD8MaY/fzkmGo7kpMPFT8BSWJ2BT1oSEQj8sDJ7ysSKT vd5CpE8oMMARHO6cxMZ/wHdS/ALB7x4ezzRWPr40ezd2+AlVjQBDP82bmMDMmOucGg aqjuFMgaaBC6TbEiceb0Qt07qM5ndXbo/gf0rFl0= To: =?UTF-8?Q?Klaus_K=C3=BCchemann?= From: Dan Kotowski Cc: freebsd-arm@freebsd.org Reply-To: Dan Kotowski Subject: Re: Recommended arm hardware (mostly for compilation)? Message-ID: In-Reply-To: <9E10C464-474F-489A-A667-B263A64E78F2@googlemail.com> References: <1b109252-3232-05c4-e1e0-2fea4739583d@spth.de> <47A5AF8A-1EB9-4721-94D5-B0A0A6FFF69B@unrelenting.technology> <9E10C464-474F-489A-A667-B263A64E78F2@googlemail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Spam-Status: No, score=-1.2 required=7.0 tests=ALL_TRUSTED,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF shortcircuit=no autolearn=disabled version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on mail.protonmail.ch X-Rspamd-Queue-Id: 49NFqx6sgHz4SZW X-Spamd-Bar: ----- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=a9development.com header.s=protonmail header.b=vvqo/lXJ; dmarc=pass (policy=none) header.from=a9development.com; spf=pass (mx1.freebsd.org: domain of dan.kotowski@a9development.com designates 185.70.40.18 as permitted sender) smtp.mailfrom=dan.kotowski@a9development.com X-Spamd-Result: default: False [-5.80 / 15.00]; ARC_NA(0.00)[]; HAS_REPLYTO(0.00)[dan.kotowski@a9development.com]; R_DKIM_ALLOW(-0.20)[a9development.com:s=protonmail]; REPLYTO_EQ_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:185.70.40.0/24]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; MIME_TRACE(0.00)[0:+]; NEURAL_HAM_MEDIUM(-1.00)[-0.999,0]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[a9development.com:+]; RCPT_COUNT_TWO(0.00)[2]; DMARC_POLICY_ALLOW(-0.50)[a9development.com,none]; IP_SCORE(-3.70)[ip: (-9.73), ipnet: 185.70.40.0/24(-4.89), asn: 62371(-3.91), country: CH(0.04)]; FREEMAIL_TO(0.00)[googlemail.com]; RCVD_COUNT_ZERO(0.00)[0]; RCVD_IN_DNSWL_LOW(-0.10)[18.40.70.185.list.dnswl.org : 127.0.5.1]; SUBJECT_ENDS_QUESTION(1.00)[]; RWL_MAILSPIKE_VERYGOOD(0.00)[18.40.70.185.rep.mailspike.net : 127.0.0.19]; ASN(0.00)[asn:62371, ipnet:185.70.40.0/24, country:CH]; MID_RHS_MATCH_FROM(0.00)[]; FROM_EQ_ENVFROM(0.00)[] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 May 2020 15:31:11 -0000 I have a SolidRun HoneyComb workstation board based on the LX2K and can con= firm it's quite powerful, however I have only been able to get Linux-based = systems running - I have not been able to get FreeBSD working, but am worki= ng on it. SolidRun provides all the sources necessary to do so, it's just a= matter of interpreting all the documentation. I'll be posting about that in another thread shortly. Dan Kotowski =E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90 Original Me= ssage =E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90 On Thursday, May 14, 2020 2:33 PM, Klaus K=C3=BCchemann via freebsd-arm wrote: > > > > Am 14.05.2020 um 16:04 schrieb myfreeweb greg@unrelenting.technology: > > On May 14, 2020 1:34:52 PM UTC, Philipp Klaus Krause pkk@spth.de wrote: > > > > > Can you recommend some hardware? > > > > AWS EC2 m6g instances :) > > > > > RockPro64 - hardware seems okay, though only 4 GB of RAM. I've read o= n > > > this list thaat the big/little cores aren't handled well by FreeBSD. > > > > There's no smart scheduler setting that would keep the big cores occupi= ed as much as possible for max performance, yes. > > But if you don't need more parallelism than 2 cores, you can just cpuse= t your workload to the big cores. > > > > > MACCHIATObin - a bit on the expensive side, but still okay and has a = RAM > > > slot. > > > > It's great, it's the cheapest arm64 "Actual PC" you can get. > > > > freebsd-arm@freebsd.org mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-arm > > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org= =E2=80=9C > > If someone=E2=80=99s looking for horsepower between those options, consid= er the LX2K from SolidRun, > while current support for FreeBSD is unknown to me . > > freebsd-arm@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-arm > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" From owner-freebsd-arm@freebsd.org Thu May 14 15:32:29 2020 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id A63542F4DB6 for ; Thu, 14 May 2020 15:32:29 +0000 (UTC) (envelope-from dan.kotowski@a9development.com) Received: from mail-40131.protonmail.ch (mail-40131.protonmail.ch [185.70.40.131]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "protonmail.com", Issuer "SwissSign Server Gold CA 2014 - G22" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 49NFsS73S7z4Sqk for ; Thu, 14 May 2020 15:32:28 +0000 (UTC) (envelope-from dan.kotowski@a9development.com) Date: Thu, 14 May 2020 15:32:13 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=a9development.com; s=protonmail; t=1589470342; bh=5bNXetLU5vEQ5AIBrh1CbLvGPBb+J6uhU3k8WTKtxQ8=; h=Date:To:From:Reply-To:Subject:From; b=FjvPztQsw5KbPFJqzh0wpLIRd995poj5QCaFVQLszixofLzvhDgayh7DNpHptLvTg 8OeSmhvJEprutjmDm5Zck3Qu2IuOnEP6fJf7jleR5ag0VmUlhi/72jJFGO122HdV8Y rQdecnckeRUKa4U63tbRIrrxS8uKhsdOm+lVNJTE= To: "freebsd-arm@freebsd.org" From: Dan Kotowski Reply-To: Dan Kotowski Subject: FreeBSD on Layerscape/QorIQ LX2160X Message-ID: MIME-Version: 1.0 X-Spam-Status: No, score=-1.2 required=7.0 tests=ALL_TRUSTED,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,HTML_MESSAGE shortcircuit=no autolearn=disabled version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on mail.protonmail.ch X-Rspamd-Queue-Id: 49NFsS73S7z4Sqk X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org; dkim=pass header.d=a9development.com header.s=protonmail header.b=FjvPztQs; dmarc=pass (policy=none) header.from=a9development.com; spf=pass (mx1.freebsd.org: domain of dan.kotowski@a9development.com designates 185.70.40.131 as permitted sender) smtp.mailfrom=dan.kotowski@a9development.com X-Spamd-Result: default: False [-6.70 / 15.00]; ARC_NA(0.00)[]; HAS_REPLYTO(0.00)[dan.kotowski@a9development.com]; R_DKIM_ALLOW(-0.20)[a9development.com:s=protonmail]; REPLYTO_EQ_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:185.70.40.0/24:c]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; HAS_PHPMAILER_SIG(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; RCPT_COUNT_ONE(0.00)[1]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; IP_SCORE(-3.70)[ip: (-9.75), ipnet: 185.70.40.0/24(-4.89), asn: 62371(-3.91), country: CH(0.04)]; DKIM_TRACE(0.00)[a9development.com:+]; MIME_BASE64_TEXT(0.10)[]; DMARC_POLICY_ALLOW(-0.50)[a9development.com,none]; TO_DN_EQ_ADDR_ALL(0.00)[]; RCVD_COUNT_ZERO(0.00)[0]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; RWL_MAILSPIKE_VERYGOOD(0.00)[131.40.70.185.rep.mailspike.net : 127.0.0.19]; ASN(0.00)[asn:62371, ipnet:185.70.40.0/24, country:CH]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_IN_DNSWL_LOW(-0.10)[131.40.70.185.list.dnswl.org : 127.0.5.1] Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: base64 X-Content-Filtered-By: Mailman/MimeDel 2.1.33 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 May 2020 15:32:29 -0000 SSdtIHdvbmRlcmluZyBpZiBhbnlib2R5IGtub3dzIG9mIHdvcmsgYmVpbmcgZG9uZSB0byBwb3J0 IEZyZWVCU0QgdG8gdGhlIExheWVyc2NhcGUgcGxhdGZvcm1zPwoKSSBoYXBwZW4gdG8gaGF2ZSBh IFNvbGlkUnVuIEhvbmV5Q29tYiBMWDJLIHdvcmtzdGF0aW9uLCBiYXNlZCBvbiBOWFAncyBMYXll cnNjYXBlIExYMjE2MEEsIG5leHQgdG8gbXkgZGVzayBydW5uaW5nIGEgY3VzdG9tLW11bHRpc3Ry YXBwZWQgRGViaWFuIEplc3NpZSBidWlsZCwgYnV0IHdvdWxkIGxvdmUgdG8gZ2V0IEZyZWVCU0Qg cnVubmluZyBpbnN0ZWFkLiBJIGhhdmUgb25seSBtaW5pbWFsIGV4cGVyaWVuY2Ugd29ya2luZyBk b3duIGluIEJTRCBkcml2ZXIva2VybmVsIGxhbmQgYW5kIG5vIGV4cGVyaWVuY2UgYXQgYWxsIHdp dGggQ3JvY2hldCwgYnV0IHdvdWxkIGxpa2UgdG8gbGVhcm4uIEFuZCB3aGlsZSBJIGNhbm5vdCBh ZmZvcmQgdG8gZG9uYXRlIHRoZSBhY3R1YWwgaGFyZHdhcmUgSSdtIGhhcHB5IHRvIHdvcmsgd2l0 aCBvdGhlcnMgdG8gdGVzdCBidWlsZHMuCgpGb3J0dW5hdGVseSBTb2xpZFJ1biBwcm92aWRlcyB0 aGUgZnVsbCBEZXZpY2VUcmVlIGFuZCBmaXJtd2FyZSBzb3VyY2VzIGluIEdpdEh1YjoKCmh0dHBz Oi8vZ2l0aHViLmNvbS9Tb2xpZFJ1bi9seDIxNjBhX2J1aWxkCgpBbmQgc29tZSBkb2N1bWVudGF0 aW9uIGFib3V0IHRoZSBib2FyZCBmcm9tIHRoZWlyIG1haW4gd2Vic2l0ZToKCmh0dHBzOi8vZGV2 ZWxvcGVyLnNvbGlkLXJ1bi5jb20va25vd2xlZGdlLWJhc2UvaG9uZXljb21iLWx4MmsvCgpodHRw czovL2RldmVsb3Blci5zb2xpZC1ydW4uY29tL2tub3dsZWRnZS1iYXNlL2x4MjE2MGEtY2V4Ny11 c2VyLW1hbnVhbC8KCmh0dHBzOi8vZGV2ZWxvcGVyLnNvbGlkLXJ1bi5jb20va25vd2xlZGdlLWJh c2UvZnJlZWJzZC8KCkdpdmVuIGhvdyBtdWNoIGluZm9ybWF0aW9uIGFuZCBzb3VyY2UgU29saWRS dW4gaGFzIHByb3ZpZGVkIHRoaXMgbWlnaHQgYmUgYSB2ZXJ5IHNpbXBsZSBidWlsZCBhbmQgYm9v dHN0cmFwIHByb2Nlc3MgLSBJIGp1c3QgaGF2ZSBubyBpZGVhIHdoZXJlIHRvIGJlZ2luLiBTb2xp ZFJ1biBoYXMgc29tZSBkb2N1bWVudGF0aW9uIG9uIGJ1aWxkaW5nIGZvciB0aGVpciBBcm1hZGEg QTM4eCBtaWNyby1TT01zOgoKaHR0cHM6Ly9kZXZlbG9wZXIuc29saWQtcnVuLmNvbS9rbm93bGVk Z2UtYmFzZS9mcmVlYnNkLwoKVW5mb3J1bmF0ZWx5IHRoYXQgcmVsaWVzIG9uIEtFUk5DT05GPUFS TUFEQTM4WCBhbmQgSSB0aGluayB0aGF0J3MgZ29pbmcgdG8gbWlzcyBzdXBwb3J0IGZvciBhbGwg dGhlIG5pY2VzdCBwYXJ0cyBvZiB0aGUgTGF5ZXJzY2FwZSAyMTYwWC4KCkRhbiBLb3Rvd3NraQ== From owner-freebsd-arm@freebsd.org Thu May 14 15:43:26 2020 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 141BB2F50F2 for ; Thu, 14 May 2020 15:43:26 +0000 (UTC) (envelope-from mw@semihalf.com) Received: from mail-qv1-xf41.google.com (mail-qv1-xf41.google.com [IPv6:2607:f8b0:4864:20::f41]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 49NG6449njz4TJg for ; Thu, 14 May 2020 15:43:24 +0000 (UTC) (envelope-from mw@semihalf.com) Received: by mail-qv1-xf41.google.com with SMTP id g20so1879541qvb.9 for ; Thu, 14 May 2020 08:43:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=semihalf-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=Tvzr06sYktc4dCkAd407ihfid0MH8RbWuufhFhGhLsg=; b=Xb1WfO5RRJMae/Yo7E2Xhyor4nRHZtp/veJEOhYQnB40SeQFPDW/ygaYcZp/UQpFnS X4AXe9MEu2UKs42it6uot88IXZcQP1RUK1bSnpoT1A51vcukl63euXhdwmkvWHKW/qF3 zg+jEfyr3X1afd7qdNYrWOoQpMZTRB24J59R/RVAJEo+hnj05Mdv9/ZPC+I4C+0lvkoZ 6te/NRA8DplQPjx8h8b8uGHKTtqCcU8hyo6wTcGq9ILq5+mHm1CmsdvKKidoF1U4Vj5q xJb8yu0TZA1s0BNuOtSYkDtm7zknuoazFa+m1blmg5YV0jZbNG24a3Uvcjf/fHZCq0iu lWWQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=Tvzr06sYktc4dCkAd407ihfid0MH8RbWuufhFhGhLsg=; b=GiwKygZ+F8pr6W0gtJ+j6Poytl40eqTTq3dcd20BHivmA6pEww8qr2hFmxJ6uZzOgw hIDXnZ/xmG+gWCN7lOXzbLwIHc9iPdf+U5BtCH0wI1PWQbFbOfjrWIerlBGcZn9pdGC7 UMbZwkaeCPN+qhojhFl9bWzUXZgIi8ZbMfQYFp9WcOpSq3EVxNoOGKKiFUMhPJqo4yAE g4QjnKP5d2zac3lEbpohDk1DB8Z71c2Mq72ZPh5w8rfCZlY09gcW1ALiGKsNn4JqZfR9 P0K1px96J7UZlqlzW/hAlw/n+ap6XQ7barU/djAoEZLqqGUOF6PeM7kjk6xNZI2cVk5p 7meA== X-Gm-Message-State: AOAM532M6pJzyzY7PmYzVwjGFWQGcN3bN7wiJFtCmyX4Q0xPZT529QOP TNJkbTYOvoteTjV0qphVOFO/V7k2h7d9ycnZF6YrHSjM X-Google-Smtp-Source: ABdhPJw65bDe04bbrf64kiVez6DwEIz0GXwJE9rxBMZCnk3XyevWTTYH5P446YPemkugTBQ8CAJsVrccVlnAaLRqru4= X-Received: by 2002:a0c:9d06:: with SMTP id m6mr5284386qvf.167.1589471003619; Thu, 14 May 2020 08:43:23 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Marcin Wojtas Date: Thu, 14 May 2020 17:43:11 +0200 Message-ID: Subject: Re: FreeBSD on Layerscape/QorIQ LX2160X To: Dan Kotowski Cc: "freebsd-arm@freebsd.org" Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Rspamd-Queue-Id: 49NG6449njz4TJg X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=semihalf-com.20150623.gappssmtp.com header.s=20150623 header.b=Xb1WfO5R; dmarc=none; spf=none (mx1.freebsd.org: domain of mw@semihalf.com has no SPF policy when checking 2607:f8b0:4864:20::f41) smtp.mailfrom=mw@semihalf.com X-Spamd-Result: default: False [-2.46 / 15.00]; ARC_NA(0.00)[]; TO_DN_EQ_ADDR_SOME(0.00)[]; R_DKIM_ALLOW(-0.20)[semihalf-com.20150623.gappssmtp.com:s=20150623]; NEURAL_HAM_MEDIUM(-1.00)[-0.995,0]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-arm@freebsd.org]; DMARC_NA(0.00)[semihalf.com]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[semihalf-com.20150623.gappssmtp.com:+]; RCPT_COUNT_TWO(0.00)[2]; RCVD_IN_DNSWL_NONE(0.00)[1.4.f.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.b.8.f.7.0.6.2.list.dnswl.org : 127.0.5.0]; R_SPF_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; IP_SCORE(-0.16)[ip: (-0.00), ipnet: 2607:f8b0::/32(-0.33), asn: 15169(-0.42), country: US(-0.05)]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 May 2020 15:43:26 -0000 Hi Dan, czw., 14 maj 2020 o 17:32 Dan Kotowski napisa=C5=82(a): > > I'm wondering if anybody knows of work being done to port FreeBSD to the = Layerscape platforms? > > I happen to have a SolidRun HoneyComb LX2K workstation, based on NXP's La= yerscape LX2160A, next to my desk running a custom-multistrapped Debian Jes= sie build, but would love to get FreeBSD running instead. I have only minim= al experience working down in BSD driver/kernel land and no experience at a= ll with Crochet, but would like to learn. And while I cannot afford to dona= te the actual hardware I'm happy to work with others to test builds. > > Fortunately SolidRun provides the full DeviceTree and firmware sources in= GitHub: > > https://github.com/SolidRun/lx2160a_build > > And some documentation about the board from their main website: > > https://developer.solid-run.com/knowledge-base/honeycomb-lx2k/ > > https://developer.solid-run.com/knowledge-base/lx2160a-cex7-user-manual/ > > https://developer.solid-run.com/knowledge-base/freebsd/ > > Given how much information and source SolidRun has provided this might be= a very simple build and bootstrap process - I just have no idea where to b= egin. SolidRun has some documentation on building for their Armada A38x mic= ro-SOMs: > > https://developer.solid-run.com/knowledge-base/freebsd/ > > Unforunately that relies on KERNCONF=3DARMADA38X and I think that's going= to miss support for all the nicest parts of the Layerscape 2160X. > The howto is a bit dated. Since about 2 years, Armada 38x has been using the GENERIC config for armv7. Anyway it has nothing in common with the arm64 LS2160X. Best regards, Marcin From owner-freebsd-arm@freebsd.org Thu May 14 15:48:57 2020 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 7DC282F5276 for ; Thu, 14 May 2020 15:48:57 +0000 (UTC) (envelope-from greg@unrelenting.technology) Received: from out0.migadu.com (out0.migadu.com [IPv6:2001:41d0:2:267::]) (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 49NGDR25dWz4TXZ for ; Thu, 14 May 2020 15:48:54 +0000 (UTC) (envelope-from greg@unrelenting.technology) Date: Thu, 14 May 2020 15:48:47 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=unrelenting.technology; s=default; t=1589471326; 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=oQIgNDU+igdw8Oy7p/tAv4NL5mTdtUwjQ926KVLZ/dM=; b=ip5r+uDSqZ0Anj4S5jUQpdgc9LbDuCvGfakT7fMuqBNuxX9LczCgOITnud/tvJKscbNWTv dQPvGkPbSi+9SfqkF7Iyi58j9bISOEbHaaN3Osoc+S1udC3Gd0uFghY2+Ulr2YaoWMLG7d pqojMXZ+A0aZOfCIpPiTSEG6kg8Q6dg= X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers. From: myfreeweb To: Dan Kotowski , "freebsd-arm@freebsd.org" Subject: Re: FreeBSD on Layerscape/QorIQ LX2160X In-Reply-To: References: Message-ID: <72D47662-240E-4851-844A-A4F92F18B3F2@unrelenting.technology> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Spam-Score: -0.10 X-Rspamd-Queue-Id: 49NGDR25dWz4TXZ X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; dkim=pass header.d=unrelenting.technology header.s=default header.b=ip5r+uDS; dmarc=pass (policy=none) header.from=unrelenting.technology; spf=pass (mx1.freebsd.org: domain of greg@unrelenting.technology designates 2001:41d0:2:267:: as permitted sender) smtp.mailfrom=greg@unrelenting.technology X-Spamd-Result: default: False [-0.59 / 15.00]; ARC_NA(0.00)[]; TO_DN_EQ_ADDR_SOME(0.00)[]; R_DKIM_ALLOW(-0.20)[unrelenting.technology:s=default]; NEURAL_HAM_MEDIUM(-0.00)[-0.002,0]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2001:41d0:2:267::]; NEURAL_HAM_LONG(-0.97)[-0.968,0]; MIME_GOOD(-0.10)[text/plain]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[unrelenting.technology:+]; RCPT_COUNT_TWO(0.00)[2]; DMARC_POLICY_ALLOW(-0.50)[unrelenting.technology,none]; RCVD_COUNT_ZERO(0.00)[0]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; IP_SCORE(1.38)[ipnet: 2001:41d0::/32(4.90), asn: 16276(1.98), country: FR(-0.00)]; ASN(0.00)[asn:16276, ipnet:2001:41d0::/32, country:FR]; MID_RHS_MATCH_FROM(0.00)[] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 May 2020 15:48:57 -0000 On May 14, 2020 3:32:13 PM UTC, Dan Kotowski wrote: >I'm wondering if anybody knows of work being done to port FreeBSD to the = Layerscape platforms? > >I happen to have a SolidRun HoneyComb LX2K workstation, based on NXP's La= yerscape LX2160A, next to my desk running a custom-multistrapped Debian Jes= sie build, but would love to get FreeBSD running instead=2E I have only min= imal experience working down in BSD driver/kernel land and no experience at= all with Crochet, but would like to learn=2E And while I cannot afford to = donate the actual hardware I'm happy to work with others to test builds=2E Do not even think about crochet or device trees or any of the embedded stu= ff on such a machine!! ;) Just use the latest UEFI firmware in ACPI mode to boot generic FreeBSD=2E Looking at their ACPI tables, they do finally have PCIe and USB3 as generi= c devices, though oddly not SATA: https://github=2Ecom/SolidRun/edk2-platfo= rms/tree/master-lx2160a/Silicon/NXP/LX2160A/AcpiTables/Dsdt From owner-freebsd-arm@freebsd.org Thu May 14 16:44:33 2020 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 10F632F6615 for ; Thu, 14 May 2020 16:44:33 +0000 (UTC) (envelope-from pkk@spth.de) Received: from mout.kundenserver.de (mout.kundenserver.de [217.72.192.75]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.kundenserver.de", Issuer "TeleSec ServerPass Class 2 CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 49NHSb5CMFz4XZc for ; Thu, 14 May 2020 16:44:31 +0000 (UTC) (envelope-from pkk@spth.de) Received: from [192.168.178.36] ([77.189.89.215]) by mrelayeu.kundenserver.de (mreue109 [212.227.15.183]) with ESMTPSA (Nemesis) id 1N8XHb-1j4DSG0Ge1-014SoL for ; Thu, 14 May 2020 18:44:29 +0200 Subject: Re: Recommended arm hardware (mostly for compilation)? To: freebsd-arm@freebsd.org References: <1b109252-3232-05c4-e1e0-2fea4739583d@spth.de> <47A5AF8A-1EB9-4721-94D5-B0A0A6FFF69B@unrelenting.technology> <9E10C464-474F-489A-A667-B263A64E78F2@googlemail.com> From: Philipp Klaus Krause Autocrypt: addr=pkk@spth.de; prefer-encrypt=mutual; keydata= mQGiBD+wIQ0RBAD5IkcgQQIAPO93xBBvviI0htuoaeb++GqG51BImx+rnWIS+1z+r3y5jQU5 IRYS8eDC3eR5PFtde/f7/3zxaJIB0bgXB1eMPot5CaN7mpUySVNh9bzH/UP7rVH0Ut7Bx/CI 7EXxhvYE23F/TAf+gS4flFqQ/GdK+MME+dg8J5nFbwCg92xq6iuAvyz7vSho9qbKHsCD3AkE AMbuLLBvk4mPvs19aRGZvT/pows1uzkeNq8fpmzvryb4UxUbU89qlNzA2Bg8ztVZGX9x5drb C4tFE29ZFAHn2bojx2ADxG85+2as8yfcz6sPG4HMzeTtugzPGCeRAXaSknZHsw6AC6LrtsEU sjEZMElfvu8uU4dthfhXOIDVNRHmA/446GsHRLosDHFuDjHpBQJPJSBnFDyRSCge2Q0gup96 GGhNc7KkYeIB8Dh7dCN3h5RYXflVTspxmgANUa+RFpL4pynsF16rtkfeh0UR8uLdoaGwMChw GyWIdRhX8MLQ8v3WHPCUrB/1f5xhRypQgF0/c8y4w5BarGQXy7AM0PljBbQxUGhpbGlwcCBL cmF1c2UgKFN0YW5kYXJkc2NobMO8c3NlbCkgPHBra0BzcHRoLmRlPohbBBMRAgAbBQI/sCEN BgsJCAcDAgMVAgMDFgIBAh4BAheAAAoJEG7VFfsbKC6a31wAni0szX2x9jjNqqch2fE5zOkd IJsSAKCuZaayyxtHPb6rpQtbDMUTS7rXe7kCDQQ/sCFjEAgAknletShOrS5UeFH6V09TksPL 5w8S1SaQThvdberD74Uaq5Weoeu5fCzeDlhRvTC+wQFxL5W2wdM3ZhqRpZIri7X3ab/WUsqv 0FCK8LB9HfioafjNg7uQbyUannvyBkj4WAfHrTDgDbNw8EJMehab9MUeCUZEkhXrk9b3rp3r /uoic1pymK0aZX+wUfayXGANAAk75HAruEWxpGObjcJ587tTOsfDAFnJlXKXLVXuqJDSraym ankbEfyX1CmfhetYn+s1fCpAHX/GOIQPEG2BCdeLdy8ApN0l6MIrRkJKbBnvnc8HsUI7Elfu huemyI/Nvhxk5+tuOS5kZBIyZKe8CwADBQf+InHwn00dafe8XNod9jRsHgCqE259ocEiL0Zs rw3NfwbckR6YVGtoovHna6I3+o4F4GPS/869WFw/w1HGGsa9t6SRjWeoH221bxYc+aTstGbA hd9OuDXnXFi9Mokh34cXQexvrVYjfOdbAl9TRezPBRygzr6XvUdUtIpZjZhW0WSdhdF67Obl F+S9kCX7v3Q0kSqnjzk05Qs5kHyaE+7BKiGQhvCz51J++CTCc/g16eOVVabHNLalAEInq1jn jAB15+JxDcA3HFup7+sHkkscAEQPPi8aNnWR32su0w9hfE1qQkvyHhOiPX2GVhm/Lt0C1vGr ZCB9Bve3r8M+Z7uMaohGBBgRAgAGBQI/sCFjAAoJEG7VFfsbKC6aQ4oAnibaEjyIlrRMTmyL K76lqhloK0EPAKCQsgCELscmeJnxyjV1zZt6AJ6ctQ== Message-ID: <6041695d-29c7-3020-d26f-690108cd8bb6@spth.de> Date: Thu, 14 May 2020 18:44:28 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.7.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit X-Provags-ID: V03:K1:IzCMv+TE+1YHlu8QstgVaJPFc8GqeCpQofdfbuLEJEjBC/ChZGe 1MbM90TmgFwDdv84L6h8XfRyEZ4aE58txEEt1RIYujQBIWb0+Hu2cVqG3MGFC/AwaDZ7OWi iU+Zwt03Hhsc/nYhJlXg3Iu7FnpJrtO8EfPZLZElSodZF3edi7Iu7IaXgZMg7JNT4yfPw4s 4Pc5UhSobyDOaxlozVTFw== X-Spam-Flag: NO X-UI-Out-Filterresults: notjunk:1;V03:K0:RVeSgdR3Sws=:vJKdtP7wsGdxOFf5oLvZT3 0HKKF/DuASsslqMljve1SmSdCRTsGo5z4w3p+11NEhCT6j8CNea/KOX1Fq0OhzZMjtnVjdJjV n5j7ScsVtJuR2c3tvFppfECoZGDQYre/muVmktMsR9xG6zYfh51xFWB2QR+KJSdf2cXvopw+8 tjB2jYfmrLvZS9DHhvclpZkLag9DXsh+WHmevaTVcurA4DqF3Rdhg5KIMKMbJEYM6p1luIVqi iJieM3Orbb7nCjKVy0xyqycVTPYIJaRRwKKDjT6fxW7fLkPqZKdJhrj+ThbsQBoIvuPK/YSlN T1UBQUYizIEkcLz1eghbFbPv3LPprIyaFIkQ4P9UudiB0oWV40YaLzUC6rZeDH9Uf975uL5is QVI4I6dZXeI5/N59BQQi5FtTl/DWTs8ryF3zQ4LjMoO+wCO/HKEqu2Qye5ABOle3pgue+VFf4 N+0iIoDFLKH3UOjI7LQ+cuiKHxOK6YG52tvCGR61fX1AKyKiiHiNf+gJdN1QSvKWciZaG7WK1 0yy8m8UPPxEYZwyvQnkmZfqfwu0L+bXjVYp90Al4TatPBNmB+2UtLJU2GAv/94Q+l5EuM/4uT JnQ4D72qUBBDpWs7a9EsiojhqUfjkg85oyNQrjBNt+6ad0ciFlidkBVm3pu147bOw5qCU4dek P/heZVElEelI1Le8ZjV6ib8/+nMjC838/5hTFBW/u8P1ukHtXO6voQsOY5l09YSb8n/bYzt8P RLLsfZM/vXdDFHb0d4mXOp3HYpleh5Qc+hFjG/lOUCmkzbEO+arGgyTRYSDvJyqdH+yzjl559 q0/gA4Rbz72IyDAypAfamgdB3FAnKTA7Mma/DkksHcRD4KeA1s= X-Rspamd-Queue-Id: 49NHSb5CMFz4XZc X-Spamd-Bar: ++++ Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of pkk@spth.de has no SPF policy when checking 217.72.192.75) smtp.mailfrom=pkk@spth.de X-Spamd-Result: default: False [4.09 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; RWL_MAILSPIKE_NEUTRAL(0.00)[75.192.72.217.rep.mailspike.net : 127.0.0.13]; RECEIVED_SPAMHAUS_PBL(0.00)[215.89.189.77.khpj7ygk5idzvmvt5x4ziurxhy.zen.dq.spamhaus.net : 127.0.0.10]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; IP_SCORE(0.34)[ip: (-0.56), ipnet: 217.72.192.0/20(0.31), asn: 8560(2.00), country: DE(-0.02)]; MIME_GOOD(-0.10)[text/plain]; MIME_TRACE(0.00)[0:+]; PREVIOUSLY_DELIVERED(0.00)[freebsd-arm@freebsd.org]; AUTH_NA(1.00)[]; RCPT_COUNT_ONE(0.00)[1]; NEURAL_SPAM_MEDIUM(0.85)[0.845,0]; TO_DN_NONE(0.00)[]; NEURAL_SPAM_LONG(1.00)[0.997,0]; RCVD_IN_DNSWL_NONE(0.00)[75.192.72.217.list.dnswl.org : 127.0.5.0]; R_SPF_NA(0.00)[]; DMARC_NA(0.00)[spth.de]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; SUBJECT_ENDS_QUESTION(1.00)[]; ASN(0.00)[asn:8560, ipnet:217.72.192.0/20, country:DE]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_TLS_ALL(0.00)[]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 May 2020 16:44:33 -0000 Am 14.05.20 um 17:30 schrieb Dan Kotowski: > I have a SolidRun HoneyComb workstation board based on the LX2K and can confirm it's quite powerful, […] Looking at the specifications, I haven't yet found anything on how much energy those LX2K or MACCHIATObin boards need and what kind of power supply would be necessary for a minimal system. From owner-freebsd-arm@freebsd.org Thu May 14 20:44:55 2020 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 03C092DF2AB for ; Thu, 14 May 2020 20:44:55 +0000 (UTC) (envelope-from crowston@protonmail.com) Received: from mail-40131.protonmail.ch (mail-40131.protonmail.ch [185.70.40.131]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "protonmail.com", Issuer "SwissSign Server Gold CA 2014 - G22" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 49NNnx53kcz3QNV for ; Thu, 14 May 2020 20:44:53 +0000 (UTC) (envelope-from crowston@protonmail.com) Date: Thu, 14 May 2020 20:44:45 +0000 To: Philipp Klaus Krause From: Robert Crowston Cc: "freebsd-arm@freebsd.org" Reply-To: Robert Crowston Subject: Re: Recommended arm hardware (mostly for compilation)? Message-ID: <7wDQBtxlTSCZJ35vc5uLkFgSsm-YeZS3l14XADTshLjgtE8mHx39CmQlzI866jWt9KuFl4CprIRIvqX924kkZ-rLWLkOdNU8Qwxnf3UhxQw=@protonmail.com> In-Reply-To: <1b109252-3232-05c4-e1e0-2fea4739583d@spth.de> References: <1b109252-3232-05c4-e1e0-2fea4739583d@spth.de> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Spam-Status: No, score=-1.2 required=7.0 tests=ALL_TRUSTED,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM shortcircuit=no autolearn=disabled version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on mail.protonmail.ch X-Rspamd-Queue-Id: 49NNnx53kcz3QNV X-Spamd-Bar: -- X-Spamd-Result: default: False [-2.10 / 15.00]; TO_DN_EQ_ADDR_SOME(0.00)[]; HAS_REPLYTO(0.00)[crowston@protonmail.com]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:185.70.40.0/24]; FREEMAIL_FROM(0.00)[protonmail.com]; DKIM_TRACE(0.00)[protonmail.com:+]; RCPT_COUNT_TWO(0.00)[2]; DMARC_POLICY_ALLOW(-0.50)[protonmail.com,quarantine]; RCVD_COUNT_ZERO(0.00)[0]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; SUBJECT_ENDS_QUESTION(1.00)[]; FREEMAIL_ENVFROM(0.00)[protonmail.com]; IP_SCORE(0.00)[ip: (-9.74), ipnet: 185.70.40.0/24(-4.89), asn: 62371(-3.91), country: CH(0.04)]; MID_RHS_MATCH_FROM(0.00)[]; ASN(0.00)[asn:62371, ipnet:185.70.40.0/24, country:CH]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-0.999,0]; R_DKIM_ALLOW(-0.20)[protonmail.com:s=protonmail]; REPLYTO_EQ_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; FREEMAIL_REPLYTO(0.00)[protonmail.com]; IP_SCORE_FREEMAIL(0.00)[]; RCVD_IN_DNSWL_LOW(-0.10)[131.40.70.185.list.dnswl.org : 127.0.5.1]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RWL_MAILSPIKE_VERYGOOD(0.00)[131.40.70.185.rep.mailspike.net : 127.0.0.19] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 May 2020 20:44:55 -0000 > (how does OpenBSD manage?) Instead of using uboot, I understand OpenBSD uses TianoCore as a UEFI emula= tion. Again, from what I understand, this does a large part of the hardware= initialization for them. For example, their PCI-e driver for the Rpi4 is a= work of simplicity. What I have hacked together thus far for FreeBSD has b= een quite the opposite. Their approach may be more sensible -- after all, u= boot is GPL'd so we don't win anything licence-wise from it. On the question itself, I wonder if anyone has tried running FreeBSD on Ama= zon's Graviton2 architecture? =E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90 Original Me= ssage =E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90 On Thursday, 14 May 2020 14:34, Philipp Klaus Krause wrote: > I'm considering to add a FreeBSD arm machine to the Small Device C > Compiler (SDCC) compile farm. The goal would be to have another arm > machine in the farm (for redundancy in case we need to drop the current > GNU/Linux arm machine, which ) and a FreeBSD machine (to allow us to > promote FreeBSD to an officially supported platform for SDCC). Its task > would be daily compilation of SDCC snapshots and running regression > tests (i.e. mostly compiling small test programs with SDCC and running > the binaries on emulators). > > Can you recommend some hardware? > > A RasPi 3B would probably a bit too weak (I have one and tried FreeBSD > 12 on it; the 1GB RAM limit is an issue for this task - in particular it > makes parallel compilation impossible); there currently is some RasPi > running GNU/Linux in the farm and it barely keeps up with the load. > > So I'm looking for something with sufficient RAM that is likely to be > well-supported by FreeBSD for some years. > > So far, I've considered: > > RasPi 4B - hardware seems ok, though FreeBSD support is apaprently > lacking due to lack of documentation (how does OpenBSD manage?), and > only 4 GB of RAM. > > RockPro64 - hardware seems okay, though only 4 GB of RAM. I've read on > this list thaat the big/little cores aren't handled well by FreeBSD. > > Pine H64 - small RAM (3GB), rather new. > > MACCHIATObin - a bit on the expensive side, but still okay and has a RAM > slot. > > Which of these is likely to work out-of-the-box in the FreeBSD 13 > release? Any recommendations on which hardware to get? > > freebsd-arm@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-arm > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" From owner-freebsd-arm@freebsd.org Thu May 14 20:55:48 2020 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id E4E652DF8B7 for ; Thu, 14 May 2020 20:55:48 +0000 (UTC) (envelope-from tuexen@freebsd.org) Received: from drew.franken.de (drew.ipv6.franken.de [IPv6:2001:638:a02:a001:20e:cff:fe4a:feaa]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.franken.de", Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 49NP2X2vLPz3R45 for ; Thu, 14 May 2020 20:55:47 +0000 (UTC) (envelope-from tuexen@freebsd.org) Received: from [IPv6:2a02:8109:1140:c3d:4136:86f2:7b59:6ff0] (unknown [IPv6:2a02:8109:1140:c3d:4136:86f2:7b59:6ff0]) (Authenticated sender: macmic) by drew.franken.de (Postfix) with ESMTPSA id 71B807220CCE9; Thu, 14 May 2020 22:55:40 +0200 (CEST) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.80.23.2.2\)) Subject: Re: Recommended arm hardware (mostly for compilation)? From: Michael Tuexen In-Reply-To: <7wDQBtxlTSCZJ35vc5uLkFgSsm-YeZS3l14XADTshLjgtE8mHx39CmQlzI866jWt9KuFl4CprIRIvqX924kkZ-rLWLkOdNU8Qwxnf3UhxQw=@protonmail.com> Date: Thu, 14 May 2020 22:55:39 +0200 Cc: Philipp Klaus Krause , "freebsd-arm@freebsd.org" Content-Transfer-Encoding: quoted-printable Message-Id: <756A264F-22EF-4B1C-BBB2-5160AC7FA03B@freebsd.org> References: <1b109252-3232-05c4-e1e0-2fea4739583d@spth.de> <7wDQBtxlTSCZJ35vc5uLkFgSsm-YeZS3l14XADTshLjgtE8mHx39CmQlzI866jWt9KuFl4CprIRIvqX924kkZ-rLWLkOdNU8Qwxnf3UhxQw=@protonmail.com> To: Robert Crowston X-Mailer: Apple Mail (2.3608.80.23.2.2) X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED,BAYES_00 autolearn=disabled version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on mail-n.franken.de X-Rspamd-Queue-Id: 49NP2X2vLPz3R45 X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-1.29 / 15.00]; local_wl_from(0.00)[freebsd.org]; NEURAL_HAM_MEDIUM(-0.30)[-0.303,0]; NEURAL_HAM_LONG(-0.99)[-0.989,0]; ASN(0.00)[asn:680, ipnet:2001:638::/32, country:DE] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 May 2020 20:55:49 -0000 > On 14. May 2020, at 22:44, Robert Crowston via freebsd-arm = wrote: >=20 >> (how does OpenBSD manage?) >=20 > Instead of using uboot, I understand OpenBSD uses TianoCore as a UEFI = emulation. Again, from what I understand, this does a large part of the = hardware initialization for them. For example, their PCI-e driver for = the Rpi4 is a work of simplicity. What I have hacked together thus far = for FreeBSD has been quite the opposite. Their approach may be more = sensible -- after all, uboot is GPL'd so we don't win anything = licence-wise from it. >=20 > On the question itself, I wonder if anyone has tried running FreeBSD = on Amazon's Graviton2 architecture? https://dmesgd.nycbug.org/index.cgi?do=3Dview&id=3D5478 https://dmesgd.nycbug.org/index.cgi?do=3Dview&id=3D5481 Best regards Michael >=20 > =E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90 = Original Message =E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2= =80=90 > On Thursday, 14 May 2020 14:34, Philipp Klaus Krause = wrote: >=20 >> I'm considering to add a FreeBSD arm machine to the Small Device C >> Compiler (SDCC) compile farm. The goal would be to have another arm >> machine in the farm (for redundancy in case we need to drop the = current >> GNU/Linux arm machine, which ) and a FreeBSD machine (to allow us to >> promote FreeBSD to an officially supported platform for SDCC). Its = task >> would be daily compilation of SDCC snapshots and running regression >> tests (i.e. mostly compiling small test programs with SDCC and = running >> the binaries on emulators). >>=20 >> Can you recommend some hardware? >>=20 >> A RasPi 3B would probably a bit too weak (I have one and tried = FreeBSD >> 12 on it; the 1GB RAM limit is an issue for this task - in particular = it >> makes parallel compilation impossible); there currently is some RasPi >> running GNU/Linux in the farm and it barely keeps up with the load. >>=20 >> So I'm looking for something with sufficient RAM that is likely to be >> well-supported by FreeBSD for some years. >>=20 >> So far, I've considered: >>=20 >> RasPi 4B - hardware seems ok, though FreeBSD support is apaprently >> lacking due to lack of documentation (how does OpenBSD manage?), and >> only 4 GB of RAM. >>=20 >> RockPro64 - hardware seems okay, though only 4 GB of RAM. I've read = on >> this list thaat the big/little cores aren't handled well by FreeBSD. >>=20 >> Pine H64 - small RAM (3GB), rather new. >>=20 >> MACCHIATObin - a bit on the expensive side, but still okay and has a = RAM >> slot. >>=20 >> Which of these is likely to work out-of-the-box in the FreeBSD 13 >> release? Any recommendations on which hardware to get? >>=20 >> freebsd-arm@freebsd.org mailing list >> https://lists.freebsd.org/mailman/listinfo/freebsd-arm >> To unsubscribe, send any mail to = "freebsd-arm-unsubscribe@freebsd.org" >=20 >=20 > _______________________________________________ > freebsd-arm@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-arm > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" From owner-freebsd-arm@freebsd.org Thu May 14 21:15:23 2020 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 44F0E2E01E2 for ; Thu, 14 May 2020 21:15:23 +0000 (UTC) (envelope-from maciphone2@googlemail.com) Received: from mail-wr1-x42e.google.com (mail-wr1-x42e.google.com [IPv6:2a00:1450:4864:20::42e]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 49NPT61cpWz3xSK for ; Thu, 14 May 2020 21:15:21 +0000 (UTC) (envelope-from maciphone2@googlemail.com) Received: by mail-wr1-x42e.google.com with SMTP id e1so609141wrt.5 for ; Thu, 14 May 2020 14:15:21 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:content-transfer-encoding:mime-version :subject:date:references:to:in-reply-to:message-id; bh=9DmT0WM1n6rbG6iNGloX0UuTxG0xQy5CRxwsgkE++aE=; b=fNA4tVKV3b3v+UeTZBFyHgv7zGbetSca/HEmNLSitshWG2XTRaX24e7ieg52Rc3336 GuUb5jDjQ4pFaameC/ssLspl/oV4ZLmhAC6nzIhey1m8UnHOxd4l6UveGsUcI3f9pNqU fkNiuwh46LwiRXTxefgS1ipF/Hf14VGuDAKCAnuHi49t/kDPvzk6W8/MM4IOyw4rn3/F oGCCwKnC47oZKwKBMMiudkqxAQZTD8/eQfZJd0bXNWa0thxHHRafBXIKgZsNuoGMDo38 biSYroEsXyWexySCqe93HwUGAu8sHFGgYCnZ50Nu4Xnr8zZuVoiyLsQuHUvuazk2PHNV p2OA== X-Gm-Message-State: AOAM530G1sRPLEIUQKVsnMZ76SzPFA62zXEZRiYOvgMzz9Ldxqi+J6SW +VkH2twQMXwk4IFhcdC0L4rBAbSM X-Google-Smtp-Source: ABdhPJyesSIa6MPtAzgeBMKoK5czu5B0Mb+aeZFgKs+vgBzsl9pAQAQmlHpCWJhpff1WCU1qVHy70g== X-Received: by 2002:a5d:480d:: with SMTP id l13mr384055wrq.49.1589490919497; Thu, 14 May 2020 14:15:19 -0700 (PDT) Received: from [192.168.1.167] ([46.114.104.254]) by smtp.googlemail.com with ESMTPSA id h74sm308261wrh.76.2020.05.14.14.15.18 for (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Thu, 14 May 2020 14:15:18 -0700 (PDT) From: =?utf-8?Q?Klaus_K=C3=BCchemann?= Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.80.23.2.2\)) Subject: Re: Recommended arm hardware (mostly for compilation)? Date: Thu, 14 May 2020 23:15:17 +0200 References: <1b109252-3232-05c4-e1e0-2fea4739583d@spth.de> <7wDQBtxlTSCZJ35vc5uLkFgSsm-YeZS3l14XADTshLjgtE8mHx39CmQlzI866jWt9KuFl4CprIRIvqX924kkZ-rLWLkOdNU8Qwxnf3UhxQw=@protonmail.com> To: freebsd-arm@freebsd.org In-Reply-To: <7wDQBtxlTSCZJ35vc5uLkFgSsm-YeZS3l14XADTshLjgtE8mHx39CmQlzI866jWt9KuFl4CprIRIvqX924kkZ-rLWLkOdNU8Qwxnf3UhxQw=@protonmail.com> Message-Id: X-Mailer: Apple Mail (2.3608.80.23.2.2) X-Rspamd-Queue-Id: 49NPT61cpWz3xSK X-Spamd-Bar: - X-Spamd-Result: default: False [-1.50 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36]; FREEMAIL_FROM(0.00)[googlemail.com]; TO_DN_NONE(0.00)[]; MV_CASE(0.50)[]; RCVD_COUNT_THREE(0.00)[3]; DKIM_TRACE(0.00)[googlemail.com:+]; DMARC_POLICY_ALLOW(-0.50)[googlemail.com,quarantine]; RECEIVED_SPAMHAUS_PBL(0.00)[254.104.114.46.khpj7ygk5idzvmvt5x4ziurxhy.zen.dq.spamhaus.net : 127.0.0.11]; FROM_EQ_ENVFROM(0.00)[]; SUBJECT_ENDS_QUESTION(1.00)[]; FREEMAIL_ENVFROM(0.00)[googlemail.com]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; MID_RHS_MATCH_FROM(0.00)[]; DWL_DNSWL_NONE(0.00)[googlemail.com.dwl.dnswl.org : 127.0.5.0]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; R_DKIM_ALLOW(-0.20)[googlemail.com:s=20161025]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-arm@freebsd.org]; IP_SCORE_FREEMAIL(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; MIME_TRACE(0.00)[0:+]; RCVD_IN_DNSWL_NONE(0.00)[e.2.4.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.5.4.1.0.0.a.2.list.dnswl.org : 127.0.5.0]; IP_SCORE(0.00)[ip: (-9.08), ipnet: 2a00:1450::/32(-2.27), asn: 15169(-0.42), country: US(-0.05)]; RCVD_TLS_ALL(0.00)[] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 May 2020 21:15:23 -0000 > Am 14.05.2020 um 22:44 schrieb Robert Crowston via freebsd-arm = : >=20 >> (how does OpenBSD manage?) >=20 > =E2=80=A6...For example, their PCI-e driver for the Rpi4 is a work of = simplicity. =E2=80=A6=E2=80=A6. > =E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90 = Original Message =E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2= =80=90 OpenBSD`s PCI-e driver targets DeviceTree in UEFI, PCI-e itself is not exposed in Uefi/ACPI for the RPI4 . From owner-freebsd-arm@freebsd.org Thu May 14 21:26:50 2020 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id C7D3A2E0663 for ; Thu, 14 May 2020 21:26:50 +0000 (UTC) (envelope-from crowston@protonmail.com) Received: from mail2.protonmail.ch (mail2.protonmail.ch [185.70.40.22]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "protonmail.com", Issuer "SwissSign Server Gold CA 2014 - G22" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 49NPkK4gv5z3y27 for ; Thu, 14 May 2020 21:26:49 +0000 (UTC) (envelope-from crowston@protonmail.com) Date: Thu, 14 May 2020 21:26:39 +0000 To: =?UTF-8?Q?Klaus_K=C3=BCchemann?= From: Robert Crowston Cc: "freebsd-arm@freebsd.org" Reply-To: Robert Crowston Subject: Re: Recommended arm hardware (mostly for compilation)? Message-ID: In-Reply-To: References: <1b109252-3232-05c4-e1e0-2fea4739583d@spth.de> <7wDQBtxlTSCZJ35vc5uLkFgSsm-YeZS3l14XADTshLjgtE8mHx39CmQlzI866jWt9KuFl4CprIRIvqX924kkZ-rLWLkOdNU8Qwxnf3UhxQw=@protonmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Spam-Status: No, score=-1.2 required=7.0 tests=ALL_TRUSTED,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM shortcircuit=no autolearn=disabled version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on mail.protonmail.ch X-Rspamd-Queue-Id: 49NPkK4gv5z3y27 X-Spamd-Bar: -- X-Spamd-Result: default: False [-2.10 / 15.00]; TO_DN_EQ_ADDR_SOME(0.00)[]; HAS_REPLYTO(0.00)[crowston@protonmail.com]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:185.70.40.0/24]; FREEMAIL_FROM(0.00)[protonmail.com]; DKIM_TRACE(0.00)[protonmail.com:+]; RCPT_COUNT_TWO(0.00)[2]; DMARC_POLICY_ALLOW(-0.50)[protonmail.com,quarantine]; FREEMAIL_TO(0.00)[googlemail.com]; RCVD_COUNT_ZERO(0.00)[0]; RCVD_IN_DNSWL_LOW(-0.10)[22.40.70.185.list.dnswl.org : 127.0.5.1]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[protonmail.com]; FROM_EQ_ENVFROM(0.00)[]; ASN(0.00)[asn:62371, ipnet:185.70.40.0/24, country:CH]; MID_RHS_MATCH_FROM(0.00)[]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-0.999,0]; R_DKIM_ALLOW(-0.20)[protonmail.com:s=protonmail]; REPLYTO_EQ_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; FREEMAIL_REPLYTO(0.00)[protonmail.com]; IP_SCORE_FREEMAIL(0.00)[]; SUBJECT_ENDS_QUESTION(1.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; IP_SCORE(0.00)[ip: (-9.74), ipnet: 185.70.40.0/24(-4.89), asn: 62371(-3.91), country: CH(0.04)]; RWL_MAILSPIKE_POSSIBLE(0.00)[22.40.70.185.rep.mailspike.net : 127.0.0.17] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 May 2020 21:26:50 -0000 What I mean is, and I don't know the detail of what happens in TianoCore, b= ut it seems a lot of the device initialization (setting up the right values= in the registers on the hardware) is done before the device is passed to O= penBSD. That's not a criticism -- it's probably the right way to go. =E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90 Original Me= ssage =E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90 On Thursday, 14 May 2020 22:15, Klaus K=C3=BCchemann via freebsd-arm wrote: > > > > Am 14.05.2020 um 22:44 schrieb Robert Crowston via freebsd-arm freebsd-= arm@freebsd.org: > > > > > (how does OpenBSD manage?) > > > > =E2=80=A6...For example, their PCI-e driver for the Rpi4 is a work of s= implicity. =E2=80=A6=E2=80=A6. > > =E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90 Origina= l Message =E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80= =90 > > OpenBSD`s PCI-e driver targets DeviceTree in UEFI, > PCI-e itself is not exposed in Uefi/ACPI for the RPI4 . > > freebsd-arm@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-arm > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" From owner-freebsd-arm@freebsd.org Thu May 14 21:48:03 2020 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 6A24E2E142D for ; Thu, 14 May 2020 21:48:03 +0000 (UTC) (envelope-from maciphone2@googlemail.com) Received: from mail-wr1-x444.google.com (mail-wr1-x444.google.com [IPv6:2a00:1450:4864:20::444]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 49NQBp5QNqz40R8 for ; Thu, 14 May 2020 21:48:02 +0000 (UTC) (envelope-from maciphone2@googlemail.com) Received: by mail-wr1-x444.google.com with SMTP id h17so729829wrc.8 for ; Thu, 14 May 2020 14:48:02 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:content-transfer-encoding:mime-version :subject:date:references:to:in-reply-to:message-id; bh=h4xVAAyW8WYxVhWCHPfDu/r13V6J8aJD4L9UPcCv498=; b=NJ7v5+PWGlmDCTMjSphjjRD9MoJApNkMAJB3cQiN+bhktxvEgkjpI8zYU2KBggSUZE 19kHR0YApkJxE65mbFv5eq7Txb1w230TF9svtzVz8Gy98WTAZCQfHstMYjsmPjoXLCPS X3tH6lxG1mJXlVYfcHwQexR6W9xtPSkbG7anpYxcXA3gQF047/PuLwdgGZx6yNgVh42z 13eJTXlO83K2m0IbBx+b+5X2XF4jQEeXL8u1gH1fwK8NMMVGBc/tbNvKU4RgijMFOeeR dnLAVNKAdPrVKEW9PrOqAhpQbgp6e/sRrg3LamZsmxzpxrcrzPqtYdwnRVoUHjG8epAK 3hyQ== X-Gm-Message-State: AOAM533og0ZWRwvvLWhGvsO9fQv+nQxLJKefeh1bqY5Q/+16uY0JybNm A01Rxeur1oufJHZ9jAbZbjLZWpll X-Google-Smtp-Source: ABdhPJy537uPmn4ImrGdsRpE2dIsACNuNu7FtKIvlt9O9cgzSb68WIPFEWAPS1942OF5CaU2+EKKoA== X-Received: by 2002:a5d:438e:: with SMTP id i14mr484133wrq.413.1589492881254; Thu, 14 May 2020 14:48:01 -0700 (PDT) Received: from [192.168.1.167] ([46.114.104.254]) by smtp.googlemail.com with ESMTPSA id m1sm447606wrx.44.2020.05.14.14.47.59 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Thu, 14 May 2020 14:48:00 -0700 (PDT) From: =?utf-8?Q?Klaus_K=C3=BCchemann?= Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.80.23.2.2\)) Subject: Re: Recommended arm hardware (mostly for compilation)? Date: Thu, 14 May 2020 23:47:58 +0200 References: <1b109252-3232-05c4-e1e0-2fea4739583d@spth.de> <7wDQBtxlTSCZJ35vc5uLkFgSsm-YeZS3l14XADTshLjgtE8mHx39CmQlzI866jWt9KuFl4CprIRIvqX924kkZ-rLWLkOdNU8Qwxnf3UhxQw=@protonmail.com> To: Robert Crowston , freebsd-arm@freebsd.org In-Reply-To: Message-Id: <3743452C-EA4D-4277-AEF9-7A18074481AF@googlemail.com> X-Mailer: Apple Mail (2.3608.80.23.2.2) X-Rspamd-Queue-Id: 49NQBp5QNqz40R8 X-Spamd-Bar: - X-Spamd-Result: default: False [-1.47 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36]; FREEMAIL_FROM(0.00)[googlemail.com]; MV_CASE(0.50)[]; RCVD_COUNT_THREE(0.00)[3]; DKIM_TRACE(0.00)[googlemail.com:+]; RCPT_COUNT_TWO(0.00)[2]; DMARC_POLICY_ALLOW(-0.50)[googlemail.com,quarantine]; FREEMAIL_TO(0.00)[protonmail.com]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; SUBJECT_ENDS_QUESTION(1.00)[]; FREEMAIL_ENVFROM(0.00)[googlemail.com]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; MID_RHS_MATCH_FROM(0.00)[]; DWL_DNSWL_NONE(0.00)[googlemail.com.dwl.dnswl.org : 127.0.5.0]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.97)[-0.974,0]; R_DKIM_ALLOW(-0.20)[googlemail.com:s=20161025]; RECEIVED_SPAMHAUS_PBL(0.00)[254.104.114.46.khpj7ygk5idzvmvt5x4ziurxhy.zen.dq.spamhaus.net : 127.0.0.11]; FROM_HAS_DN(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-arm@freebsd.org]; IP_SCORE_FREEMAIL(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[4.4.4.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.5.4.1.0.0.a.2.list.dnswl.org : 127.0.5.0]; IP_SCORE(0.00)[ip: (2.70), ipnet: 2a00:1450::/32(-2.27), asn: 15169(-0.42), country: US(-0.05)]; RCVD_TLS_ALL(0.00)[] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 May 2020 21:48:03 -0000 > =E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90 = Original Message =E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2= =80=90 > On Thursday, 14 May 2020 22:15, Klaus K=C3=BCchemann via freebsd-arm = wrote: >=20 >>=20 >>=20 >>> Am 14.05.2020 um 22:44 schrieb Robert Crowston via freebsd-arm = freebsd-arm@freebsd.org: >>>=20 >>>> (how does OpenBSD manage?) >>>=20 >>> =E2=80=A6...For example, their PCI-e driver for the Rpi4 is a work = of simplicity. =E2=80=A6=E2=80=A6. >>> =E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90 = Original Message =E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2= =80=90 >>=20 >> OpenBSD`s PCI-e driver targets DeviceTree in UEFI, >> PCI-e itself is not exposed in Uefi/ACPI for the RPI4 . > Am 14.05.2020 um 23:26 schrieb Robert Crowston = : >=20 > What I mean is, and I don't know the detail of what happens in = TianoCore, but it seems a lot of the device initialization (setting up = the right values in the registers on the hardware) is done before the = device is passed to OpenBSD. That's not a criticism -- it's probably the = right way to go. If we want to get FreeBSD to boot in ACPI-mode(tianocore/edkII) on rpi4 = we probably will have quite nothing to do with=20 PCI-e itself to get access to the USB-bus. genet is already implemented in rpi4-uefi in Version 1.13 . What we have to fix/ implement is our generic_xhci - driver, where = something like INIT=20 fails to dma =E2=80=A6.=20 kls From owner-freebsd-arm@freebsd.org Sat May 16 06:24:15 2020 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 2F1DC2E71E4 for ; Sat, 16 May 2020 06:24:15 +0000 (UTC) (envelope-from jmg@gold.funkthat.com) Received: from gold.funkthat.com (gold.funkthat.com [IPv6:2001:470:800b::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "gate2.funkthat.com", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 49PFbw1mFtz411s for ; Sat, 16 May 2020 06:24:12 +0000 (UTC) (envelope-from jmg@gold.funkthat.com) Received: from gold.funkthat.com (localhost [127.0.0.1]) by gold.funkthat.com (8.15.2/8.15.2) with ESMTPS id 04G5C8lS091885 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 15 May 2020 22:12:08 -0700 (PDT) (envelope-from jmg@gold.funkthat.com) Received: (from jmg@localhost) by gold.funkthat.com (8.15.2/8.15.2/Submit) id 04G5C782091884; Fri, 15 May 2020 22:12:07 -0700 (PDT) (envelope-from jmg) Date: Fri, 15 May 2020 22:12:07 -0700 From: John-Mark Gurney To: myfreeweb Cc: Dan Kotowski , "freebsd-arm@freebsd.org" Subject: Re: FreeBSD on Layerscape/QorIQ LX2160X Message-ID: <20200516051207.GT4213@funkthat.com> Mail-Followup-To: myfreeweb , Dan Kotowski , "freebsd-arm@freebsd.org" References: <72D47662-240E-4851-844A-A4F92F18B3F2@unrelenting.technology> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <72D47662-240E-4851-844A-A4F92F18B3F2@unrelenting.technology> X-Operating-System: FreeBSD 11.3-STABLE amd64 X-PGP-Fingerprint: D87A 235F FB71 1F3F 55B7 ED9B D5FF 5A51 C0AC 3D65 X-Files: The truth is out there X-URL: https://www.funkthat.com/ X-Resume: https://www.funkthat.com/~jmg/resume.html X-TipJar: bitcoin:13Qmb6AeTgQecazTWph4XasEsP7nGRbAPE X-to-the-FBI-CIA-and-NSA: HI! HOW YA DOIN? can i haz chizburger? User-Agent: Mutt/1.6.1 (2016-04-27) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (gold.funkthat.com [127.0.0.1]); Fri, 15 May 2020 22:12:08 -0700 (PDT) X-Rspamd-Queue-Id: 49PFbw1mFtz411s X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of jmg@gold.funkthat.com has no SPF policy when checking 2001:470:800b::2) smtp.mailfrom=jmg@gold.funkthat.com X-Spamd-Result: default: False [-2.25 / 15.00]; ARC_NA(0.00)[]; TO_DN_EQ_ADDR_SOME(0.00)[]; RCVD_TLS_ALL(0.00)[]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; TO_DN_SOME(0.00)[]; IP_SCORE(-1.46)[ipnet: 2001:470::/32(-4.10), asn: 6939(-3.15), country: US(-0.05)]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[funkthat.com]; AUTH_NA(1.00)[]; NEURAL_HAM_LONG(-1.00)[-0.997,0]; TO_MATCH_ENVRCPT_SOME(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-0.997,0]; R_SPF_NA(0.00)[]; FORGED_SENDER(0.30)[jmg@funkthat.com,jmg@gold.funkthat.com]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:6939, ipnet:2001:470::/32, country:US]; FROM_NEQ_ENVFROM(0.00)[jmg@funkthat.com,jmg@gold.funkthat.com]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 16 May 2020 06:24:15 -0000 myfreeweb wrote this message on Thu, May 14, 2020 at 15:48 +0000: > > > On May 14, 2020 3:32:13 PM UTC, Dan Kotowski wrote: > >I'm wondering if anybody knows of work being done to port FreeBSD to the Layerscape platforms? > > > >I happen to have a SolidRun HoneyComb LX2K workstation, based on NXP's Layerscape LX2160A, next to my desk running a custom-multistrapped Debian Jessie build, but would love to get FreeBSD running instead. I have only minimal experience working down in BSD driver/kernel land and no experience at all with Crochet, but would like to learn. And while I cannot afford to donate the actual hardware I'm happy to work with others to test builds. > > Do not even think about crochet or device trees or any of the embedded stuff on such a machine!! ;) > > Just use the latest UEFI firmware in ACPI mode to boot generic FreeBSD. > > Looking at their ACPI tables, they do finally have PCIe and USB3 as generic devices, though oddly not SATA: https://github.com/SolidRun/edk2-platforms/tree/master-lx2160a/Silicon/NXP/LX2160A/AcpiTables/Dsdt If this is the case, then the generic aarch64 images should boot on it... Not sure what will happen w/ the SATA though... -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not." From owner-freebsd-arm@freebsd.org Sat May 16 19:05:27 2020 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 455332FAA3A for ; Sat, 16 May 2020 19:05:27 +0000 (UTC) (envelope-from rodrigo@osorio.me) Received: from smtp.osorio.me (smtp.osorio.me [5.196.94.126]) by mx1.freebsd.org (Postfix) with ESMTP id 49PZVF71Glz3Pjv for ; Sat, 16 May 2020 19:05:25 +0000 (UTC) (envelope-from rodrigo@osorio.me) Received: from [192.168.1.184] (unknown [78.194.61.125]) (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) (No client certificate requested) by smtp.osorio.me (Postfix) with ESMTPSA id 3FFB5E2DD6 for ; Sat, 16 May 2020 19:05:19 +0000 (UTC) To: freebsd-arm@freebsd.org From: Rodrigo Osorio Subject: Issues with the pine A64+ board (no ethernet, hdmi stops, etc) Message-ID: <1869c25d-aa2f-bcbc-d255-1bbca4721328@osorio.me> Date: Sat, 16 May 2020 21:05:18 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:68.0) Gecko/20100101 Thunderbird/68.7.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US X-Rspamd-Queue-Id: 49PZVF71Glz3Pjv X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of rodrigo@osorio.me designates 5.196.94.126 as permitted sender) smtp.mailfrom=rodrigo@osorio.me X-Spamd-Result: default: False [-3.10 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; RECEIVED_SPAMHAUS_PBL(0.00)[125.61.194.78.khpj7ygk5idzvmvt5x4ziurxhy.zen.dq.spamhaus.net : 127.0.0.11]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+mx]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-arm@freebsd.org]; TO_DN_NONE(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; DMARC_NA(0.00)[osorio.me]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; IP_SCORE(-0.90)[ip: (-7.95), ipnet: 5.196.0.0/16(1.48), asn: 16276(1.98), country: FR(-0.00)]; RCVD_NO_TLS_LAST(0.10)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:16276, ipnet:5.196.0.0/16, country:FR]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 16 May 2020 19:05:27 -0000 Hi, Today I try to run pine64 images in my pine A64+ board[1] and found some blocking issues: - No ethernet device not found - No sound device - Only one USB connector seems to work - HDMI only work during the first part of the boot sequence (tested with the 12.1 only) - pciconf -lv result is empty I try the 12.0-RELEASE , 12.1-RELEASE and 13.0-CURRENT (20200514) 12.0: Serial output: http://files.osorio.me/pine64-logs/pine64-12.0.boot.txt 12.1: Serial output: http://files.osorio.me/pine64-logs/pine64-12.1.boot.txt Errors: Module simplebus/awg failed to register: 17         Module awg/miibus failed to register: 17 13.0: Serial output: http://files.osorio.me/pine64-logs/pine64-13-20200514.boot.txt I also did the test with the 12.1-RELEASE LTS, but u-boot fails with the following message: U-Boot SPL 2019.07 (Nov 01 2019 - 01:52:40 +0000) DRAM: 0 MiB ### ERROR ### Please RESET the board ### Hope this helps, All the best, -- rodrigo [1] https://www.pine64.org/devices/single-board-computers/pine-a64/ From owner-freebsd-arm@freebsd.org Sat May 16 22:13:50 2020 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id B86BD2FF441 for ; Sat, 16 May 2020 22:13:50 +0000 (UTC) (envelope-from jmg@gold.funkthat.com) Received: from gold.funkthat.com (gold.funkthat.com [IPv6:2001:470:800b::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "gate2.funkthat.com", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 49Pfgd2cjHz45wR for ; Sat, 16 May 2020 22:13:46 +0000 (UTC) (envelope-from jmg@gold.funkthat.com) Received: from gold.funkthat.com (localhost [127.0.0.1]) by gold.funkthat.com (8.15.2/8.15.2) with ESMTPS id 04GMDi3j008094 (version=TLSv1.2 cipher=DHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for ; Sat, 16 May 2020 15:13:44 -0700 (PDT) (envelope-from jmg@gold.funkthat.com) Received: (from jmg@localhost) by gold.funkthat.com (8.15.2/8.15.2/Submit) id 04GMDiN1008092 for freebsd-arm@FreeBSD.org; Sat, 16 May 2020 15:13:44 -0700 (PDT) (envelope-from jmg) Date: Sat, 16 May 2020 15:13:44 -0700 From: John-Mark Gurney To: freebsd-arm@FreeBSD.org Subject: need help w/ Cora-Z7, XC7Z007S Zynq board Message-ID: <20200516221344.GH4213@funkthat.com> Mail-Followup-To: freebsd-arm@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Operating-System: FreeBSD 11.3-STABLE amd64 X-PGP-Fingerprint: D87A 235F FB71 1F3F 55B7 ED9B D5FF 5A51 C0AC 3D65 X-Files: The truth is out there X-URL: https://www.funkthat.com/ X-Resume: https://www.funkthat.com/~jmg/resume.html X-TipJar: bitcoin:13Qmb6AeTgQecazTWph4XasEsP7nGRbAPE X-to-the-FBI-CIA-and-NSA: HI! HOW YA DOIN? can i haz chizburger? User-Agent: Mutt/1.6.1 (2016-04-27) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (gold.funkthat.com [127.0.0.1]); Sat, 16 May 2020 15:13:44 -0700 (PDT) X-Rspamd-Queue-Id: 49Pfgd2cjHz45wR X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of jmg@gold.funkthat.com has no SPF policy when checking 2001:470:800b::2) smtp.mailfrom=jmg@gold.funkthat.com X-Spamd-Result: default: False [-2.25 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-0.997,0]; RCVD_TLS_ALL(0.00)[]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; IP_SCORE(-1.46)[ipnet: 2001:470::/32(-4.11), asn: 6939(-3.16), country: US(-0.05)]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-arm@freebsd.org]; TO_DN_NONE(0.00)[]; AUTH_NA(1.00)[]; RCPT_COUNT_ONE(0.00)[1]; NEURAL_HAM_LONG(-1.00)[-0.995,0]; DMARC_NA(0.00)[funkthat.com]; R_SPF_NA(0.00)[]; FORGED_SENDER(0.30)[jmg@funkthat.com,jmg@gold.funkthat.com]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:6939, ipnet:2001:470::/32, country:US]; FROM_NEQ_ENVFROM(0.00)[jmg@funkthat.com,jmg@gold.funkthat.com]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 16 May 2020 22:13:50 -0000 Hello, Recently got the Cora-Z7 board, and want to get FreeBSD working on it. With a bit of help from manu, I managed to get FreeBSD booting on it, but running into issues w/ the clocks. The issue is that I need to set the clock-frequency for the global-clock, otherwise I don't have an event timer and the kernel panics. I configured it in the dts: https://www.funkthat.com/~jmg/FreeBSD/cora-z7/zynq-coraz7.dts But the issue is that time passes approximately 6.25x faster than it should. This was measured via pinging a remote host on the board, and via another machine, observing that it was about 6.23x difference, and noticing that 50MHz/8MHz is 6.25x. The 50 MHz speed was selected because the Cora-Z7 user guide says that the PS_CLK block is provided a 50 MHz clock, and the dts provided by Digilent uses 50 MHz as well: https://github.com/Digilent/u-boot-digilent/blob/master/arch/arm/dts/zynq-coraz7.dts#L41 If I change the clock to 8MHz, it hangs at: mmcsd0: 16GB at mmc0 50.0MHz/4bit/65535-block WARNING: WITNESS option enabled, expect reduced performance. Root mount waiting for: CAM Anyone have any suggestions on how to proceed? This is using the latest 13.0-CURRENT GENERICSD snapshot image. To boot, I did have to use the vendor supplied u-boot, as getting digilent's u-boot to compile wasn't easy as they haven't updated to the current version of OpenSSL, and porting their changes over mainline u-boot was going to be a bit of work. I was able to extract the boot.bin from their BSP package, and put that on the FAT file system (I did end up reformatting the FAT to FAT32, but not sure if this was needed or not), along w/ the above mentioned dts compiled to dtb. U-boot commands: fatload mmc 0 $netstart EFI/BOOT/bootarm.efi bootefi $netstart and then loader fails to properly get the boot device set: Command line arguments: l Image base: 0x10000000 EFI version: 2.05 EFI Firmware: Das U-boot (rev 0.00) Console: comconsole (0) Load Path: /uEnv.txt Load Device: sdhci@e0100000.blk Startup error in /boot/lua/loader.lua: LUA ERROR: cannot open /boot/lua/loader.lua: no such file or directory. so, I have to manually load the kernel and dtb with the following commands: set currdev=disk0s2a load /boot/kernel/kernel set currdev=disk0s1 set hw.ncpu=1 load -t dtb dtb/zynq-coraz7.dtb set currdev=disk0s2a boot The hw.ncpu=1 is necessary as we haven't committed the review that detects number of cpus by the registers: https://reviews.freebsd.org/D14429 dmesg: https://www.funkthat.com/~jmg/FreeBSD/cora-z7/dmesg.cora.z7.txt -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not."