logs: three riscv64 boots of v4.0.0-alpha.2, looking for run 197's failure

Browse Source

Acceptance run 197 (#130) failed one riscv64 check: no 'Boot disk: not a
StarshipOS stick' line, with POST, the identity and the prompt all passing.
Booted three more times here on the same tree: each printed the line and
passed (4 of 4 with logs/20261107-184616). The Zuse stick has no ESP
(--esp-mib 0), so the firmware cannot have booted from it; the serial
capture losing or garbling the line is what is left to check, against run
197's own log.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01GE3SDvQn5EoxdGufk84zz2

...

This commit is contained in:

Claude

2026-11-07 19:15:04 +00:00

parent cabe974872

commit 37f62d688b

6 changed files with 9 additions and 0 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download Patch File Download Diff File Expand all files Collapse all files

experiments/bare_metal/runs/doe-riscv64-20261107-190906.csv

experiments/bare_metal/runs/doe-riscv64-20261107-191105.csv

experiments/bare_metal/runs/doe-riscv64-20261107-191304.csv

logs/20261107-190906/riscv64/qemu-riscv64-20261107-190906.log

LFS

BIN

Binary file not shown.

logs/20261107-191105/riscv64/qemu-riscv64-20261107-191105.log

LFS

BIN

Binary file not shown.

logs/20261107-191304/riscv64/qemu-riscv64-20261107-191304.log

LFS

BIN

Binary file not shown.