Skip to content

[main] Enforce single GPU per trainer - #84

Open
Tobiaspk wants to merge 3 commits into
mainfrom
bugfix/avoid_multi_gpu
Open

[main] Enforce single GPU per trainer#84
Tobiaspk wants to merge 3 commits into
mainfrom
bugfix/avoid_multi_gpu

Conversation

@Tobiaspk

@Tobiaspk Tobiaspk commented Aug 31, 2026

Copy link
Copy Markdown
Collaborator

Closes #12, where segger tries to use all assigned GPUs. Thanks to @eastagiletracker for finding this fix (closing #82 as out of scope).

Tested this on a SLURM cluster before/after the fix and confirmed this fixes the issue.

@Tobiaspk Tobiaspk changed the title Pin Trainer to a single device [main] Pin Trainer to a single device Aug 31, 2026
@Tobiaspk Tobiaspk changed the title [main] Pin Trainer to a single device [main] Enforce single GPU per trainer Aug 31, 2026
@Tobiaspk
Tobiaspk changed the base branch from integration/peerlab to main September 2, 2026 14:13
@Tobiaspk
Tobiaspk force-pushed the bugfix/avoid_multi_gpu branch from 3202db0 to fc1c3f6 Compare September 3, 2026 14:52
Tobiaspk and others added 2 commits September 3, 2026 10:53
Segger's Trainer instances defaulted to all assigned GPUs, causing failures on multi-GPU SLURM allocations. Set devices=1 explicitly in segment.py and debug/prediction.py.
Co-authored-by: East Agile Tracker <tracker@eastagile.com>
@Tobiaspk
Tobiaspk force-pushed the bugfix/avoid_multi_gpu branch from fc1c3f6 to 98f6064 Compare September 3, 2026 14:59
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.

CUDA illegal memory access when running Segger on multi-GPU machine

1 participant