vh/esh-pfi-infrastructure
1
0
Fork 0
Code Issues 7 Pull Requests Actions Packages Projects Releases Wiki Activity

memory: snapshot — 2026-10-11 U13 cutover executed + accepted (one card + svos-dev answers open), fv-ml1 hang + evidence capture, stale snapshots gone; 6 entries archived

Browse Source
This commit is contained in:
vh
2026-10-11 13:54:24 -07:00
parent df7161bbe0
commit 5202847abb
12 changed files with 88 additions and 40 deletions
Download Patch File Download Diff File Expand all files Collapse all files
persistent-memory.d/2026-10-11-fv-ml1-hard-hang.md
+3
View File
@@ -0,0 +1,3 @@
# 2026-10-11-fv-ml1-hard-hang
`[2026-10-11]` **fv-ml1 hard hang ~0005, self-reset ~0008, back by 0015 (all seats).** Journal ends mid-normal-operation (no shutdown), pstore empty, SOL shows nothing (no serial kernel console), BMC restart cause `unknown`, SEL only shows the 00:08 boot events (⚠ the BMC clock is 7 h behind, so ipmitool prints them as 17:08 the day before). Idle at the time (Beszel 0004: CPU 0.15%, no Scriberr job). The sp5100 TCO watchdog exists (60 s). infra-ops sent an ACPI soft-off at 00:12:14 believing it still hung; it landed in early boot before logind watched the button, so no effect. Open (Prime): capture evidence next time (serial console on the kernel cmdline for SOL, and/or kdump); the pre-patch snapshot is HELD.