vgsp-sema: SESSION 130 xlate regression bisect - the r727 translator regressions were re-tested on a fresh boot: with the translator ON and the utility sweep OFF, victory_saxpy and victory_math PASS with checksums identical to the gate-off baseline (saxpy csum=981440890.500000), so the SESSION 129/130 sweep changes fixed the saxpy/math half; the remaining xlate-on regression is victory_multikernel, whose physical forward times out repeatedly (GR LAUNCH FAILED ... qmd_rel=0xc0ffee01, hold active), so the default stays 0 until that forward path is fixed. The UTILITY SWEEP is the other regression source (util_scan=24 broke saxpy bad=1047527 and hung math) and stays opt-in until its channel reads prefer the direct walk

1 files changed, 16 insertions, 4 deletions

diff --git a/kernel/gsp_sema_service.c b/kernel/gsp_sema_service.c
index 1a844cb..6f005b5 100644
--- a/kernel/gsp_sema_service.c
+++ b/kernel/gsp_sema_service.c
@@ -1866,10 +1866,22 @@ module_param_named(sema_vas_cand_ms, svc_vas_cand_age_ms, uint, 0644);
  * SESSION 127 C5C0 translator gate. When 1, the sweep additionally
  * translates continuation entries into launch work (tail-aware method
  * parse, inline-QMD capture, LOAD_INLINE_DATA materialization, C5B5
- * copy-out capture, candidate-owned release withholding). Default 0 keeps
- * the historical sweep behaviour for the CUDA batteries; the Vulkan
- * translator cycles pass sema_gr_xlate=1. Flip the default once the CUDA
- * battery is proven clean with it on.
+ * copy-out capture, candidate-owned release withholding).
+ *
+ * SESSION 130 re-test of the r727 "translator regressions" (translator on,
+ * utility sweep OFF, r746): victory_saxpy and victory_math now PASS with
+ * checksums identical to the gate-off baseline (saxpy
+ * csum=981440890.500000), so the saxpy/math half of the r727 regression
+ * is FIXED (the SESSION 129/130 sweep changes); victory_mail PASSES. The
+ * remaining xlate-on regression is victory_multikernel: its launch is
+ * captured and submitted to the physical channel but the forward times
+ * out repeatedly (`GR LAUNCH FAILED: timeout after 2000 ms
+ * (qmd_rel=0xc0ffee01 want=0x600df00d ...) h=0x5c000019
+ * push=0x20043c394`, `hold active`), so the client hangs - the default
+ * stays 0 until that forward path is fixed. The UTILITY SWEEP
+ * (`sema_gr_util_scan`) is the OTHER regression source: at 24 it broke
+ * saxpy (`bad=1047527`) and hung math on r745, so it stays opt-in
+ * (default 0) until its channel reads prefer the direct walk over pins.
  */
 static bool gsp_sema_gr_xlate;
 module_param_named(sema_gr_xlate, gsp_sema_gr_xlate, bool, 0644);