Skip to content

[B200+][NVLink5+] reset GPUs after FABRIC_MODE=1 is set - #909

Merged
tariq1890 merged 1 commit into
mainfrom
fm-nvlink5-gpu-reset
Aug 10, 2026
Merged

[B200+][NVLink5+] reset GPUs after FABRIC_MODE=1 is set#909
tariq1890 merged 1 commit into
mainfrom
fm-nvlink5-gpu-reset

Conversation

@tariq1890

@tariq1890 tariq1890 commented Aug 6, 2026

Copy link
Copy Markdown
Contributor

NVLinked systems that use NVLink generation 5 or greater require the GPUs to be reset after Fabric Manager is started up with FABRIC_MODE=1 set in its config.

@tariq1890
tariq1890 force-pushed the fm-nvlink5-gpu-reset branch from 0453b86 to 6f936fb Compare August 6, 2026 02:49
@tariq1890
tariq1890 requested a review from shivamerla August 6, 2026 03:03
Comment thread rhel10/nvidia-driver Outdated
# We reset the GPU devices after Fabric Manager startup to clear stale FM
# partition data that may have carried over previous driver container runs
echo "Resetting GPUs to clear stale Fabric Partition states..."
nvidia-smi -r

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Instead of a blanket reset, I wonder if we need to check if the fabric state is In Progress first on all GPUs before attempting to reset:

nvidia-smi --query-gpu "fabric.state" --format "csv,noheader"

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Isn't it possible that the Completed state could be stale as well?

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

My statement was incorrect here. When switch from FABRIC_MODE 0 to 1, all the GPUs will go to In Progress fabric state until there's a partition activation that uses those GPUs. So its not valid to reset the GPU by checking for the fabric state.

Your current implementation of doing the reset if we're trying to start in FABRIC_MODE=1 makes sense.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for confirming! I will resolve this comment.

@tariq1890
tariq1890 force-pushed the fm-nvlink5-gpu-reset branch from 6f936fb to c9d2e19 Compare August 7, 2026 02:05
@tariq1890 tariq1890 changed the title [B200+][NVLink5+] reset GPUs after FM service startup [B200+][NVLink5+] reset GPUs after FABRIC_MODE=1 is set Aug 7, 2026
@tariq1890
tariq1890 marked this pull request as ready for review August 7, 2026 02:06
@tariq1890 tariq1890 self-assigned this Aug 7, 2026
Signed-off-by: Tariq Ibrahim <tibrahim@nvidia.com>
@tariq1890
tariq1890 force-pushed the fm-nvlink5-gpu-reset branch from c9d2e19 to 88a0ec2 Compare August 10, 2026 19:01
@tariq1890
tariq1890 merged commit 7b70c79 into main Aug 10, 2026
53 of 116 checks passed
@tariq1890
tariq1890 deleted the fm-nvlink5-gpu-reset branch August 10, 2026 20:00
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