igneum-network/igneum
1
0
Fork 0
Code Issues Pull requests Releases Activity

Counter ASIC 2.0 status 01:12: the repro run read as beside the miner, agg-cost-pc2-5 go

Browse source 
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
This commit is contained in:
igneum-labs 2026-10-06 01:10:48 +00:00
parent aae4dbc45b
commit 02ab3d94d6
1 changed files with 4 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
docs/plans/counter-asic-2-status.md
View file

@ -762,3 +762,7 @@ m16-inline-pc2-1 (00:38:54 to 00:43:17Z, 263 s, exit 0; app 0.3.11; the miners r
## 00:59 the chain past DAA 144,000: N4 = N5 = 154,800 is final; the repro run in its tenth minute
The crossing watcher (pid 49195) at 00:55:29Z: DAA 144,209, epoch 40, class v2, 57.9 blocks per minute on the observer (PC 2 at 105 to 116 MH/s and the Mac at about 26 MH/s on the new side). DAA 144,000 is behind the chain, so the 10,800 floor can no longer be re-pinned and N4 = N5 = 154,800 stands as published; at 57.9 blocks per minute the crossing lands at about 03:58Z (10,591 DAA to go at 00:55Z). Machines: PC 2 and the Mac on 0.3.11 at 0139ab9d; the laptop silent since its 23:28:48Z update-now (its install), PC 1 down since 22:31:06Z, Sam's Mac quit at 20:47Z; each takes 0.3.11 and the nine fields at relaunch. PC 2 queue: run-repro-pc2-20261006 running since 00:49:30Z (about 14 min), then agg-cost-pc2-5 (12 min), then the ledger-fixes-0311 suites (about 8 min; I publish it from the ledger-rebase worktree). The final report to main follows the suites' close, about 01:40Z.
## 01:12 the repro run closed; its 5090 rows read as beside the live miner; agg-cost-pc2-5 has its go
run-repro-pc2-20261006 (00:44:29Z fetch, the run 00:49:30 to 01:09:38Z, 1,509 s, exit 0, "all cards restored; done"). The package's bit-exact checks PASS on every backend (fingerprint 25f96e7dce90bd4e at 1 GiB on CUDA, NVIDIA OpenCL and gfx1036 OpenCL; program bcc1248b10cc90f2, 128 loads). The rates: RTX 5090 CUDA 62.412 MH/s (120 s, batch 2^24), 5090 OpenCL 62.283 (30 s), gfx1036 3.312 (the integrated RDNA 2, 1 CU); the memprobes 17.5 G dependent reads per second at 1 GiB on CUDA (chase 1,766 ns), 339 GB/s stream, 13.4 T ALU op/s. The 5090 rows are HALF this card's rate in every other run tonight (M16's honest 132.20 at 00:40Z; the app 105 to 116 wall) and the package's proving step took 33.9 s compressed and 20.2 s core on block-338-shard1 against 16.8 s in sweep 3, so the run most likely shared the card with the app's live CUDA worker: its card-off step reads nothing from /api/state (the "{}" defect) and waits 30 s without confirming a stopped worker. Reading passed to the repro agent to confirm from the job's own worker-count lines; if so, the PC 2 5090 rows are "beside the live miner" rows and the morning re-runs the 5090 block alone (gfx1036 and the memprobes stand). The script's close failed twice (ConvertTo-Json out of memory on the sample set; Set-Content with an empty path for the markdown), so no result file was written on PC 2; every row is in the intake. Package fixes, the class: the card-off step confirms by nvidia-smi's compute-apps list, the writer drops the samples from the JSON. "go PC 2" to agg-cost-pc2-5 at 01:10 (about 12 min), then the ledger-fixes-0311 suites.