Date: Mon, 30 Jul 2018 22:47:12 -0700 From: bob prohaska <fbsd@www.zefox.net> To: freebsd-arm@freebsd.org Subject: Re: RPI3 swap experiments Message-ID: <20180731054712.GA92917@www.zefox.net> In-Reply-To: <20180725232453.GA57716@www.zefox.net> References: <ba33d8a7-a849-3893-8016-0765ebe1c51f@sentry.org> <2deaaec3-f78f-0b09-5ca7-27e14c6979f9@sentry.org> <bc8da02c-4465-9634-6fd0-0af4c63aa49d@sentry.org> <20180723063526.GA45726@www.zefox.net> <AB5EE2E4-B2FD-4CA9-A993-04C2A4BE10AE@yahoo.com> <20180723155311.GB45726@www.zefox.net> <4ED9B658-A5A8-4BA6-9412-EBB7150B4B66@yahoo.com> <20180723190257.GA47869@www.zefox.net> <76BCFCB9-1071-4557-9FDE-017444ADBF42@yahoo.com> <20180725232453.GA57716@www.zefox.net>
next in thread | previous in thread | raw e-mail | index | archive | help
OOMA is still killing processes in -j4 buildworld sessions for no obvious reason when using mixed USB/microSD swap. The most recent experiment is with r336877 rebuilding itself from a clean start. The various log files are at http://www.zefox.net/~fbsd/rpi3/swaptests/r336877/ The OOMA kills occur around two hours after the worst read/write delays, which are in the low tens of seconds. Perhaps most curiously, the long delays don't appear to involve swap partitions. Similar problems now seem present with the RPI2 on 11-stable. The first failure was with r335398 trying to compile 336871. Buildworld has been backed down to -j2 and restarted in the hope it'll eventually succeed. In this particular case all swap is on USB, in a single 2 GB partition. It would be most interesting to see what happens if OOMA could be turned off. Is that possible? Thanks for reading, bob prohaska
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20180731054712.GA92917>