Date: Tue, 6 Mar 2018 13:27:10 -0500 From: Mike <the.lists@mgm51.com> Cc: freebsd-arm@freebsd.org Subject: Re: Is maximum swap usage tunable? Message-ID: <1dabd314-28da-d8d6-b0f8-7269840eabb0@mgm51.com> In-Reply-To: <20180305183331.GB47820@www.zefox.net> References: <20180228214301.GA29481@www.zefox.net> <b82801b8-bc29-414c-1170-621bb4a5d937@mgm51.com> <CANCZdfq_MpxjUyVd-=%2BMiAQAER4TeDh9irhx_evdXwa3yt3h0g@mail.gmail.com> <20180303162605.GA41874@www.zefox.net> <20180304182831.GA44154@www.zefox.net> <CANCZdfpcccDuhJh4EF0C4KFz=dcN5mWvQ9aMiyF53kD=hMzy3Q@mail.gmail.com> <1520189171.38056.2.camel@freebsd.org> <20180304214003.GB44154@www.zefox.net> <20180305045723.GA47820@www.zefox.net> <637a406a-feba-23dc-be3c-d71d839503f7@mgm51.com> <20180305183331.GB47820@www.zefox.net>
index | next in thread | previous in thread | raw e-mail
On 3/5/2018 1:33 PM, bob prohaska wrote: > On Mon, Mar 05, 2018 at 09:59:15AM -0500, Mike wrote: >[snip] >> I plan to try again, same hardware but with 2GB swap space. >> > Please post what you learn... The compile stopped in the middle of build-worls. Here are the last things in the build log: === --- CodeGen/CGDebugInfo.o --- c++ -O2 -pipe -I/usr/obj/usr/src/arm64.aarch64/tmp/obj-tools/lib/clang/libclang -I/usr/obj/usr/src/arm64.aarch64/tmp/obj-tools/lib/clang/libllvm -I/usr/src/contrib/llvm/tools/clang/lib/Basic -I/usr/src/contrib/llvm/tools/clang/lib/Driver -I/usr/src/contrib/llvm/tools/clang/include -I/usr/src/lib/clang/include -I/usr/src/contrib/llvm/include -DLLVM_BUILD_GLOBAL_ISEL -D__STDC_LIMIT_MACROS -D__STDC_CONSTANT_MACROS -DLLVM_DEFAULT_TARGET_TRIPLE=\"aarch64-unknown-freebsd12.0\" -DLLVM_HOST_TRIPLE=\"aarch64-unknown-freebsd12.0\" -DDEFAULT_SYSROOT=\"/usr/obj/usr/src/arm64.aarch64/tmp\" -ffunction-sections -fdata-sections -gline-tables-only -MD -MF.depend.CodeGen_CGDebugInfo.o -MTCodeGen/CGDebugInfo.o -Qunused-arguments -I/usr/obj/usr/src/arm64.aarch64/tmp/legacy/usr/include -std=c++11 -fno-exceptions -fno-rtti -gline-tables-only -stdlib=libc++ -Wno-c++11-extensions -c /usr/src/contrib/llvm/tools/clang/lib/CodeGen/CGDebugInfo.cpp -o CodeGen/CGDebugInfo.o --- CodeGen/CGDecl.o --- c++ -O2 -pipe -I/usr/obj/usr/src/arm64.aarch64/tmp/obj-tools/lib/clang/libclang -I/usr/obj/usr/src/arm64.aarch64/tmp/obj-tools/lib/clang/libllvm -I/usr/src/contrib/llvm/tools/clang/lib/Basic -I/usr/src/contrib/llvm/tools/clang/lib/Driver -I/usr/src/contrib/llvm/tools/clang/include -I/usr/src/lib/clang/include -I/usr/src/contrib/llvm/include -DLLVM_BUILD_GLOBAL_ISEL -D__STDC_LIMIT_MACROS -D__STDC_CONSTANT_MACROS -DLLVM_DEFAULT_TARGET_TRIPLE=\"aarch64-unknown-freebsd12.0\" -DLLVM_HOST_TRIPLE=\"aarch64-unknown-freebsd12.0\" -DDEFAULT_SYSROOT=\"/usr/obj/usr/src/arm64.aarch64/tmp\" -ffunction-sections -fdata-sections -gline-tables-only -MD -MF.depend.CodeGen_CGDecl.o -MTCodeGen/CGDecl.o -Qunused-arguments -I/usr/obj/usr/src/arm64.aarch64/tmp/legacy/usr/include -std=c++11 -fno-exceptions -fno-rtti -gline-tables-only -stdlib=libc++ -Wno-c++11-extensions -c /usr/src/contrib/llvm/tools/clang/lib/CodeGen/CGDecl.cpp -o CodeGen/CGDecl.o === The Pi3 was hung. No response to keyboard or ssh. There were some messages in what appeared to be a looping scroll on the console. I was able to get a fuzzy pic, here: https://archive.mgm51.com/fbsd-build.jpg /var/log/messages had nothing odd except for: ===== Mar 5 11:18:16 rpi3 login: ROOT LOGIN (root) ON ttyv0 Mar 5 11:19:03 rpi3 kernel: lock order reversal: Mar 5 11:19:03 rpi3 kernel: 1st 0xffff000040937360 bufwait (bufwait) @ /usr/src/sys/kern/vfs_bio.c:3735 Mar 5 11:19:03 rpi3 kernel: 2nd 0xfffffd00018f0000 dirhash (dirhash) @ /usr/src/sys/ufs/ufs/ufs_dirhash.c:289 Mar 5 11:19:03 rpi3 kernel: stack backtrace: Mar 5 11:19:03 rpi3 kernel: #0 0xffff0000003b59d8 at witness_debugger+0x64 Mar 5 11:19:03 rpi3 kernel: #1 0xffff00000035cc30 at _sx_xlock+0x7c Mar 5 11:19:03 rpi3 kernel: #2 0xffff0000005cd5e0 at ufsdirhash_remove+0x38 Mar 5 11:19:03 rpi3 kernel: #3 0xffff0000005d03ec at ufs_dirremove+0x124 Mar 5 11:19:03 rpi3 kernel: #4 0xffff0000005d7700 at ufs_rmdir+0x114 Mar 5 11:19:03 rpi3 kernel: #5 0xffff00000067b528 at VOP_RMDIR_APV+0xac Mar 5 11:19:03 rpi3 kernel: #6 0xffff0000004210b0 at kern_rmdirat+0x16c Mar 5 11:19:03 rpi3 kernel: #7 0xffff00000064d59c at do_el0_sync+0x8bc Mar 5 11:19:03 rpi3 kernel: #8 0xffff0000006349f4 at handle_el0_sync+0x74 Mar 5 11:37:36 rpi3 kernel: lock order reversal: Mar 5 11:37:36 rpi3 kernel: 1st 0xffff0000408228f8 bufwait (bufwait) @ /usr/src/sys/vm/vm_pager.c:374 Mar 5 11:37:36 rpi3 kernel: 2nd 0xfffffd0001c119c8 ufs (ufs) @ /usr/src/sys/dev/md/md.c:952 Mar 5 11:37:36 rpi3 kernel: stack backtrace: Mar 5 11:37:36 rpi3 kernel: #0 0xffff0000003b59d8 at witness_debugger+0x64 Mar 5 11:37:36 rpi3 kernel: #1 0xffff00000032bcbc at __lockmgr_args+0x6ac Mar 5 11:37:36 rpi3 kernel: #2 0xffff0000005c8864 at ffs_lock+0x88 Mar 5 11:37:36 rpi3 kernel: #3 0xffff00000067bf18 at VOP_LOCK1_APV+0xac Mar 5 11:37:36 rpi3 kernel: #4 0xffff000000426fac at _vn_lock+0x64 Mar 5 11:37:36 rpi3 kernel: #5 0xffff000000173fd0 at mdstart_vnode+0x398 Mar 5 11:37:36 rpi3 kernel: #6 0xffff0000001729d4 at md_kthread+0x1bc Mar 5 11:37:36 rpi3 kernel: #7 0xffff00000031807c at fork_exit+0x7c ====== The entries before 11:37 were during boot-up. The 11:37 entries were around the time the RPi3 hung. Oh yeah... # uname -a FreeBSD rpi3 12.0-CURRENT FreeBSD 12.0-CURRENT #0 r330034: Mon Feb 26 22:51:01 UTC 2018 root@releng3.nyi.freebsd.org:/usr/obj/usr/src/arm64.aarch64/sys/GENERIC arm64 Note sure how to show the version of source it was building, suggestions? fwiw, and YMMV. Hope this helps.help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1dabd314-28da-d8d6-b0f8-7269840eabb0>