- Rating
- 2
- Confidence
- 3
- Informativeness
- 3
- Presentation
- 2
- Soundness
- 2
Read review
Paper summary
The paper investigates how numerical errors from different sources can lead to attention instability through a shared query–key pathway. Using a reproduced BF16 streaming-accumulator fault and controlled weight-gradient quantization, it studies QK spectral growth through gradient replacement and direction-specific interventions. It also introduces QKGuard, which monitors attention logits and permanently enables parameter-free per-head QK normalization after a threshold crossing.
Critical strengths
-
The paper goes beyond correlating spectral growth with training collapse. Selective QK-gradient correction while leaving the fault active, together with direction-specific interventions and matched-energy controls, provides meaningful causal evidence for the QK pathway in the tested settings.
-
The protection mechanism is evaluated across multiple architectures, fault locations, seeds, and training horizons. Matched guarded and unguarded runs, along with longer-duration experiments, strengthen the evidence that QK normalization can prevent collapse under the studied conditions.
Critical weaknesses
-
The practical representativeness of the failure settings remains insufficiently established. The initial collapse arises in a particular implementation that stores streaming-attention carries in BF16, whereas standard FP32-accumulating implementations do not collapse within the reported comparison windows. Additional evidence primarily uses controlled post-reduction weight-gradient quantization. These experiments are useful for causal analysis, but do not establish how frequently the identified pathway is consequential in commonly used, correctly implemented low-precision training workflows. This limits the demonstrated practical scope of QKGuard.
-
The incremental benefit of threshold-triggered protection over established, always-on QK normalization is unclear. QKGuard leaves the numerical error source active and intervenes downstream; preventing collapse therefore does not by itself establish recovery of fault-free training quality. The reported closeness to always-on QK normalization supports the effectiveness of delayed intervention, but does not establish a clear advantage in quality, efficiency, or preservation of the original training behavior. The mechanism analysis is more compelling than the demonstrated added value of the proposed deployment strategy.
Questions for authors
-
Do the existing experiments include naturally occurring instability in a standard low-precision training pipeline without the BF16-carry implementation or imposed post-reduction gradient quantization? If so, please identify the configuration and evidence connecting that instability to the same QK pathway. Otherwise, please clarify the intended scope of the practical claims.
-
What measurable benefit does QKGuard provide over always-on QK normalization? Please clarify whether the current results establish an advantage in training quality or total runtime, including monitoring overhead, and how guarded endpoints compare with a fault-free reference rather than only an always-normalized reference.
Reply to Reviewer 2eam: standard training pipelines and what the switch adds
Thank you for the review, and for crediting the causal design.
Yes. The new §2.2 shows that PyTorch's fused bf16 attention, with no injected error and no custom kernel, collapses GPT-2 small when the learning rate stays near its peak without weight decay.
All 6 runs at peak learning rates 6e-4 and 8e-4 collapse. The kernel is PyTorch's own scaled-dot-product attention under bf16 autocast, which accumulates in fp32. The instability follows the same QK pathway as the faulty kernel: σ(WQ) starts to run away before every collapse, from under 10 to peaks over 400, and switching on QK normalization when the monitored attention-logit statistic crosses 30 rescues all 6 runs. With attention computed explicitly in fp32 and everything else unchanged, none of 6 runs collapses. The weight-gradient experiments you mention ran on this same fused path, and as our general comment explains, the revision now reports them as fused-attention runs.
No. The current results show no advantage over QK normalization from the start in training quality and do not establish one in runtime.
As point 2 of our general comment explains, the revision presents the switch as a test of the analysis, which we agree is the stronger part of the paper. Guarded runs end where runs with QK normalization from the start end, and also close to runs in which the error is removed. Under fused attention, guarded runs reach validation loss 3.20–3.26, and runs of the same recipe with fp32 attention 3.18–3.25. With the faulty kernel at 350M, switching on QK normalization when the statistic crosses 30 ends at 4.04 train loss, and switching the kernel's computation to fp32 at the same moment ends at 4.03. For runtime, Appendix C shows that monitoring adds no measurable time per update, and after the switch the run pays the cost of QK normalization.