deepseek-ai/DeepGEMM
1
0
Fork 0
mirror of https://github.com/deepseek-ai/DeepGEMM.git synced 2026-11-05 00:47:26 +00:00
Code Issues 162 Projects Packages Wiki Activity

[GH-ISSUE #140] VLLM Integration: Assertion error csrc/jit_kernels/impls/smxx_layout.hpp:136 'mn % 4 == 0 and num_groups == 1' #80

New issue
Closed
opened 2026-10-26 21:12:03 +00:00 by bsakaguchi · 1 comment
bsakaguchi commented 2026-10-26 21:12:03 +00:00
Owner
Copy link

Originally created by @yewentao256 on GitHub (Jul 24, 2025).
Original GitHub issue: https://github.com/deepseek-ai/DeepGEMM/issues/140

Purpose

This error will appear/disappear with the same code using vllm with different version of DeepGEMM

So could someone give me more context about this? Is this a bug inside DeepGEMM, or the caller should update the way of using it.

Ways to reproduce

https://github.com/vllm-project/vllm/pull/21559, use this unit test code.

If we downgrade DeepGEMM to https://github.com/RayWang96/DeepGEMM/tree/multi_arch_support with commit cc416ee4fa, the unit will pass.

If we are using main branch:

E       RuntimeError: Failed: Assertion error csrc/jit_kernels/impls/smxx_layout.hpp:136 'mn % 4 == 0 and num_groups == 1'

../../../vllm/utils/deep_gemm.py:111: RuntimeError
Originally created by @yewentao256 on GitHub (Jul 24, 2025). Original GitHub issue: https://github.com/deepseek-ai/DeepGEMM/issues/140 ## Purpose This error will appear/disappear with the same code using vllm with different version of DeepGEMM So could someone give me more context about this? Is this a bug inside DeepGEMM, or the caller should update the way of using it. ## Ways to reproduce https://github.com/vllm-project/vllm/pull/21559, use this unit test code. If we downgrade DeepGEMM to https://github.com/RayWang96/DeepGEMM/tree/multi_arch_support with commit cc416ee4faf0533a9263c2de814e5565f56ca1cc, the unit will pass. If we are using main branch: ```bash E RuntimeError: Failed: Assertion error csrc/jit_kernels/impls/smxx_layout.hpp:136 'mn % 4 == 0 and num_groups == 1' ../../../vllm/utils/deep_gemm.py:111: RuntimeError ```
bsakaguchi commented 2026-10-26 21:12:04 +00:00
Author
Owner
Copy link

@LyricZhao commented on GitHub (Jul 30, 2025):

After #141, I believe it is fixed. Thanks! Feel free to reopen it if the issue remains.

<!-- gh-comment-id:3135031492 --> @LyricZhao commented on GitHub (Jul 30, 2025): After #141, I believe it is fixed. Thanks! Feel free to reopen it if the issue remains.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
public-sync-20261014
0930-release
nv_dev
fix-mega-moe-fence
public-release-2609
public-release-2607
public-release-2606
mega-update
public-release-260416
ko3n1g/ci/build-wheels
nv_dev_f8e8fb5
nv_dev_950d31a
nv_dev_67fc648
nv_dev_c491439
nv_dev_4ff3f54
v2.1.1.post3
v2.1.1.post2
v2.1.1.post1
v2.1.1
v2.1.0
Labels
Clear labels   
pull-request
Mirrored from GitHub Pull Request

No labels
pull-request
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
deepseek-ai/DeepGEMM#80
No description provided.