mirror of
https://github.com/deepseek-ai/DeepEP.git
synced 2026-11-05 00:47:32 +00:00
[GH-ISSUE #49] Assertion failed: internode_ll.cu:259, condition: num_recv_tokens != 0 #46
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/DeepEP#46
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 @abcdabcd987 on GitHub (Mar 5, 2025).
Original GitHub issue: https://github.com/deepseek-ai/DeepEP/issues/49
Hi, I ran into the following assertion when running the low latency kernel test over 4 nodes.
I tried to build the kernels with and without
DISABLE_AGGRESSIVE_PTX_INSTRS=1. It did not help.GPU is H100. NIC is ConnectX-7 (MT_0000000838). The link layer is Infiniband.
Error is the same even if it's on a single node (
WORLD_SIZE=1).Do you have any clue on where things might be wrong? Thanks!
@abcdabcd987 commented on GitHub (Mar 5, 2025):
test_low_latency.txt
Here's the full log with
NVSHMEM_DEBUG=TRACEif it helps.@LyricZhao commented on GitHub (Mar 6, 2025):
Can you confirm the NVSHMEM patch is correctly installed? This seems something wrong with network adaptive routing (AR). Or you can try switch on/off the AR setting for your network.
cc @sphish
@LyricZhao commented on GitHub (Mar 6, 2025):
Or could you please try modifying
num_recv_tokens = ld_acquire_global(rdma_recv_count + local_expert_idx * num_ranks + src_rank);intold_acquire_sys_global?@GangLuICT commented on GitHub (Mar 13, 2025):
Have you solved this issue? We met the same issue on a SRIOV/VF & iommu=on environment.
But it does not occur when SRIOV is disabled.
@sphish commented on GitHub (Mar 18, 2025):
It seems that one of the ranks might have encountered an exception and didn't reach the GPU kernel execution. We have also disabled SRIOV and haven't experienced similar issues before.