rg> List-Unsubscribe: Sender: owner-freebsd-arm@FreeBSD.org Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3826.700.81\)) Subject: Re: Arm v7 RPi2 -current unresponsive to debugger escape during buildworld From: Mark Millard In-Reply-To: Date: Mon, 24 Nov 2025 19:40:21 -0800 Cc: freebsd-arm@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <5EC9F997-541F-4907-B37F-B1EE1BCB8798@yahoo.com> References: To: bob prohaska X-Mailer: Apple Mail (2.3826.700.81) X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Rspamd-Queue-Id: 4dFpPQ5GkKz3YHV On Nov 24, 2025, at 18:07, bob prohaska wrote: > A few minutes ago a Pi2 running buildworld for -current locked up = again, with no > responsie to the debugger escape. >=20 > The system was swapping fairly hard but not stuck, maybe 600 MB in = use, eventually > swap use declined but in minutes it got stuck with top displaying: >=20 > last pid: 51520; load averages: 2.82, 2.96, 2.96 = up 1+02:48:27 16:27:58 > 57 processes: 3 running, 54 sleeping > CPU: 66.4% user, 0.0% nice, 16.0% system, 0.3% interrupt, 17.4% idle > Mem: 183M Active, 540M Inact, 416K Laundry, 175M Wired, 98M Buf, 19M = Free > Swap: 2048M Total, 23M Used, 2025M Free, 1% Inuse >=20 > PID USERNAME THR PRI NICE SIZE RES STATE C TIME WCPU = COMMAND > 51497 root 5 59 0 352M 208M uwait 3 0:08 161.51% = ld.lld > 51518 root 1 101 0 167M 71M CPU1 1 0:03 87.52% = cc > 51520 root 1 59 0 167M 72M RUN 2 0:03 67.88% = cc > 11811 root 1 0 0 6724K 1456K CPU0 0 5:51 0.46% = top > 2047 root 1 0 0 4676K 704K select 0 1:08 0.09% = powerd > 2206 bob 1 0 0 14M 1212K select 0 0:46 0.06% = sshd-session > 2119 root 1 9 0 14M 2320K select 1 1:27 0.00% = sshd >=20 > The over-100% utilization for cpu 3 looks somewhat implausible. It is very plausible based on the above: note that THR (thread count) indicates 5 for ld.lld : It can have more than one core in use at the same time part of the time in order to have 161.51% WCPU. More than core 3 was in use by ld.lld . Some of the information shown is likely specific to the main/original thread. (Top has a display mode that shows one thread per line instead of one process per line. It can also display Thread IDs instead of Process IDs. But PID can sometimes make it easier to identify which threads are part of one process. Non-thread-specific information is replicated. Top can also display more of the command line text.) > Might it suggest anything significant? I haven't seen this from=20 > top in a long time, so relatively speaking it's new behavior.=20 >=20 > There were no console warnings of any kind. =3D=3D=3D Mark Millard marklmi at yahoo.com