Field noteOct 27, 20261 min read1 source

Humming block-FP8 path fails DeepSeek-V4.1-Flash on Hopper at tensor parallel 4 and 8

In one minute

vLLM maintainer Michael Goin reported an open bug affecting DeepSeek-V4.1-Flash on NVIDIA Hopper GPUs when Humming block-FP8 MoE activations are used with pure tensor parallelism of 4 or 8.

What changed: A new issue reports that Humming’s block-FP8 MoE path fails to start DeepSeek-V4.1-Flash on Hopper at tensor parallel sizes 4 and 8, exposing a compatibility limitation not stated in the Humming announcement.

The report used eight NVIDIA H200 GPUs, CUDA 13.0, PyTorch 2.14.0+cu130, humming-kernels 0.1.18, and a vLLM build from main. Startup fails during profiling with an AssertionError because the model's MoE intermediate size of 2304 becomes a per-rank K dimension of 576 at TP=4 or 288 at TP=8; neither is divisible by the 128-element input-scale group. TP=1 and TP=2 are listed as working, as is expert parallelism.

The issue says vLLM already pads expert K to a multiple of 128, but Humming must support the remaining partial scale group. A Humming GEMM fix is merged and a quantization fix remains draft, with a Humming release and vLLM dependency bump still planned. Main-branch Hopper serving defaults to BF16 activations, so that default path is described as unaffected. The report does not establish a release date for the fix or confirm the behavior across other models, GPU architectures, or deployments.

Evidence / sources

  1. 1github.com/vllm-project/vllm/issues/63793
All Field Notes

Next reads

Read next

Open the graph
  1. 01topicInferenceExplore the inference topic hub.
  2. 02topicModelsExplore the models topic hub.
  3. 03archiveField NotesOpen the latest editorial analysis.
  4. 04source ledgerSource LedgerInspect the public source evidence graph.
Who read this page?Machine requests, hidden until opened

Loading the privacy-safe route aggregate...

Open the JSON contract