Date: Thu, 2 Apr 2020 16:33:59 -0700 From: bob prohaska <fbsd@www.zefox.net> To: freebsd-arm@freebsd.org Subject: Unexpected OOM kill on rpi2 while building world Message-ID: <20200402233359.GA31562@www.zefox.net>
next in thread | raw e-mail | index | archive | help
Two installations of the FreeBSD-12.1-STABLE-arm-armv7-RPI2-20200305-r358659.img image have set up and built -j4 world using a single 64GB Samsung Evo Plus microSD card with a 2.6 GB swap partition. No changes to /boot/loader.conf required. On the third installation, the machine stopped with pid 68521 (c++), jid 0, uid 0, was killed: out of swap space so I set vm.pfault_oom_attempts="-1" and restarted buildworld with -DNO_CLEAN The machine promptly reported pid 93318 (c++), jid 0, uid 0, was killed: out of swap space In neither case were there any "indefinite wait...." or any other warning messages. At that point I set vm.pageout_oom_seq="4096" and restarted buildworld, again with -DNO_CLEAN. Buildworld seems to have gotten past the bottleneck and looks like it will complete, but I'm puzzled, both at the appearance of the trouble, not formerly seen on the Pi2, and on the failure of vm.pfault_oom_attempts="-1" by itself to disable OOMA. Casual observation suggests swap use peaks at a few hundred MB under 12.1 on the Pi2. All three installations were run on the same physical Pi, though of course the microSD cards were distinct. Even so, all three cards are nominally identical and likely from the same batch. The one tangible difference is that the Pi2 is now on a private network, the two earlier buildworlds were on a public network. Can't see how that would matter, however. Thanks for reading, and any insights. bob prohaska
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20200402233359.GA31562>