Data and AI struggles

1,348 problems · 309 companies

MLOps

Trouble with vLLM kernel

2 posts from 2 people2d activeFading, +0 this weekunverified

Posts per day

Posts per day2 posts, Oct 2 to Oct 29

The posts behind it

GitHub issuesvllm-project/vllm · Justee21Oct 7

[Bug]: CUTLASS MoE kernel benchmarks fail with ImportError: cannot import name 'fused_topk'

### Your current environment Not environment-specific: this is an import error in the benchmark scripts themselves, reproducible on any machine with vLLM installed from source (checked on `main` at 32fbfa1). ### 🐛 Describe the bug Three CUTLASS MoE kernel benchmarks crash at...

1 reactions1 replies
GitHub issuesvllm-project/vllm · SeverinVisionaryOct 2

[Bug][CPU] apply_top_k_top_p_triton drops tokens that top-p must keep (kernel logic; reproduces end to end on V1 and V2)

### Your current environment vLLM main `98b29aa99` (also `e6674262f`, `4056c8ac1`, `015497965`, `8e58ac22a`), CPU build (`VLLM_TARGET_DEVICE=cpu`), torch 2.13.0+cpu, bundled triton-cpu 3.8.0, Python 3.12, Linux x86_64 (Intel Xeon @ 2.10GHz, AVX512). `HAS_TRITON` is true, so...

1 replies

Companies and products named

2 posts
1 post
About this problem

Evidence

2 posts from 2 people in 1 place, about 2 a week over 6 days. Mostly on vllm-project/vllm. Tools named alongside: NVIDIA.

Frustration Frustration 0 of 3· Seen on GitHub issues

How it was grouped

Posts about vLLM with no known issue, sharing the word "kernel". First post Oct 2, 2026, latest Oct 7, 2026. Unverified: fewer than 3 posts, or one person or place only. Method

Other vLLM problems

Running vLLM locally hits memory and speed limits

13 posts from 13 people on GitHub issues, Reddit.

vLLM upgrades break working setups

17 posts from 17 people on GitHub issues.

Trouble with vLLM cache

Top post: "AOT compile cache never loads for Qwen3.5 models: Kernel index 1 not found in id_to_kernel", one of 4 posts from 4 people on GitHub issues.

vLLM runs out of context on real work

5 posts from 5 people on GitHub issues.

vLLM vulnerabilities are hard to triage and patch

3 posts from 3 people on Glyph Ibis.

vLLM users keep filing bugs

Top post: "Qwen3.8-flash-next 0% MTP acceptance rate in disaggregated PD serving", one of 44 posts from 40 people on GitHub issues, Reddit.

vLLM GPU access and drivers are painful

5 posts from 3 people on GitHub issues.

Trouble with vLLM performance

Top post: "Waiting requests re-walk their whole prefix-cache hit on every scheduling step", one of 3 posts from 3 people on GitHub issues, Reddit.

RAG on vLLM returns irrelevant or missing context

3 posts from 3 people on GitHub issues.

Trouble with vLLM installation

Top post: "v0.30.0 CPU wheels now require manylinux_2_39 (glibc 2.39), breaking installation on Ubuntu 22.04/Rhel9", one of 3 posts from 3 people on GitHub issues.

Trouble with vLLM decoding

Top post: "Support Qwen3.x MTP (Multi-Token Prediction) for speculative decoding", one of 3 posts from 3 people on GitHub issues.

Fine-tuning vLLM is costly and unpredictable

3 posts from 3 people on GitHub issues.

History

First seen with 2 posts; the top post now: "CUTLASS MoE kernel benchmarks fail with ImportError: cannot import name 'fused_topk'".

Oct 29, 2026