Skip to content

Fix: data on both cuda:0 and cuda:1 when using --torch-device cuda:1#6243

Closed
robinDLFM wants to merge 1 commit into
Unity-Technologies:developfrom
robinDLFM:fix-cuda-device
Closed

Fix: data on both cuda:0 and cuda:1 when using --torch-device cuda:1#6243
robinDLFM wants to merge 1 commit into
Unity-Technologies:developfrom
robinDLFM:fix-cuda-device

Conversation

@robinDLFM

@robinDLFM robinDLFM commented Sep 2, 2025

Copy link
Copy Markdown

Proposed change(s)

Solves:
RuntimeError: Expected all tensors to be on the same device, but found at least two devices, cuda:1 and cuda:0! (when checking argument for argument mat1 in method wrapper_CUDA_addmm)
when using --torch-device cuda:1

  • Bug fix
  • Code refactor

@CLAassistant

CLAassistant commented Sep 2, 2025

Copy link
Copy Markdown

CLA assistant check
All committers have signed the CLA.

@montplaisir

Copy link
Copy Markdown
Contributor

Thank you for your submission!
Your changes were covered by PR #6303.

montplaisir added a commit that referenced this pull request Jun 17, 2026
…raining devices. (#6303)

Port these PRs to current code:

#6297 Add PyTorch XPU as Target Device
#6243 Fix: data on both cuda:0 and cuda:1 when using --torch-device cuda:1
#6225 Release 22/inconsistent device tensor action in trainers [Don't Merge]
#6094 add support for mac m1/m2 chips mps gpu

Co-authored-by: @ekaakurniawan Eka Antonius Kurniawan <eka.a.kurniawan@gmail.com>
Co-authored-by: @robinDLFM Robin De Lissnyder
Co-authored-by: @Jkho80 
Co-authored-by: @zyunlongz Yunlong Zuo <zyunlongz@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants