From nobody Thu Nov 06 14:04:52 2025 X-Original-To: freebsd-current@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 4d2P7P2yfMz6GCFP; Thu, 06 Nov 2025 14:04:01 +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 "pelorus.zefox.org", Issuer "pelorus.zefox.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4d2P7M6Znvz3xSn; Thu, 06 Nov 2025 14:03:59 +0000 (UTC) (envelope-from fbsd@www.zefox.net) 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 Received: from www.zefox.net (localhost [127.0.0.1]) by www.zefox.net (8.18.1/8.18.1) with ESMTPS id 5A6E4qsX001874 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Thu, 6 Nov 2025 06:04:52 -0800 (PST) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.18.1/8.18.1/Submit) id 5A6E4qQM001873; Thu, 6 Nov 2025 06:04:52 -0800 (PST) (envelope-from fbsd) Date: Thu, 6 Nov 2025 06:04:52 -0800 From: bob prohaska To: freebsd-arm@freebsd.org Cc: freebsd-current@freebsd.org Subject: Arm v7 RPi2 -current unresponsive to debugger escape during buildworld Message-ID: List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Spamd-Bar: / X-Spamd-Result: default: False [0.02 / 15.00]; AUTH_NA(1.00)[]; NEURAL_HAM_MEDIUM(-0.99)[-0.990]; NEURAL_HAM_LONG(-0.83)[-0.827]; WWW_DOT_DOMAIN(0.50)[]; MID_RHS_WWW(0.50)[]; MIME_GOOD(-0.10)[text/plain]; NEURAL_HAM_SHORT(-0.07)[-0.067]; RCVD_TLS_LAST(0.00)[]; ARC_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; RCPT_COUNT_TWO(0.00)[2]; MISSING_XM_UA(0.00)[]; ASN(0.00)[asn:7065, ipnet:50.1.16.0/20, country:US]; MID_RHS_MATCH_FROM(0.00)[]; MLMMJ_DEST(0.00)[freebsd-arm@freebsd.org,freebsd-current@freebsd.org]; DMARC_NA(0.00)[zefox.net]; FROM_EQ_ENVFROM(0.00)[]; FROM_HAS_DN(0.00)[]; R_DKIM_NA(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; TO_MATCH_ENVRCPT_ALL(0.00)[]; TO_DN_NONE(0.00)[]; R_SPF_NA(0.00)[no SPF record] X-Rspamd-Queue-Id: 4d2P7M6Znvz3xSn For roughly the past year I've been seeing buildworld become unresponsive compiling -current on a Pi2 (armv7). The stoppages seem random, sometimes with no visible memory pressure, other times while swapping. The machine uses a USB mechanican hard drive for root and swap. Numerous attemps to use enter-tilda-control-B to get into the debugger have failed, with absolutely no response. In the most recent case the disk activity light was flashing rapidly, a relatively uncommon event. The frozen top window showed ~312 MB swap in use, less than half of the maximum commonly seen for a -j3 buildworld. Looking at the log file after power-cycling it appeared to have last updated the previous evening, so it seems unlikely it got stuck on a core dump. Reboot was uneventful, with fsck completing successfully. Buildworld has been restarted, it'll pick up where it left off. The last entries in the buildworld log file were: Building /usr/obj/usr/src/arm.armv7/lib/clang/libclang/Sema/SemaTemplateInstantiateDecl.pico Building /usr/obj/usr/src/arm.armv7/lib/clang/libclang/Sema/SemaTemplateVariadic.pico Building /usr/obj/usr/src/arm.armv7/lib/clang/libclang/Sema/SemaType.pico Building /usr/obj/usr/src/arm.armv7/lib/clang/libclang/Sema/SemaWasm.pico Building /usr/obj/usr/src/arm.armv7/lib/clang/libclang/Sema/SemaX86.pico Building /usr/obj/usr/src/arm.armv7/lib/clang/libclang/Sema/TypeLocBuilder.pico Building /usr/obj/usr/src/arm.armv7/lib/clang/libclang/Serialization/ASTCommon.pico Building /usr/obj/usr/src/arm.armv7/lib/clang/libclang/Serialization/ASTReader.pico Building /usr/obj/usr/src/arm.armv7/lib/clang/libclang/Serialization/ASTReaderDecl.pico Building /usr/obj/usr/src/arm.armv7/lib/clang/libclang/Serialization/ASTReaderStmt.pico No warnings or errors of any kind appear on the serial console, ever. Is there some other way to get at debugger services in a case like this? I understand it's possible to run programs under debugger "supervision" at the time of invocation, but would that provide any extra avenues to find out what's going wrong? I think not, but I'd like very much to gather some useful information toward a fix. Thanks for reading, bob prohaska