STATE-CURRENT: 10:55 check-back - H1 promote-ctx wedge, designed locked fail-safe hold, green-eye wave 2

1 files changed, 28 insertions, 6 deletions

diff --git a/STATE-CURRENT.md b/STATE-CURRENT.md
index ae7fb95..7aaf9f1 100644
--- a/STATE-CURRENT.md
+++ b/STATE-CURRENT.md
@@ -1,6 +1,6 @@
 # Open-IOV Current State
 
-> **Snapshot: 2026-10-02 09:25.** This is a dated public status page, not live
+> **Snapshot: 2026-10-02 10:55.** This is a dated public status page, not live
 > state; it is refreshed on every progress check. Live working notes are
 > maintained outside this repository; the public known-knowns/unknowns document
 > is authoritative here:
@@ -81,6 +81,23 @@ chain succeeds.
 
 ## Right now (frontier)
 
+- **Host is parked in the designed locked fail-safe; reboot pending approval
+  (2026-10-02 ~10:07, user hold ~10:25).** The GR context-promote retry
+  (default-off follow-up to the H1 host GR ladder) went green through
+  boot/READY, the GR context queries, a zeroed 307-page context buffer with
+  its page-directory mapping and the GR0 channel + compute object, but the
+  server-side `GPU_PROMOTE_CTX` request **wedged the resource manager** (an
+  internal assert `0x52a8b04`, no reply, no engine fault), so the ladder
+  aborted by design. Teardown could not clear the protected region (the
+  booter-unload gate needs a handoff bit the wedged server never sets; the
+  host-side unlock is fuse-locked on this part), so the module refused the
+  hand-back and kept the power-domain locks: module unloaded, GPU unbound,
+  protected region still up, `nvidia-smi` unavailable. This is the fail-safe
+  working as designed - host stable, no freeze, pstore empty, no rail
+  cycles. The acting session deliberately paused here; the reboot request is
+  awaiting approval because other work is running, and no further live GPU
+  cycles are planned this boot. The promote-assert bisection plan is ready
+  for the next boot.
 - **Guest-submission relay and fault replay landed, default off (P6c
   C0/C1/C3, 2026-10-02 07:43-08:07).** With `gsp_phys_relay=1` the physical
   engine authors the guest CE copy and the release semaphore: the
@@ -106,7 +123,10 @@ chain succeeds.
   0 rail cycles, same boot). Current wall: make the GR engine execute the
   submitted compute block - bisect GR allocation parameters, the release
   method encoding and the method order/context init, using the drained GR
-  fault records. Next: host `vectorAdd`, then guest GR forwarding.
+  fault records. The timeout was then root-caused to an uncommitted GR engine
+  context (`CTXNOTVALID`); the follow-up promote-context attempt wedged the
+  server - see the top bullet. Next: host `vectorAdd`, then guest GR
+  forwarding.
 - **Experimental tooling: green-eye (2026-10-02 08:36, in development).**
   `debug/risc-v-gsp-rm-vm/` boots GSP/uproc firmware in a RISC-V QEMU VM
   with a GDB stub and adds Frida-like runtime inspection, a scripting/plugin
@@ -712,9 +732,10 @@ Work execution (host service vs client synchronization):
            exactly-once release, engine-authored release semaphores and
            forwarded-fault relay (all default off; one relay data-mismatch
            under triage; software fail-closed fallback remains); a host GR
-           ladder allocates a GR channel + compute object but its first GR
-           submit timed out - real guest page tables/channels and GR
-           execution remain
+           ladder allocates a GR channel + compute object but the first
+           submit faulted `CTXNOTVALID` and the promote fix wedged the server
+           (host parked in the locked fail-safe pending an approved reboot) -
+           real guest page tables/channels and GR execution remain
  [not yet] correct results (vectorAdd)
 ```
 
@@ -744,7 +765,8 @@ Recent chain of walls removed (2026-09-28 to 2026-09-30):
       backend bring-up -> real GSP-RM session -> host RM client -> real CE copy
       on the physical engine -> guest CE copies hardware-authored with
       engine-authored releases -> forwarded-fault relay -> host GR ladder
-      -> GR execution is the next wall
+      -> GR ctx CTXNOTVALID fault -> promote-ctx server assert + designed
+      locked fail-safe (reboot pending) -> GR execution is the next wall
 ```
 
 ## Tools, code paths and fixes behind this progress