vllm - 💡(How to fix) Fix [Bug]: setting kv_cache_dtype to fp8 or fp8_e4m3 causes the d node to crash

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
RAW_BUFFERClick to expand / collapse

Your current environment

vllm v0.21.0 module: deepseek-v3-fp8

🐛 Describe the bug

<img width="793" height="363" alt="Image" src="https://github.com/user-attachments/assets/9ce8097c-b4b5-45f8-a80e-c55811643218" /> <img width="1413" height="217" alt="Image" src="https://github.com/user-attachments/assets/5a52f51c-2d5e-4c64-b005-f76d4c67d772" />

Data writes are normal. When using lmcache with the mooncake backend as an external KV cache, the write data type is uint8.

<img width="792" height="308" alt="Image" src="https://github.com/user-attachments/assets/63736c29-f78a-4b30-b3da-dbb275eb608f" />

Before submitting a new issue...

  • Make sure you already searched for relevant issues, and asked the chatbot living at the bottom right corner of the documentation page, which can answer lots of frequently asked questions.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

vllm - 💡(How to fix) Fix [Bug]: setting kv_cache_dtype to fp8 or fp8_e4m3 causes the d node to crash