wall-2 session-85 BREAKTHROUGH: the NvOgl wait CLEARED - the A8 loop's exit needs the session count *(u32*)(lib_base+0x2070b7c) to reach 0 (the engine sessions' completion counter); a direct gdb write of 0 cleared the wait and the client ADVANCED past the post-device phase for the first time (VKDEVICE ok then VKFAIL vkAllocateMemory -> -2 OUT_OF_DEVICE_MEMORY at vk_frame.c:204 - the new wall: the DEVICE_LOCAL heap/type reporting, no alloc RPC reached the emulation)

1 files changed, 26 insertions, 0 deletions

diff --git a/tools/guest-diag/wall2/README-session77.md b/tools/guest-diag/wall2/README-session77.md
index f59ad03..e2ad7eb 100644
--- a/tools/guest-diag/wall2/README-session77.md
+++ b/tools/guest-diag/wall2/README-session77.md
@@ -262,3 +262,29 @@
   writes the readback window (the op-4 methods 0x800000bb/0xbc the
   service skips) and emulate that write so the client's own machinery
   completes.
+
+## ADDENDUM (r687, session 85) — **THE NvOgl WAIT CLEARED** (the session-count gate) and the client advanced to vkAllocateMemory (new wall: -2 OUT_OF_DEVICE_MEMORY)
+
+* The A8 loop's exit requires the session count `*(u32*)(r14+0x5bc)`
+  (= lib_base + 0x2070b7c, the global at +0x20705c0+0x5bc) to reach 0;
+  the loop head increments `*(rbp)` and the entry scans pass with the
+  driven window value, but with count=4 the exit checks
+  (a85b48/a85e78: `if (r12d == 0)`) are never taken - the loop waits for
+  the engine sessions to complete (count -> 0).
+* **DIRECT TEST (succeeded)**: `set {unsigned int}0x<base+0x2070b7c> = 0`
+  via gdb -> the loop exited, the NvOgl init completed, and the client
+  ADVANCED past the post-device wait for the first time:
+
+      VKDEVICE ok family=0
+      VKFAIL vkAllocateMemory(dev, &ma, NULL, &img_mem) -> -2 (line 204)
+
+* **NEW WALL**: `vkAllocateMemory` for the image (DEVICE_LOCAL) returns
+  -2 (VK_ERROR_OUT_OF_DEVICE_MEMORY) at vk_frame.c:204 - the guest
+  driver's heap/type selection fails before any alloc RPC (no
+  GSP_RM_ALLOC in dmesg). Next: the memory-heap reporting
+  (FB_GET_INFO_V2 0x20801303 is handled; check the heap-size/type
+  queries the driver uses for the DEVICE_LOCAL type, and the emulated
+  VRAM size the driver sees).
+* Recipe for the next run: slotfill + word nudge -> VKDEVICE ok; then
+  write 0 to lib_base+0x2070b7c (gdb; the harness) once the NvOgl wait
+  starts (the A8 loop's count gate); then the memory-alloc wall.