From owner-freebsd-arm@freebsd.org Fri Mar 30 23:50:42 2018 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9C27BF7478F for ; Fri, 30 Mar 2018 23:50:42 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [50.1.20.27]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "www.zefox.org", Issuer "www.zefox.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 18E1186407 for ; Fri, 30 Mar 2018 23:50:41 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (localhost [127.0.0.1]) by www.zefox.net (8.15.2/8.15.2) with ESMTPS id w2UNodYD053852 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 30 Mar 2018 16:50:40 -0700 (PDT) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.15.2/8.15.2/Submit) id w2UNodU2053851; Fri, 30 Mar 2018 16:50:39 -0700 (PDT) (envelope-from fbsd) Date: Fri, 30 Mar 2018 16:50:39 -0700 From: bob prohaska To: freebsd-arm@freebsd.org Subject: More problems self-hosting -current on RPi3 Message-ID: <20180330235039.GA53786@www.zefox.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.24 (2015-08-30) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Mar 2018 23:50:42 -0000 Here's a strange buildworld failure with -current on an RPI3. To set the stage, a make -j2 buildworld/buildkernel was run from a clean (run make cleandir twice, rm -rf /usr/obj/usr/src) start. Kernel and sources were at, or close to, r331146. Buildworld finished, but the kernel build failed on an error of long standing, something about mismatches between various versions of stdint.h in the file system. Svnlite update reported quite a bit of activity, so the world/kernel build was restarted with -j2 and -DNO_CLEAN. Some hours later, the system was found with all ssh sessions terminated and the top output recorded in the link below. It looks as if the system decided it was out of swap, and then went on a killing spree when lld.ld didn't go away. Disregarding the stated swap usage, ld.lld was less than 1.4 GB in size with 3 GB of swap. Details are at http://www.zefox.net/~fbsd/rpi3/crashes/20180330/ It's worth noting that gstat reports write speeds of 2-3 MB/sec to the microSD card and USB flash, which does not seem much worse than mechanical hard disks. The system _does_ seem prone to a sort of "swap frenzy" when swap usage goes much over 10%, recovering at intervals when all the cores are busy. Some months ago it was at least occasionally possible to finish a -j4 buildworld, now even -j2 buildworld is extremely uncertain. Is anybody able to self host -current in the last few weeks on an RPI3? Thanks for reading, bob prohaska