Firmware Update Leaves GB10 Burns 11% Lower, Serving Faster
Petronella updated 8 GB10 units; burns fell about 11% while Qwen3.8-27B serving gained 4% to 8%.
Craig Petronella’s lab halted its benchmark program on September 25 after one GB10 switched itself off under load. Reading firmware across all eight units found at least four different combinations, including one Spark reporting the placeholder 0x00000001 for its embedded controller, SoC firmware and USB-C power delivery. The team updated the cluster as one set through fwupd and apt, canary first, and verified with an independent read-only script.
The numbers cut against intuition. A 15-second fp16 burn fell from 88.6 to 91.4 TFLOPS before the update to 77.6 to 81.3 after. Real serving moved the other way: Qwen3.8-27B on one Spark rose from 23.1 to 25.0 tok/s for one user and 303 to 315 at 32 users. Code decode gained 4% to 7% at every load level; prefill stayed flat and slipped at the longest inputs. The lab’s working explanation: decode is memory bound at 273 GB/s, the burn is compute bound.
The shutdowns did not stop with the update. Spark 1 powered off a second time on new firmware, and Spark 2 and MSI 3 followed, each at or near the start of a very long input. Wall power per outlet caught what log monitoring missed; the dying unit drew 179.6 watts, then 4.36. Seven of eight units carried NVIDIA’s kho=off hotfix package, nvidia-spark-grub-kho. The one MSI unit missing it gained nothing measurable after installation.