From nobody Sat Jun 17 23:28:00 2023 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 4QkByr1tdwz4ffxG for ; Sat, 17 Jun 2023 23:27:48 +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 4QkByq5qxTz4VYF for ; Sat, 17 Jun 2023 23:27:47 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Authentication-Results: mx1.freebsd.org; none Received: from www.zefox.net (localhost [127.0.0.1]) by www.zefox.net (8.17.1/8.15.2) with ESMTPS id 35HNS0al037568 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Sat, 17 Jun 2023 16:28:00 -0700 (PDT) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.17.1/8.15.2/Submit) id 35HNS0QA037567; Sat, 17 Jun 2023 16:28:00 -0700 (PDT) (envelope-from fbsd) Date: Sat, 17 Jun 2023 16:28:00 -0700 From: bob prohaska To: Mark Millard Cc: freebsd-arm@freebsd.org Subject: Re: Armv7 linker failure on -current Message-ID: References: <8B771495-1C68-4A23-8658-02A8AD28088B@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: X-Rspamd-Queue-Id: 4QkByq5qxTz4VYF X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:7065, ipnet:50.1.16.0/20, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N On Sat, Jun 17, 2023 at 04:05:12PM -0700, Mark Millard wrote: > On Jun 17, 2023, at 11:42, bob prohaska wrote: > > > On Sat, Jun 17, 2023 at 08:34:16AM -0700, Mark Millard wrote: > >> On Jun 17, 2023, at 07:34, bob prohaska wrote: > >> > >>> A Pi2 running -current stops in buildworld with > >> > >> I assume self building an update to main [so: 14]. > >> > > > > Correct. > > > >> What commit last built successfully? (This bounds what would be different > >> in official materials.) > >> > > > > I haven't kept any manual records, but uname -a reports > > FreeBSD www.zefox.com 14.0-CURRENT FreeBSD 14.0-CURRENT #39 main-9f135336f5: Fri Jun 16 02:18:02 PDT 2023 bob@www.zefox.com:/usr/obj/usr/src/arm.armv7/sys/GENERIC arm > > > > Since my original post git pull found a few updates and I restarted buildworld > > I expect that this means there is no evidence left to look at > what was originally reported. I still have the buildworld output from the failure, but given what went before I'm not at all confident it represents anything to do with FreeBSD. > > > It has failed also, but with what looks like an unrelated error. These problems > > emerged after a silent hang using -j3, followed by power-cycling and reboot. -j3 > > was backed down to -j2 and buildworld restarted, with the mischief reported here > > ensuing. > > I see. Messy. > > > I'm starting to wonder if there's some undetected corruption in either /usr/src > > or /usr/obj. Perhaps I'd best run make cleandir twice and start over. That will > > likely take at least few days. This is a mechanical hard disk setup, with 1 GB > > swap. Boot is via microSD using only bootcode.bin, with the usual msdos partition > > on the hard disk. > > > > Is there a more expedient approach under the circumstances? > > If I understand right, there is no evidence to examine from > the original report's context to guide any investigation. It Apart from the buildworld log, no. I was quite surprised at the lockup, -j3 and a gig of swap had been working fine for several build/install cycles. It was especially surprising when nothing turned up on the console. > seems you need to establish a known context (broken or > working) to possibly investigate. > Make cleandir was run twice and -j2 meta-mode buildworld restarted. I'll be more careful with the wreckage next time. Thanks for writing! bob prohaska