Date: Thu, 18 Mar 2021 22:14:26 -0700 From: Mark Millard <marklmi@yahoo.com> To: bob prohaska <fbsd@www.zefox.net> Cc: freebsd-arm <freebsd-arm@freebsd.org>, tech-lists <tech-lists@zyxst.net> Subject: Re: RPI4 clock speeds and serial port ( temperatures idle and -j4 buildworld buildkernel ) Message-ID: <81AC0353-258C-41C3-86B1-C133E33D97E3@yahoo.com> In-Reply-To: <EA6BE351-98F5-4446-BA4D-948F04EDFD3B@yahoo.com> References: <20210318170053.GA26688@www.zefox.net> <9FFA0A51-C0B7-4121-95CA-B98669809007@yahoo.com> <E4CF6642-CB70-4495-A865-05469953561C@yahoo.com> <EA6BE351-98F5-4446-BA4D-948F04EDFD3B@yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2021-Mar-18, at 13:50, Mark Millard <marklmi at yahoo.com> wrote: > On 2021-Mar-18, at 13:01, Mark Millard <marklmi at yahoo.com> wrote: >=20 > On 2021-Mar-18, at 12:05, Mark Millard <marklmi@yahoo.com> wrote: >>=20 >>> . . . >>=20 >> I've not done temperate testing in a >> while. One quick report I can make >> is that for my "always cpu_freq 2000 >> always sdram_freq 3200" contexts >> with the RPI4B only doing whatever >> background tasks are involved in >> being basically idle but having >> the heatsinks and active cooling >> (fans): >>=20 >> # sysctl -a | grep temper >> hw.cpufreq.temperature: 35012 >> dev.cpu.0.temperature: 35.0C >>=20 >> in a currently 15.5C or so ambient >> context is rather typical. >>=20 >=20 > So I started up a from-scratch "rebuild self" > -j buildworld buildkernel via an ssh over > Ethernet session. (This may minimize > interrupt overhead vs. the output text > scrolling the serial console?) >=20 > 30+ minutes into the build: >=20 > I'm seeing figures like (the high so far): >=20 > hw.cpufreq.temperature: 49137 > dev.cpu.0.temperature: 49.1C >=20 > (Such pairs give some idea of the > fairly short term variability.) >=20 > I'm only bothering to look once > a minute or so: >=20 > # while (true); do sleep 60 ; sysctl hw.cpufreq.temperature = dev.cpu.0.temperature ; done >=20 > So far the widest fairly-short-term variation > was in: >=20 > hw.cpufreq.temperature: 45727 > dev.cpu.0.temperature: 45.6C >=20 >=20 > FYI: The build reported: >=20 > make[1]: "/usr/fbsd/mm-src/Makefile.inc1" line 339: SYSTEM_COMPILER: = Determined that CC=3Dcc matches the source tree. Not bootstrapping a = cross-compiler. > make[1]: "/usr/fbsd/mm-src/Makefile.inc1" line 344: SYSTEM_LINKER: = Determined that LD=3Dld matches the source tree. Not bootstrapping a = cross-linker. >=20 >=20 > Later I'll report the maximum(s) observed. But it will > be a few hours for the build to complete. >=20 Looking at the -j4 buildworld buildkernel output I see a few of examples of making it into the 50s. The highest being: hw.cpufreq.temperature: 52059 dev.cpu.0.temperature: 52.0C Ignoring the start-warmup/end-cooldown: a few under 46.0C So unlikely that there was any throttling. FYI: World build completed on Thu Mar 18 21:31:44 PDT 2021 World built in 29705 seconds, ncpu: 4, make -j4 . . . Kernel build for GENERIC-NODBG completed on Thu Mar 18 22:10:02 PDT 2021 Kernel(s) GENERIC-NODBG built in 2298 seconds, ncpu: 4, make -j4 So somewhat under 9 hours. Note: I've never checked how much of a difference using a microsd card instead of the USB3 SSD makes for such a temperature test. =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?81AC0353-258C-41C3-86B1-C133E33D97E3>