Files
LithosAnanke/logs/20261119-ci-snapshot
Claude 13fae6df30 qemu_session.py: the CPU snapshot also dumps the code at each PC
Eight words at the PC, by its address, name the function offline. The
image loads where the firmware puts it, and the boot does not print
that address. aarch64's monitor has no $pc, so the address is taken
from the register line; checked on a real, paused QEMU.

Test first: the snapshot test, 6 checks; the new one failed before.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017RzZgrf7V7Zk2iczBXDRbm
2026-11-19 02:32:21 +00:00
..

The CI aarch64 BIRTH stall, 2026-11-18/19 (Captain Bob: "Measure, then fix"; then "Diagnose on CI").

CI's Acceptance has failed on aarch64 at "BIRTH: node 11 born from Hera" on every head since 58d0e887
(jobs 828, 835, 840, 850): the birth does not finish within the session's 300 s wait. POST passes there.

Here it does not reproduce:
- host mesh boot: a birth is 0.045 s and 374,589 fabric steps (nucleus 7,515 cells);
- local aarch64 boots (unsigned): the birth in about 11 s, background or foreground
  (local-aarch64-birth-timeline.txt; logs/20261118-235613/);
- an instrumented scratch kernel (counters in the mesh's heart()): one ticking node, the heartbeat at
  most 0x203 ticks behind once at the prompt and then keeping up -- no catch-up spiral.

The one known difference: CI signs its capsules and checks each signature at open; a birth checks one
(forth79.4th), about 7 s on CI's aarch64 by its boot's timing -- not 300 s.

So qemu_session.py now prints where the CPUs are when a check fails (cpu_snapshot: the monitor's
registers three times, a second apart), and CI's next failure will show it.
Test first: scripts/test_qemu_session_snapshot.sh (test-before.log: 3 failures; test-after.log: PASS).
The monitor's register text was checked on real QEMU, paused with no kernel: aarch64 "PC=", riscv64
"pc", x86 "EIP"/"RIP" -- all matched.