From nobody Thu Nov 06 14:45:01 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 4d2Q2w2fvVz6GG7h; Thu, 06 Nov 2025 14:45:12 +0000 (UTC) (envelope-from ronald-lists@klop.ws) Received: from smtp-relay-int-backup.realworks.nl (smtp-relay-int-backup.realworks.nl [87.255.56.188]) (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 did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4d2Q2v4Cdbz44kR; Thu, 06 Nov 2025 14:45:11 +0000 (UTC) (envelope-from ronald-lists@klop.ws) Authentication-Results: mx1.freebsd.org; none Received: from smtp-relay-int-backup.realworks.nl (crmpreview7.colo2.realworks.nl [10.2.52.37]) by mailrelayint2.colo2.realworks.nl (Postfix) with ESMTP id 4d2Q2k3P7bz1j2; Thu, 6 Nov 2025 15:45:02 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=klop.ws; s=rw2; t=1762440302; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=6CAA5KT1mRxHjvgbXe1hANzHDIbPZ/4JMOZY1dZSxpA=; b=Mu3d+jYw7jn/cNtLaOoTrmLVd3krPny8qSUy2E40YuvLekp49IKz75sxDkIuebwNgfCkAu gCX9Um4Nn9EF6Kxg3AkkWOUF3c72cdU7pB8MJ+lkBtCNisnzHyyVSFT76DRihkChRdhhKF a9u3OwIaTllw7Vyi3D1ah5Sc4vLvVXbW/a1q2+VnJbs7skJr/DthqhaJjJpvO/A15scBF0 Z9tX8b6yePjbsDPdPnUVwVumRhBwAcH5AprzN5lkNF6Ovn+xbF2nXuz776dc673VACOSMe 2Rs473BMM0j46RTkcKP3AbF6k1mFqTFKkq+Xcnur9Mv4zOmHJjnQGXqsVB1YaA== Received: from crmpreview7.colo2.realworks.nl (localhost [127.0.0.1]) by crmpreview7.colo2.realworks.nl (Postfix) with ESMTP id EF22F18024D; Thu, 6 Nov 2025 15:45:01 +0100 (CET) Date: Thu, 6 Nov 2025 15:45:01 +0100 (CET) From: Ronald Klop To: bob prohaska Cc: freebsd-current@freebsd.org, freebsd-arm@freebsd.org Message-ID: <475995705.6919.1762440301455@localhost> In-Reply-To: References: Subject: Re: Arm v7 RPi2 -current unresponsive to debugger escape during buildworld 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: multipart/alternative; boundary="----=_Part_6918_2102122641.1762440301376" X-Mailer: Realworks (772.17) X-Originating-Host: from (83-81-212-149.cable.dynamic.v4.ziggo.nl [83.81.212.149]) by crmpreview7.colo2.realworks.nl [10.2.52.37] with HTTP; Thu, 06 Nov 2025 15:45:01 +0100 Importance: Normal X-Priority: 3 (Normal) X-Originating-User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:144.0) Gecko/20100101 Firefox/144.0 X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:38930, ipnet:87.255.32.0/19, country:NL] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Rspamd-Queue-Id: 4d2Q2v4Cdbz44kR ------=_Part_6918_2102122641.1762440301376 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Hi, To me it sounds like your machine is overwhelmed by swapping. Try -j1 buildworld. Regards, Ronald. Van: bob prohaska Datum: donderdag, 6 november 2025 15:04 Aan: freebsd-arm@freebsd.org CC: freebsd-current@freebsd.org Onderwerp: Arm v7 RPi2 -current unresponsive to debugger escape during buildworld > > 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 > > > > > > > > > > > ------=_Part_6918_2102122641.1762440301376 Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit Hi,

To me it sounds like your machine is overwhelmed by swapping.

Try -j1 buildworld.

Regards,
Ronald.

 

Van: bob prohaska <fbsd@www.zefox.net>
Datum: donderdag, 6 november 2025 15:04
Aan: freebsd-arm@freebsd.org
CC: freebsd-current@freebsd.org
Onderwerp: Arm v7 RPi2 -current unresponsive to debugger escape during buildworld

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






 
 

  ------=_Part_6918_2102122641.1762440301376--