logs: the protocol on 36b25805 -- FAIL: aarch64 BIRTH stalled here too; the repro boot that caught it
accept-aarch64 failed at BIRTH. The new CPU snapshot showed the kernel looping, not hung. The other stages passed, including riscv64, the stick, test-32, the proofs and the images. I ran them before reading aarch64's result, which was the wrong order. The repro boot (logs/20261119-012050) gave the code at each PC. Matched in the loader EFI's map, they name bitmap_get inside stadium_resident_heat_total, then background_decay and isqrt64. That is the heartbeat's load, which walked all 335,544 Stadium cells every tick. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_017RzZgrf7V7Zk2iczBXDRbm
This commit is contained in:
Reference in New Issue
Block a user