mirror of
https://github.com/deepseek-ai/DeepGEMM.git
synced 2026-11-05 00:47:26 +00:00
[GH-ISSUE #147] [bug] Unspecified Launch Failure of Normal GEMM when n=16 #85
Labels
No labels
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
deepseek-ai/DeepGEMM#85
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Chtholly-Boss on GitHub (Jul 30, 2025).
Original GitHub issue: https://github.com/deepseek-ai/DeepGEMM/issues/147
The refactoring of the repo seems to introduce a bug when
n=16, here is the minimal reproducible steps:tests/generators.py, modify the normal generator as:tests/test_core.py, only enable thetest_gemm:Then in the project root, run
PYTHONPATH=. python3 tests/test_core.py, and we get the output as:DG_JIT_DEBUGmessages like follows:I doubted there might be a bug related to TMA multicast logic in the impl. In this case, we launch 10 SMs but only 9 have works to do. However, when TMA loading done, B8 will wait the empty barrier which need B9 to arrive like:
But B9 has no work to do, it will never "arrive" the empty barrier.
However, when I try to reproduce this in the repo before refactoring, I failed.
I am confused about what happened...
BTW, when m=2112, this also happens.
@LyricZhao commented on GitHub (Jul 30, 2025):
Thanks! @yukuai26 please follow this up.
@yukuai26 commented on GitHub (Aug 1, 2025):
@Chtholly-Boss Hello, thank you for your bug report. We have fixed this issue in our latest PR #149. Please give it another try. Since this bug has been resolved, I will close this issue.