Date: Fri, 27 Mar 2020 19:25:45 -0700 From: Mark Millard <marklmi@yahoo.com> To: bob prohaska <fbsd@www.zefox.net> Cc: freebsd-arm@freebsd.org Subject: Re: Belated out of swap kill on rpi3 at r359216 Message-ID: <5549E63B-0784-4B58-AD36-2A2EDC518308@yahoo.com> In-Reply-To: <0A8CF8D1-8D0F-40E2-A10D-EB44BEEAB557@yahoo.com> References: <20200324155753.GA91922@www.zefox.net> <83E41A13-6C24-4B56-A837-779044038FBC@yahoo.com> <20200324185518.GA92311@www.zefox.net> <75CE3C07-8A0A-4D32-84C6-24BEA967447E@yahoo.com> <20200324224658.GA92726@www.zefox.net> <764D5A86-6A42-44E0-A706-F1C49BB198DA@yahoo.com> <20200325015633.GA93057@www.zefox.net> <0FF6BC4C-296F-49F3-8FB8-AA87A49349E2@yahoo.com> <20200326220649.GA99824@www.zefox.net> <0A8CF8D1-8D0F-40E2-A10D-EB44BEEAB557@yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2020-Mar-26, at 16:24, Mark Millard <marklmi at yahoo.com> wrote:
> On 2020-Mar-26, at 15:06, bob prohaska <fbsd at www.zefox.net> wrote:
>=20
>> . . .
>=20
> Anyway, I may, for a time, have one context that is
> more like yours than is normal for me. As stands, the
> RPi3 is doing a from-scratch buildworld buildkernel .
> (Reconstructing the head -r358966 that it is already
> running.) It is not splitting the I/O load but is
> using a USB SSD (via a powered hub), not the microsd
> card. No extra logging. vm.pfault_oom_attempts=3D-1
> and vm.pageout_oom_seq=3D120 for this attempt. 3072
> MiBytes of page/swap space. It is a -j4 build attempt.
>=20
("No extra logging" meant: beyond my normal typescript
recording of the build output. That file ended up at
7741518 Bytes for size.)
The build completed without any /var/log/message or
console output during the build. My modified version
of top reported (details copied from a ssh window) . . .
For Mem: 738512Ki MaxObsActive, 190608Ki MaxObsWired, 906372Ki =
MaxObs(Act+Wir)
For Swap: 1927Mi MaxObsUsed
(top was started before the build. "MaxObs" is short
for "Maximum Observed".)
The build took a few minutes under 31 hrs.
(Ending: 2010-03-27:18:54:03
Starting: 2020-03-26:12:02:47).
Because it was rebuilding -r358966 that it was already
running, no bootstrap compiler or linker was built,
despite it being a from-scratch build: The system
compiler and linker were sufficient.
For reference: the details of what was specified for
building (contributes to "how long it took"). . .
# more ~/src.configs/src.conf.cortexA53-clang-bootstrap.aarch64-host=20
TO_TYPE=3Daarch64
#
KERNCONF=3DGENERIC-NODBG
TARGET=3Darm64
.if ${.MAKE.LEVEL} =3D=3D 0
TARGET_ARCH=3D${TO_TYPE}
.export TARGET_ARCH
.endif
#
WITH_SYSTEM_COMPILER=3D
WITH_SYSTEM_LINKER=3D
#
WITH_LIBCPLUSPLUS=3D
WITHOUT_BINUTILS_BOOTSTRAP=3D
WITH_ELFTOOLCHAIN_BOOTSTRAP=3D
#Disables avoiding bootstrap: WITHOUT_LLVM_TARGET_ALL=3D
WITH_LLVM_TARGET_AARCH64=3D
WITH_LLVM_TARGET_ARM=3D
WITHOUT_LLVM_TARGET_MIPS=3D
WITHOUT_LLVM_TARGET_POWERPC=3D
WITHOUT_LLVM_TARGET_RISCV=3D
WITHOUT_LLVM_TARGET_X86=3D
WITH_CLANG=3D
WITH_CLANG_IS_CC=3D
WITH_CLANG_FULL=3D
WITH_CLANG_EXTRAS=3D
WITH_LLD=3D
WITH_LLD_IS_LD=3D
WITHOUT_BINUTILS=3D
WITH_LLDB=3D
#
WITH_BOOT=3D
WITHOUT_LIB32=3D
#
#
NO_WERROR=3D
#WERROR=3D
MALLOC_PRODUCTION=3D
#
# Avoid stripping but do not control host -g status as well:
DEBUG_FLAGS+=3D
#
WITH_DEBUG_FILES=3D
#
# Use of the .clang 's here avoids
# interfering with other C<?>FLAGS
# usage, such as ?=3D usage.
CFLAGS.clang+=3D -mcpu=3Dcortex-a53
CXXFLAGS.clang+=3D -mcpu=3Dcortex-a53
CPPFLAGS.clang+=3D -mcpu=3Dcortex-a53
ACFLAGS.arm64cpuid.S+=3D -mcpu=3Dcortex-a53+crypto
ACFLAGS.aesv8-armx.S+=3D -mcpu=3Dcortex-a53+crypto
ACFLAGS.ghashv8-armx.S+=3D -mcpu=3Dcortex-a53+crypto
# more /usr/src/sys/arm64/conf/GENERIC-NODBG=20
#
# GENERIC -- Custom configuration for the arm64/aarch64
#
include "GENERIC"
ident GENERIC-NODBG
makeoptions DEBUG=3D-g # Build kernel with gdb(1) =
debug symbols
options ALT_BREAK_TO_DEBUGGER
options KDB # Enable kernel debugger support
# For minimum debugger support (stable branch) use:
#options KDB_TRACE # Print a stack trace for a =
panic
options DDB # Enable the kernel debugger
# Extra stuff:
#options VERBOSE_SYSINIT=3D0 # Enable verbose sysinit =
messages
#options BOOTVERBOSE=3D1
#options BOOTHOWTO=3DRB_VERBOSE
#options KTR
#options KTR_MASK=3DKTR_TRAP
##options KTR_CPUMASK=3D0xF
#options KTR_VERBOSE
# Disable any extra checking for. . .
nooptions DEADLKRES # Enable the deadlock resolver
nooptions INVARIANTS # Enable calls of extra sanity =
checking
nooptions INVARIANT_SUPPORT # Extra sanity checks of =
internal structures, required by INVARIANTS
nooptions WITNESS # Enable checks to detect =
deadlocks and cycles
nooptions WITNESS_SKIPSPIN # Don't run witness on spinlocks =
for speed
nooptions DIAGNOSTIC
nooptions MALLOC_DEBUG_MAXZONES # Separate malloc(9) zones
nooptions BUF_TRACKING
nooptions FULL_BUF_TRACKING
=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?5549E63B-0784-4B58-AD36-2A2EDC518308>