From 7c12eb7c85de5ce506f4ad3e234b6ad98832c821 Mon Sep 17 00:00:00 2001 From: Arthur Hanson Rasmusson Date: Thu, 1 Oct 2026 08:47:09 -0400 Subject: STATE-CURRENT: FWSEC carve milestone; fail-safe teardown limit; approved reboot for restoration --- STATE-CURRENT.md | 9 +++++++++ 1 file changed, 9 insertions(+) (limited to 'STATE-CURRENT.md') diff --git a/STATE-CURRENT.md b/STATE-CURRENT.md index ffa2dde..131cf6e 100644 --- a/STATE-CURRENT.md +++ b/STATE-CURRENT.md @@ -47,6 +47,15 @@ chain succeeds. passes end-to-end (`ALL OK`, payload 64/64) with real releases (`faked=0`, `miss=0`, `stale=0`), confirming the recent pump/parser and rewind changes did not regress the baseline. +- **Physical-backend milestone (2026-10-01)**: the module-owned GPU path + reached the first successful secure-verification (FWSEC) carve of the + protected region on the real TU104 under the verified D0 power-domain + harness. The teardown of a FWSEC-only carve is not host-recoverable on this + fused part, so the GPU is left in the documented fail-safe (protected + region up, distribution driver deliberately not rebound) and is being + restored by an approved reboot; the next stage is a single-cycle real boot + (secure verification -> bootloader -> RISC-V start -> resource-manager + initialization) so the normal boot lifecycle makes teardown valid. - **The full CUDA driver-API smoke test passes with correct data**: the client completes `cuCtxCreate -> cuMemAlloc -> cuMemcpyHtoD -> cuMemcpyDtoH -> cuMemFree -> cuCtxDestroy` and prints `ALL OK`, with the 64-byte payload -- cgit v1.2.3