GPU Memory Mismatch – Troubleshooting Guide

KB 721021 - GPU Memory Mismatch – Troubleshooting Guide

Alert Information

Alert Name: GPU Memory Mismatch

Severity: P3 – Medium Impact

Alert Description:
This alert is generated when the detected GPU memory size on a node does not match the expected configuration.

Alert Summary

The monitoring system has detected that the GPU memory reported by the system differs from the expected GPU memory configuration.


A mismatch may indicate:

  • Incorrect GPU SKU installed

  • GPU firmware issue

  • Hardware fault

  • Improperly seated GPU

  • BIOS configuration mismatch

Impact

  1. GPU workloads may fail or run incorrectly.
  2. Resource allocation in the HPC cluster may become inconsistent.
  3. Indicates possible hardware misconfiguration or GPU malfunction.

Alert Handling Procedure

L1 Engineer Actions

When this alert is triggered, the L1 engineer must perform the following steps:
  1. Review and log the alert summary and node details.

  2. Wait for 20 - 30 Mints if it gets auto resolved. 

  3. Create an internal ticket for tracking the issue.

  4. Verify if the alert is persistent or intermittent.

  5. If the alert continues to appear, escalate the issue to L2 engineering.

  6. After confirmation from L2, update the Issues Master Sheet with the incident details.


L2 Engineer Investigation Steps

L2 engineers must perform deeper diagnostics to validate the GPU configuration.

Step 1 – Check GPU Details

Run the command:
nvidia-smi

Verify:

  • Number of GPUs detected

  • GPU model

  • GPU memory per device


Step 2 – Verify System Memory

Run:
cat /proc/meminfo

This provides system memory information and helps verify node memory configuration.

Step 3 – Check Hardware Memory Details

Run:
sudo dmidecode -t memory

This command displays hardware memory configuration and installed memory modules.

Step 4 – Validate GPU Configuration

Compare the collected information and verify:
  • Installed GPU SKU matches expected configuration

  • No GPU is reporting reduced memory size


Step 5 – Check Firmware and BIOS

Verify the following:
  • GPU firmware version

  • Node BIOS version

  • Hardware configuration consistency with cluster standards

Step 6 – Hardware Troubleshooting

If a mismatch is detected:
  1. Perform a power cycle of the node.
  2. Post customer confirmation, Reseat the GPU according to OEM hardware handling guidelines.
  3. Boot the system and re-run diagnostic commands.

Step 7 – OEM Escalation

If the issue persists after troubleshooting:
  • Escalate the issue to the OEM/vendor support team.
  • Provide:
    • Command outputs
    • Node details
    • GPU information
    • Logs from diagnostics

Command Reference

Verify GPU Visibility on Node:
nvidia-smi
Validate System Memory Configuration:
cat /proc/meminfo

Verify Installed Memory Modules:
sudo dmidecode -t memory

This command verifies:
  1. Installed memory modules
  2. Slot population
  3. Memory capacity
  4. Manufacturer details

Remarks

  1. In some scenarios, GPUs may appear healthy at the OS level, but Kubernetes does not advertise them as allocatable resources.
  2. In such cases, GPU workloads will not be scheduled on the node, even though nvidia-smi shows GPUs as available.
  3. Monitoring systems relying only on nvidia-smi may fail to trigger alerts. Therefore, GPU availability must also be validated from the Kubernetes scheduler perspective.


    • Related Articles

    • KB 744001 - GPU Memory Temperature Critical - Troubleshooting Guide

      Purpose This document provides a standardized approach for handling and troubleshooting the GPU Memory Temperature Critical alert, including L1 and L2 actions, escalation procedures, and resolution criteria. Alert Name GPU Memory Temperature Critical ...

    • KB 265938 - Nvidia-smi Tool Alert - Troubleshooting Guide

      Purpose This document provides a standardized approach for handling and troubleshooting the Nvidia-smi Tool alert, including L1 and L2 actions, escalation guidelines, and resolution criteria. Alert Name Nvidia-smi Tool Alert Description This alert is ...

    • KB 021137 - Network Down IB Alert - Troubleshooting Guide

      Purpose This document provides a standardized approach for handling and troubleshooting the Network Down – IB alert, including L1 and L2 actions, escalation process, and resolution criteria. Alert Name Network Down – IB Alert Description This alert ...

    • KB 715314 - ZFS Pool Capacity Warning Alert - Troubleshooting Guide

      Purpose This document provides a standardized approach for handling and troubleshooting the ZFS Pool Capacity Warning alert, helping L1 and L2 engineers prevent storage exhaustion and maintain system stability. Alert Name ZFS Pool Capacity Warning ...

    • KB 021273 - Network Speed IB Alert - Troubleshooting Guide

      Purpose This document provides a standardized approach for handling and troubleshooting the Network Speed – IB alert, including L1 and L2 actions, escalation process, and resolution guidelines. Alert Name Network Speed IB Alert Description This alert ...

    • Recent Articles

    • KB-630208 | How to use Find and Locate to search for files in Linux

      Purpose To provide Linux administrators and Field Engineers with guidance on using the find and locate utilities to efficiently search for files and directories within a Linux filesystem based on criteria such as name, type, size, timestamps, ...

    • KB-630164 | How to use rsync to Synchronize Files

      Purpose To provide a clear and practical procedure for using the rsync utility to synchronize files and directories between local systems and remote hosts, including push and pull operations, while preserving file attributes and optimizing data ...

    • KB-630107 | How to create a Linux swap file

      Purpose To provide Field Engineers and Linux administrators with a standardized procedure for creating, configuring, and validating a Linux swap file. This procedure helps ensure sufficient virtual memory is available when physical RAM is exhausted ...

    • MSI All-in-One (AIO) PC – Physical Damage Policy for Warranty Claims

      MSI All-in-One (AIO) PC – Physical Damage Policy for Warranty Claims MSI's standard warranty does not cover physical or accidental damage to an All-in-One (AIO) PC. If the damage is determined to be caused by external factors rather than a ...

    • KB 134833 - Troubleshooting NVSM Alert NV-CPU-XX – Unrecoverable CPU Internal Error

      Purpose This document provides a general troubleshooting procedure for the NVIDIA System Management (NVSM) alert NV-CPU-XX, which indicates that a CPU has reported an internal error. The article outlines how to verify whether the alert represents an ...

    • Popular Articles

    • CP Plus Camera and NVR Configuration

      NVR Configuration The CP Plus Pro Series of NVRs have been meticulously designed for providing you with upgraded performance and higher recording quality in your IP video surveillance solution. The robust processor that has been inculcated in this ...

    • KB 775235 - Kerberos Authentication – Overview

      What is Kerberos? Kerberos is a secure authentication method used in our Active Directory (AD) environment (mbuzztech.com). It allows users to: Access multiple systems without re-entering passwords (Single Sign-On – SSO) Log in once Where We Use It ...

    • How to Remove and Reinstall NVIDIA Drivers on Ubuntu

      This article provides step by step guide to completely remove existing NVIDIA drivers and reinstall specific version of the NVIDIA driver on the Ubuntu system Prerequisites Administrative (sudo) access to the Ubuntu system. Internet access to ...

    • KB 692001 - Personal Computers and Servers - Classification and Point of Contact

      We can classify the computers that MBUZZ handles based on their form-factor as below: Tower Workstations, Desktops, Gaming PCs and SFF (Small form factor) PCs fall under this category. These are computers people would use on a desk and rarely move. ...

    • KB 298031 - M.2 SSD Tier List

      The sequential read and write speeds, which are usually the most advertised number, are not a proper benchmark of real-world performance or the quality of an SSD. This article categorizes and tiers SSDs based on factors like the type of NAND flash, ...