deepspeedai / deepspeedai/DeepSpeed

[BUG] - Multiple 5090s failing on deepspeed.initialize()

Open
#7,261 26 comments 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug training
Dominant language
Python
Stars
43.1k
Forks
5k
Avg merge
4d 15h
Merged PRs (30d)
112

Description

Describe the bug

The developer of the training code Diffusion-pipe helped me debug this, the issue on that repository has all the relevant information that I have now. His summary:

So plain PyTorch GPU communication ops work. But deepspeed.initialize() is always failing when it does its version of cross-GPU communication. Myself and other users have this working, but it fails specifically with multiple 5090s, and you are probably the only person who has tried that setup.

I would raise an issue with Deepspeed. I don't think I've done anything wrong in the application code, and it is likely an internal Deepspeed problem. Without being able to reproduce the error myself, there's not much more I can do.

Full issue: https://github.com/tdrussell/diffusion-pipe/issues/235#issuecomment-2831270369

To Reproduce
Steps to reproduce the behavior:

Run deepspeed.initialize() with 2 x 5090 GPUs

System info (please complete the following information):

  • OS: ubuntu 24.04
  • GPU count and types: 1 machine with 2 x 5090s
  • Python version: 3.12
  • Any other relevant info about your setup: All latest Nvidia drivers, pytorch nightly etc.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the deepspeed.initialize() entry point and review the linked Diffusion-pipe issue for the missing failure details. Reproduce the problem on Ubuntu 24.04 with Python 3.12 and two 5090 GPUs, comparing it with the reported working plain PyTorch communication; done means initialization completes successfully.

Written by the indexing model from the issue text.

Assessment

Tech stack
python, pytorch
Domain
distributed-systems, machine-learning
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.