vh/forgefirm
1
0
Fork 0
mirror of https://github.com/openglow-org/forgefirm.git synced 2026-09-27 08:41:13 -07:00
Code Issues Packages Projects Releases Wiki Activity

docs: the forced kernel hang and the two measurements closed

Browse Source 
CAMPAIGN-LOG: the forced hang on image 20260902144848 with its times,
the watchdog register read back, U-Boot's recovery branch (the purple
button), the recovery image on the lease, and the power cycle back; the
pad measurement dropped by decision. BRINGUP item 9: both measurements
closed; the pushes, the pins, one build and the campaign on that image
remain.
This commit is contained in:
ScottW514
2026-09-02 18:30:38 -04:00
parent 61f44011aa
commit 380f67d666
2 changed files with 40 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/BRINGUP.md
+7 -3
View File
@@ -1360,9 +1360,13 @@ pump flag. Beam detect stays with item 6.
The session's queues are green on image 20260902144848, the unattended
set and the attended set both (2026-09-02); the harness and diagnostic
defects they found are fixed in local commits (the dated record is in
CAMPAIGN-LOG). Owed now: the two bench measurements below, the pushes in
CI order, the pin bumps, one image build, and the campaign on that image,
which the release gate asks for.
CAMPAIGN-LOG). The two bench measurements are closed: the connector pads
were not measured (the device tree carries the factory's pad configuration
and the factory machine shows no trouble there, the operator's decision),
and the forced kernel hang ended in the factory recovery after the 60 s
watchdog with a power cycle returning, as documented. Owed now: the pushes
in CI order, the pin bumps, one image build, and the campaign on that
image, which the release gate asks for.
Decisions taken in the remediation that the operator confirms or reverses:
the release image has no shell login (the install page now says so); the
cloud client holds and resumes on the cooling verdict with a 30-minute