Linear attention & SSMs · state-only · training-free

When Dynamic Scaling Fails

A Scale–State Feedback Governs Recurrent-State Quantization in Linear-Attention and SSM LLMs

Yuhang Jiang

Independent Researcher

NeurIPS 2026 Workshop on Long-Context Foundation Models

Read the abstract

Linear-attention and state-space LLMs carry long context in a fixed-size recurrent state, and quantizing that state is the natural way to cut its cost during long decode. Unlike a weight tensor, the state is rewritten at every step, so a quantizer applied at each step sits inside the recurrence and its errors compound. INT4 that leaves synthetic recall perfectly intact at the start destroys it a thousand steps later. The mechanism is a feedback between the quantizer scale and the state it is derived from. Yoking that scale to a full-precision reference removes the resulting norm explosion entirely, yet recovers only 1.8 of the 5.4 nats lost, so numerical instability and functional degradation are separable failures. The remainder is a resolution problem that locating outliers does not solve, since every outlier-aware scheme here loses to plain persistent scaling. Allocating bits across layers does help, but under article-disjoint splits a learned allocation collapses onto the trivial rule of protecting the first few layers. Run out to 32K, group-wise INT4 is worth no more than discarding the state. Contain the scale rather than locate outliers, and report the decode horizon at which a bit-width was certified.

The phenomenon

A bit-width is not safe or unsafe. It is safe for so long.

Quantize the recurrent state at every decode step and ask the model, at the end, for a fact planted before the quantization began. At the moment quantization starts, every bit-width answers perfectly. Drag the horizon and watch where each one lets go.

NIAH recall, 12 seeds — GDN 0.8B

Recurrent-state norm on independent articles, log scale

Per-token dynamic INT4 inflates the state by two to three orders of magnitude. Every static curve sits on the unquantized reference.

Nothing is measured between H=0 and H=1024, so the page draws that span faintly, as the paper does.

The mechanism

The quantizer measures the thing it is damaging

Per-token dynamic scaling reads its scale from the state it is about to quantize. Quantization error inflates the state; a bigger state raises the scale; a coarser grid inflates it further. To test whether that loop is the cause rather than a correlate, we run the same quantizer twice and, in one arm, take the scale from a full-precision reference running alongside — the same grid, the same bit-width, but the loop cut.

GDN 0.8B, 16 held-out articles, H=2048. The 2B model behaves the same way; both are in data.js.

What contains it

Three remedies work, and they are the same remedy

If the loop runs through the scale, anything that stops the scale from tracking the state should help — and what helps says what the loop is made of. Pick an intervention.

Excess NLL at H=2048, paired over 16 articles

Against this: spending the same bits on finding the outliers

Every scheme below is given more information than uniform group-wise scaling, at a matched or higher bit rate. None of them beats it, and giving the extra bits to the most-overflowing channels does not beat giving them to a random subset.

Matched-rate comparison — teacher-forced NLL, lower is better
What is left

With the loop cut, the rest is resolution

Yoking removes the runaway and leaves most of the loss. Two accounts survive that: the grid is too coarse, or rounding error simply accumulates over thousands of steps. They make opposite predictions about bit-width, so we ran it — with the scale yoked, so the feedback cannot confound the sweep.

Yoked residual by bit-width — 16 articles

The trap

Pick the horizon you would have evaluated at

Every policy here is certified on natural text at the horizon you choose. Choose a short one and the verdict is encouraging. The same runs continue to 32K.

Excess NLL against decode horizon, 7 long articles — the dashed line is clearing the state to zero

Where this matters, and where it does not

How much of the decode cache is the state, really?

The recurrent state is a fixed cost; in a hybrid, the attention KV cache next to it grows with context. So the case for quantizing the state is strongest in a pure SSM, and weakest exactly where long-context arguments live. Computed from the published configs.

This is the paper's own limitation, and it is in the Limitations section rather than buried.

Does any of it transfer off the delta rule?

The frontier and the feedback do. Which containment wins does not. Below are the same four policies under the same protocol — 16 held-out articles, H=2048 — on two delta-rule models and one SSM. Read each row against its own dashed control: a policy to the right of it costs more than discarding the state outright.

Excess NLL at H=2048 — dashed line is that model's zero-state control

If you quantize a recurrent state
Contain the scale, do not hunt outliers. A calibrated ceiling bounds the feedback edge, a periodic reset interrupts it, and a persistent scale removes it. Schemes that spend their information locating outliers lose to plain persistent scaling.
Report the horizon a bit-width was certified at. Recall at 2K says nothing about 32K, and short evaluations certify policies as safe long before their failures appear.
Check against clearing the state. A policy that loses to a zero-state control is an expensive way of discarding it. Per-token dynamic INT4 loses to it on all three models, and a single persistent scale loses to it on both delta-rule models and beats it on the SSM.
Cite

BibTeX


    

Non-archival workshop paper. Update this entry if an archival version appears.