R.3

Incident index

This page lists every issue the manual cites, with its status at 0.31.0.

Use this page to check whether a problem you see is known.

States are as of 2026-10-22. Numbers refer to issues in the vLLM repository.

Issues

IssueWhat it reportsStatePage
44740a negative CUDA graph memory estimate with MTP speculation on the GB10, which makes the KV cache too largeopenDGX Spark
46307memory use above the --gpu-memory-utilization share during the startup profile on the GB10, which stopped the hostclosed as stale on 2026-10-22, with no fixDGX Spark
52479a level 2 wake from sleep that does not reload the speculative draft, so no draft token is acceptedopenRL rollouts
54623the Qwen3.5 family never loads checkpoint KV scales, so an FP8 KV cache runs at scale 1.0openFP8 KV cache
57853a weight update sent while the engine sleeps segfaults the engine coreopenRL rollouts
60333one MTP draft loader drops FP8 KV scales, and the draft layers use scale 1.0openFP8 KV cache
58726slow weight load on the GB10, from per-tensor copies out of the file mapopenDGX Spark
59770slower NVFP4 decode for one model on the GB10 since 0.29.0opentroubleshooting
60174one repeated token after a prefix-cache hit with DFlash2 or DSpark speculation on 0.30 and 0.31closed on 2026-10-22troubleshooting
60262a crash at start when an FP8 KV cache picks FlashInfer without a working kernel buildopentroubleshooting
60830invalid JSON with MTP speculation and a JSON schema on one modelclosedtroubleshooting
60838--mamba-block-size has no effect after the removal of the all Mamba cache modeopenlong contexts
61024the project roadmap for Q4 2026, which lists the removal of the old model runneropenModel Runner V2
61886KV offloading that does not depend on the tensor-parallel sizeopenKV connectors
59538a compression layer for KV transfer and storageopenKV connectors
61229KV blocks released during a remote read in the NIXL connectoropenKV connectors
58253a request for a reviewer role, to raise review capacityopenhistory
61698a request for reproducible evals and benchmarks that contributors run on their own GPUsopenhistory

Our own incidents

DateMachineWhat happenedPage
2026-10-22L4, shared GPUthe start failed, because one request at a maximum length of 2,928 tokens needed slightly more KV cache than was freestartup
2026-10-21GB10the first weight load of 56.93 GiB took 330 secondsDGX Spark

vLLM 0.31.0 · db9527a · 2026-10-05 · Edition 2026.10