Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 20 Mar 2021 12:27:48 -0700
From:      Mark Millard <marklmi@yahoo.com>
To:        bob prohaska <fbsd@www.zefox.net>
Cc:        freebsd-arm <freebsd-arm@freebsd.org>
Subject:   Re: RPI4 clock speeds and serial port ( temperatures idle and -j4 buildworld buildkernel )
Message-ID:  <AD8A445A-DF90-4525-8042-EA2A667558FE@yahoo.com>
In-Reply-To: <20210320182821.GA49050@www.zefox.net>
References:  <EA6BE351-98F5-4446-BA4D-948F04EDFD3B@yahoo.com> <81AC0353-258C-41C3-86B1-C133E33D97E3@yahoo.com> <20210319174359.GA38899@www.zefox.net> <FA5A110A-4E7A-4381-BBE5-9B3022CA9008@googlemail.com> <20210319195019.GA39087@www.zefox.net> <FDBC2E89-8473-4C3A-B12E-78821949FDDB@yahoo.com> <20210320005302.GA40542@www.zefox.net> <81CB0CCA-59AC-49A2-9372-4E2C22E3214D@googlemail.com> <20210320155638.GA41617@www.zefox.net> <63E61033-667C-4A08-9012-7D987B652176@yahoo.com> <20210320182821.GA49050@www.zefox.net>

next in thread | previous in thread | raw e-mail | index | archive | help
On 2021-Mar-20, at 11:28, bob prohaska <fbsd at www.zefox.net> wrote:

> On Sat, Mar 20, 2021 at 10:41:48AM -0700, Mark Millard wrote:
>> On 2021-Mar-20, at 08:56, bob prohaska <fbsd atwww.zefox.net> wrote:
>>=20
>>> The most recent test on the 8GB Pi4 finished in 9 hours. That was =
after
>>> running make cleandir twice, but having the installed system and the
>>> sources relatively close (days) in age, on -current.
>>=20
>> So a debug kernel was running? (Non-debug running for my builds.)
>=20
> Yes.
>=20
>>=20
>> Did it include a buildkernel? Or just a buildworld?
>>=20
>=20
> Just buildworld in 9 hours.=20
>=20
>> At around 9 hours, it would take standardizing on a (equivalent
>> of) src.conf too be able to well compare your context vs. mine
>> now, if we ever want to do so. I'll list my file later below
>> for reference, although I'm probably more likely to try your
>> src.conf content in my overclocked context than you are
>> likely to try building via my src.conf like content in your
>> powerd context.
>>=20
>=20
> No /etc/src.conf for this test, nor /etc/make.conf.=20

I have a -j4 buildworld build kernel going on the
FreeBSD RPi4B 8GiByte, based on using a prefix of:

env __MAKE_CONF=3D"/dev/null" \
SRCCONF=3D"/dev/null" SRC_ENV_CONF=3D"/dev/null"

I'll report the buildworld and buildkernel times
once it is done.

The RPi4 support for powerd (cpufreq) was added
on 2020-Jun-20 but my RPi4B activity started
well before then. That is why I did not go down
the powerd path in how I configured things. It
will be interesting to compare to your time.

>> Welcome to the world of overnight (sleep-time) buildworld on a
>> small board computer.
>>=20
>=20
> It's a most welcome change!

You can now also buildworld and buildkernel targeting
armv7 in the overnight time frame via either:

A) a form of cross build (using src.conf like file(s))
or:
B) running an armv7 world in a chroot and doing a
   "native" style build in the chroot.

You can also set up poudriere (or just a chroot area
that you chroot to) in order to build armv7 ports in.

This also has less of a memory limitation in that
multiple full-sized armv7 build processes can be
in RAM at once without swapping/paging: more total
RAM in use than an armv7 would allow, though no
individual process gets more than an armv7 could
potentially allow.

You could build for the RPi3(s) or other aarch64
machines on the RPi4(s) as well. So, likely your
arm build activity no longer has to take up nearly
as much time, especially the really long-wait
builds.

>>> That's with powerd
>>> enabled, but no other speedup tweaks. Temps were just under  60 C, =
with
>>> a fan in the case but no heatsinks on the ICs.=20
>>=20
>> Ambient temperature? (It is the difference that indicates how
>> well your cooling is working and it is the difference that
>> is more comparable across contexts. For example, my around
>> 15.5C ambient likely was likely around 10C lower than for
>> many reported figures.)
>>=20
>=20
> Ambient was around 15-17 C at the times of observation.=20
>=20
>>>> sysctl dev.cpu.0.freq will definitely show the current freq.
>>>=20
>>> On a Pi3 with GENERIC-MMCCAM kernel  (also running buildworld) it =
reports
>>> bob@www:/usr/freebsd-src % sysctl dev.cpu.0.freq
>>> dev.cpu.0.freq: 1200
>>> also with no other speedup efforts beyond powerd. That machine has =
heastinks
>>> on the ICs but only a fan blowing in through the openings in the =
plastic case.
>>> It's around 60C.=20
>>>=20
>>> So far the effects of powerd seems to be uniformly good, with=20
>>> no downsides. Next, to try a Pi2 v1.1 (armv7)
>>>=20
>=20
> The Pi2 V1.1 is now running buildworld with powerd enabled. Heatsinks
> on the ICs, but no fan at all, < 50 C (17C ambient) with 0% idle, 900=20=

> MHz, serial console seems to work fine.=20
>=20
>>=20
>> FYI (not that you are likely to build and run such:
>>=20
> [snipped for brevity]
>=20
> Alas, you are right. It's already difficult to keep the=20
> experiments straight in my head......too many variations.
>=20
> But, unless something most unexpected goes wrong, it seems
> that powerd is useful on the Pi series computers. =20
>=20

Yep.

=3D=3D=3D
Mark Millard
marklmi at yahoo.com
( dsl-only.net went
away in early 2018-Mar)




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AD8A445A-DF90-4525-8042-EA2A667558FE>