Skip to content

Glitch Token and MiniMax-M2 ​

MiniMax-M2 had a visible failure around 马嘉祺: it could often describe the person, but the generated name was unstable, 嘉琪 was replaced by 俊杰 or 佳琪, the token was avoided by llm purposely. MiniMax-M2.7 was later reported to fix this case. Here are some possible explanations of this interesting phenomenon.

The team found that: token of 嘉祺 has high cos cimilarity of lm_head logits after pre-training, but switched extremely low after SFT. Then somnething must happen in SFT(post-training) !

LM Head Drift ​

The output logit for token i is:

zi=h⊤wi+bi

For cross entropy, the gradient on wi is approximately:

∂L∂wi=(pi−1i=y)h

Target tokens receive strong updates. Non-target tokens receive weaker updates, especially when pi is small. During SFT/RLHF, common instruction tokens, format tokens, punctuation, and high-frequency text are updated often. Rare characters and rare name paths receive much less direct correction.

At the same time, the transformer body continues to move:

hpretrain→hposttrain

The issue may be relative drift:

∥Δwrare∥≪∥Δh∥

The logit change can be expanded as:

Δzi=(Δh)⊤wi+h⊤Δwi+(Δh)⊤Δwi

For a rare token, Δwi can be small, so (Δh)⊤wi may dominate. My short version of the mechanism is: representation drift plus sparse supervision may produce logit anomalies.

This also explains why "all parameters are trained together" is not enough. They are in one system, but they may not be updated at the same rate.

POST-TRAINING DATA MATTERS !

Fix ​

One possible fix is to repeat or upsample SFT examples that contain rare-token vocabulary. This may reduce LM head drift by giving those rare output directions more post-training supervision. Similarly, increasing post-training coverage for Japanese, Russian, and other low-resource-language tokens may reduce both drift and glitch-token behavior.

The key question is whether this becomes a one-off patch or a broader eval category. If the self-evolution loop turns a user-visible failure into systematic coverage, the fix is more valuable than the single corrected name.

This drift also has a linguistic analogy: a word can change meaning even if its written form stays unchanged, because the surrounding semantic system has moved. This is similar to semantic drift across historical stages of a language.

Architecture ​

Tokenizer quality matters, but I would not put the whole problem there. The final behavior may depend on tokenizer segmentation, pretraining coverage, post-training distribution, LM head calibration, MoE routing, quantization, sampling, and logit processors.

For MoE models, routing adds another discrete layer. A small router or numerical difference may change the hidden state, then change the ranking among similar low-frequency tokens.

The metric I would add here is vocabulary health. Math, code, and agent benchmarks do not tell us whether long-tail tokens are calibrated. Exact copying, Unicode, multilingual names, file paths, and low-frequency character sequences should be measured separately.

Takeaway ​

Glitch-token behavior may not be only a tokenizer corner case. It may be a mismatch between continuous representation space and discrete symbol reproduction.

For ordinary generation, semantic tolerance hides the mismatch. For names and exact strings, it becomes visible.

References ​