mirror of
https://github.com/deepseek-ai/DeepEP.git
synced 2026-11-05 00:47:32 +00:00
[GH-ISSUE #17] Test test_low_latency.py failed on H20 ROCE #17
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#17
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 @HanHan009527 on GitHub (Feb 25, 2025).
Original GitHub issue: https://github.com/deepseek-ai/DeepEP/issues/17
Issue Description
run test_low_latency.py failed.
test_intranode.py and 2 H20 node test_internode.py can run nomally.
Not familiar with nvshmem, thanks a lot for your help.
Actual Result
Environment
mlx5_0 is a ocp/vpc nic.
Additional Information
Please provide any other relevant information, such as error logs, screenshots, etc.
@zdddddda commented on GitHub (Feb 25, 2025):
I have the same issue with HanHan009527. How can this problem be solved?
@haswelliris commented on GitHub (Feb 25, 2025):
The error logs indicate an NVSHMEM-related issue during the initialization of QPs (Queue Pairs). It is recommended to contact NVIDIA technical support to provide necessary assistance for RoCE devices, particularly for enabling IBGDA functionality on BlueField-3 (BF3) adapters.
If you're experiencing the same issue, please share your feedback with the NVSHMEM development team to help investigate and resolve the problem.
@HanHan009527 commented on GitHub (Feb 26, 2025):
thanks, Let me try NVSHMEM examples on BlueField-3, and contact NVIDIA technical support.
@WJTian commented on GitHub (Feb 26, 2025):
I ran into this problem while doing nvshmem perftest and it was resolved by upgrading to nvshmem_src_3.2.5-1.
@sphish commented on GitHub (Feb 26, 2025):
@WJTian Thank you for your feedback! At the time of our release, the source code for NVSHMEM v3.2.5 was not yet available. I will test it soon!
@HanHan009527 commented on GitHub (Feb 26, 2025):
I tried this solution and luckily the patch file can be apply directly, it really works. LOL thanks a lot. @WJTian @sphish
@kefins commented on GitHub (Feb 26, 2025):
What is the matter? I got errors when applying the patch to nvshmem_src_3.2.5-1:
@kefins commented on GitHub (Feb 26, 2025):
Besides the patch problem. I got antother other while compiling DeepEP with nvshmem_src_3.2.5-1.
@Qizhi697 commented on GitHub (Feb 26, 2025):
I have the same problem.
@kefins commented on GitHub (Feb 26, 2025):
I think it was caused by lacking the patch.
@HanHan009527 commented on GitHub (Feb 27, 2025):
yes, if you use
git apply patchfile, you will get this error. I use PyCharm to apply the patch file. not sure what is the differents of this tow tools.@Ben286 commented on GitHub (Feb 27, 2025):
Is there a solution for 3.1.7 ?
@Dixeran commented on GitHub (Mar 7, 2025):
Hello, have you attempted to execute the low-latency test within H20? I was able to patch into nvshmem 3.2.5, which indeed resolved the QPs issue. However, I still encountered other problems during the execution of the low-latency tests.
@sphish commented on GitHub (Mar 9, 2025):
We haven't tested on the h20 machine, but theoretically it should work. What issues are you encountering? @Dixeran
@Dixeran commented on GitHub (Mar 17, 2025):
Seems like some hardware resources retriction compare to H800?
@sphish commented on GitHub (Mar 17, 2025):
Yes, the H20 has fewer SMs compared to the H800. Please refer to https://github.com/deepseek-ai/DeepEP/issues/15#issuecomment-2682343603.
@xing0821 commented on GitHub (Apr 20, 2025):
did you already patched? This problem appear when i try to patch at second time
@sphish commented on GitHub (Apr 21, 2025):
@xing0821 Have you pulled the newest code? The latest patch should have solved this problem.