From nobody Tue Jan 25 18:08:23 2022 X-Original-To: freebsd-arm@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 723AE1976BD2 for ; Tue, 25 Jan 2022 18:08:24 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [50.1.20.27]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "www.zefox.com", Issuer "www.zefox.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Jjvwl4sQdz3h1H for ; Tue, 25 Jan 2022 18:08:23 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (localhost [127.0.0.1]) by www.zefox.net (8.16.1/8.15.2) with ESMTPS id 20PI8NwB043953 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Tue, 25 Jan 2022 10:08:24 -0800 (PST) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.16.1/8.15.2/Submit) id 20PI8NxN043952; Tue, 25 Jan 2022 10:08:23 -0800 (PST) (envelope-from fbsd) Date: Tue, 25 Jan 2022 10:08:23 -0800 From: bob prohaska To: Mark Millard Cc: Free BSD , bob prohaska Subject: Re: Troubles building world on stable/13 Message-ID: <20220125180823.GB43635@www.zefox.net> References: <20220121031601.GA26308@www.zefox.net> <8595CFBD-DC65-4472-A0A1-8A7BE1C031D6@yahoo.com> <20220124165449.GA39982@www.zefox.net> <5FAC2B2C-7740-435E-A183-FB3EF1FCE7F9@yahoo.com> <1CB4EDCD-0998-4363-8CEA-14854EB76FA3@yahoo.com> <20220125162245.GA43635@www.zefox.net> <61A3CF79-552C-4884-A8EA-85003B249856@yahoo.com> List-Id: Porting FreeBSD to ARM processors List-Archive: https://lists.freebsd.org/archives/freebsd-arm List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arm@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <61A3CF79-552C-4884-A8EA-85003B249856@yahoo.com> X-Rspamd-Queue-Id: 4Jjvwl4sQdz3h1H X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of fbsd@www.zefox.net has no SPF policy when checking 50.1.20.27) smtp.mailfrom=fbsd@www.zefox.net X-Spamd-Result: default: False [0.90 / 15.00]; RCVD_TLS_ALL(0.00)[]; ARC_NA(0.00)[]; WWW_DOT_DOMAIN(0.50)[]; MID_RHS_MATCH_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; NEURAL_HAM_MEDIUM(-1.00)[-0.996]; NEURAL_HAM_LONG(-0.99)[-0.994]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[zefox.net]; AUTH_NA(1.00)[]; R_SPF_NA(0.00)[no SPF record]; NEURAL_SPAM_SHORT(0.99)[0.991]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; MLMMJ_DEST(0.00)[freebsd-arm]; FREEMAIL_TO(0.00)[yahoo.com]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:7065, ipnet:50.1.16.0/20, country:US]; RCVD_COUNT_TWO(0.00)[2]; MID_RHS_WWW(0.50)[] X-ThisMailContainsUnwantedMimeParts: N On Tue, Jan 25, 2022 at 09:13:08AM -0800, Mark Millard wrote: > > -DBATCH ? I'm not aware of there being any use of that symbol. > Do you have a documentation reference for it so that I could > read about it? > It's a switch to turn off dialog4ports. I can't find the reference now. Perhaps it's been deprecated? A name like -DUSE_DEFAULTS would be easier to understand anyway. On a whim, I tried building devel/llvm13 on a Pi4 running -current with 8 GB of RAM and 8 GB of swap. To my surprise, that stopped with: nemesis.zefox.com kernel log messages: +FreeBSD 14.0-CURRENT #26 main-5025e85013: Sun Jan 23 17:25:31 PST 2022 +swap_pager: indefinite wait buffer: bufobj: 0, blkno: 1873450, size: 4096 +swap_pager: indefinite wait buffer: bufobj: 0, blkno: 521393, size: 4096 +swap_pager: indefinite wait buffer: bufobj: 0, blkno: 209826, size: 12288 +swap_pager: indefinite wait buffer: bufobj: 0, blkno: 1717218, size: 24576 +pid 56508 (c++), jid 0, uid 0, was killed: failed to reclaim memory On an 8GB machine, that seems strange. Per the failure message I restarted the build of devel/llvm13 with make -DBATCH MAKE_JOBS_UNSAFE=YES > make.log & It seems to be running with only one thread so far, not sure if that's by design or happenstance. > > However, restarting buildworld using -j1 appears to have worked past > > the former point of failure. > > Hmm. That usually means one (or both) of two things was involved > in the failure: > > A) a build race where something is not (fully) ready when > it is used > > B) running out of resources, such as RAM+SWAP > The stable/13 machine is short of swap; it has only 2 GB, which used to be enough. Maybe that's the problem, but having an error report that says it's a segfault is a confusing diagnostic. > But, as I understand, you were able to use a .cpp and > .sh file pair that had been produced to repeat the > problem on the RPi3B --and that would not have been a > parallel-activity context. > To be clear, the reproduction was on the same stable/13 that reported the original failure. An attempt at reproduction on a different Pi3 running -current ran without any errors. Come to think of it, that machine had more swap, too. > > It's in the building libraries phase now. > > Based on log size I'd guess it's about halfway through buildworld. > > > > Well, hopefully you will not be stuck with -j1 builds in > the future as well. > Indeed! bob prohaska