deepspeedai / deepspeedai/DeepSpeedExamples
RuntimeError with BLOOMZ: Expected all tensors to be on the same device, but found at least two devices, cuda:0 and cpu!
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 6.8k
- Forks
- 1.1k
- Avg merge
- 2d 16h
- Merged PRs (30d)
- 1
Description
I'm facing the above error in both stage 1 and stage 2 when using BLOOMZ 3B and 560M.
I tried adding "model.to(device)" and "model.to('cuda')" to main.py but neither worked.
The error only appears when I switch from Llama to BLOOMZ.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start in main.py and reproduce the failure in both stage 1 and stage 2 with BLOOMZ 3B or 560M, comparing the device setup with the working Llama path. Inspect the full traceback and model/device placement to identify the CPU-versus-CUDA mismatch; done means both BLOOMZ sizes run without the RuntimeError.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- machine-learning
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100