Compute
Elastic Cloud Server
Huawei Cloud Flexus
Bare Metal Server
Auto Scaling
Image Management Service
Dedicated Host
FunctionGraph
Cloud Phone Host
Huawei Cloud EulerOS
Networking
Virtual Private Cloud
Elastic IP
Elastic Load Balance
NAT Gateway
Direct Connect
Virtual Private Network
VPC Endpoint
Cloud Connect
Enterprise Router
Enterprise Switch
Global Accelerator
Management & Governance
Cloud Eye
Identity and Access Management
Cloud Trace Service
Resource Formation Service
Tag Management Service
Log Tank Service
Config
OneAccess
Resource Access Manager
Simple Message Notification
Application Performance Management
Application Operations Management
Organizations
Optimization Advisor
IAM Identity Center
Cloud Operations Center
Resource Governance Center
Migration
Server Migration Service
Object Storage Migration Service
Cloud Data Migration
Migration Center
Cloud Ecosystem
KooGallery
Partner Center
User Support
My Account
Billing Center
Cost Center
Resource Center
Enterprise Management
Service Tickets
HUAWEI CLOUD (International) FAQs
ICP Filing
Support Plans
My Credentials
Customer Operation Capabilities
Partner Support Plans
Professional Services
Analytics
MapReduce Service
Data Lake Insight
CloudTable Service
Cloud Search Service
Data Lake Visualization
Data Ingestion Service
GaussDB(DWS)
DataArts Studio
Data Lake Factory
DataArts Lake Formation
IoT
IoT Device Access
Others
Product Pricing Details
System Permissions
Console Quick Start
Common FAQs
Instructions for Associating with a HUAWEI CLOUD Partner
Message Center
Security & Compliance
Security Technologies and Applications
Web Application Firewall
Host Security Service
Cloud Firewall
SecMaster
Anti-DDoS Service
Data Encryption Workshop
Database Security Service
Cloud Bastion Host
Data Security Center
Cloud Certificate Manager
Edge Security
Situation Awareness
Managed Threat Detection
Blockchain
Blockchain Service
Web3 Node Engine Service
Media Services
Media Processing Center
Video On Demand
Live
SparkRTC
MetaStudio
Storage
Object Storage Service
Elastic Volume Service
Cloud Backup and Recovery
Storage Disaster Recovery Service
Scalable File Service Turbo
Scalable File Service
Volume Backup Service
Cloud Server Backup Service
Data Express Service
Dedicated Distributed Storage Service
Containers
Cloud Container Engine
SoftWare Repository for Container
Application Service Mesh
Ubiquitous Cloud Native Service
Cloud Container Instance
Databases
Relational Database Service
Document Database Service
Data Admin Service
Data Replication Service
GeminiDB
GaussDB
Distributed Database Middleware
Database and Application Migration UGO
TaurusDB
Middleware
Distributed Cache Service
API Gateway
Distributed Message Service for Kafka
Distributed Message Service for RabbitMQ
Distributed Message Service for RocketMQ
Cloud Service Engine
Multi-Site High Availability Service
EventGrid
Dedicated Cloud
Dedicated Computing Cluster
Business Applications
Workspace
ROMA Connect
Message & SMS
Domain Name Service
Edge Data Center Management
Meeting
AI
Face Recognition Service
Graph Engine Service
Content Moderation
Image Recognition
Optical Character Recognition
ModelArts
ImageSearch
Conversational Bot Service
Speech Interaction Service
Huawei HiLens
Video Intelligent Analysis Service
Developer Tools
SDK Developer Guide
API Request Signing Guide
Terraform
Koo Command Line Interface
Content Delivery & Edge Computing
Content Delivery Network
Intelligent EdgeFabric
CloudPond
Intelligent EdgeCloud
Solutions
SAP Cloud
High Performance Computing
Developer Services
ServiceStage
CodeArts
CodeArts PerfTest
CodeArts Req
CodeArts Pipeline
CodeArts Build
CodeArts Deploy
CodeArts Artifact
CodeArts TestPlan
CodeArts Check
CodeArts Repo
Cloud Application Engine
MacroVerse aPaaS
KooMessage
KooPhone
KooDrive

GPU Fault Handling

Updated on 2025-01-07 GMT+08:00

Prerequisites

Cloud Native Log Collection has been installed in the cluster so that GPU events can be synchronously reported to AOM.

GPU Isolation Event

When a GPU malfunctions, the system automatically isolates the faulty GPU. For details, see Table 1.

Table 1 GPU isolation event

Event Cause

Error Details

Description

Result

GPUMemoryError

Device=%s, UUID=%s, SN=%s has failed remapped rows; The device will go unhealthy.

Failed to obtain the number of remapped rows in NVML.

The faulty GPU device is isolated.

GPUMemoryError

Device=%s, UUID=%s, SN=%s has more than 60 retired pages caused by both multiple single bit ecc error and double bit ecc error, DBE error number: %d, SBE error number: %d; The device will go unhealthy.

The total number of DBE errors and SBE errors of the GPU device is greater than 60.

The faulty GPU device is isolated.

GPUMemoryError

Device=%s, UUID=%s, SN=%s has more than 4 SRAM uncorrectable ecc errors count; The device will go unhealthy.

The number of uncorrectable ECC errors of the GPU device is greater than 4.

The faulty GPU device is isolated.

GPUXidError

Failed to determine gpu device uuid for Xid=%d; Marking all devices as unhealthy.

Failed to obtain the UUID using NVML.

The GPU device of the faulty GPU node is isolated.

GPUXidError

Xid=%d on Device=%s, UUID=%s, SN=%s, the device will go unhealthy.

GPU Xid error occurred, and the affected Xids are 74 and 79.

The faulty GPU device is isolated.

GPUHealthWarning

Device=%s, UUID=%s, SN=%s failed to get fan state.

The fan on the GPU device is not running properly.

The affected GPU device is not isolated.

GPUHealthWarning

Device=%s, UUID=%s, SN=%s failed to get power state.

Failed to obtain the power of the GPU device.

The affected GPU device is not isolated.

Fault Locating

  • Failed to obtain the number of remapped rows in NVML.

    The GPU driver or GPU device malfunctions. Contact customer service based on the type of the node (ECS or BMS) where the GPU device resides.

  • The total number of DBE errors and SBE errors of the GPU device is high.

    The GPU driver or GPU device malfunctions. Contact customer service based on the type of the node (ECS or BMS) where the GPU device resides.

  • There are uncorrectable ECC errors of the GPU device.
    1. Log in to the node where the GPU isolation event occurred.
    2. Go to the /usr/local/nvidia/bin directory and run the nvidia-smi -q command.

      If the nvidia-smi command is unavailable or fails to be executed, the failure may be caused by the lack of GPU driver. Reinstall the GPU driver and try again.

    3. Check the ECC ERROR in the command output.
      • Correctable Error: Such an error will not interrupt services or trigger GPU isolation.
      • Uncorrectable Error: Such an error will interrupt services and trigger GPU isolation.
    4. If there are uncorrectable errors, perform the following operations to rectify the fault:
      1. Configure taints on the target node to evict the existing service load from the node.
      2. Restart the target node.
      3. If the fault persists, collect the output of the nvidia-smi -q command and contact customer service based on the type of the node (ECS or BMS) where the GPU device resides.
  • Failed to obtain the UUID using NVML.
    1. Log in to the node where the GPU isolation event occurred.
    2. Access /usr/local/nvidia/bin.
    3. Run the nvidia-smi command and check the device ID in the command output, for example, 00:0D.0.

      If the nvidia-smi command is unavailable or fails to be executed, the failure may be caused by the lack of GPU driver. Reinstall the GPU driver and try again.

    4. Run the lspci | grep NVIDIA command and check the device ID in the command output.
    5. Compare the two results. If they do not match, contact customer service based on the type of the node (ECS or BMS) where the GPU device is located.
  • The Xid of the GPU device is incorrect.
    1. Log in to the node where the GPU isolation event occurred.
    2. Run the dmesg -T | grep -i NVRM command and check the command output.
    3. If information in the "Xid(PCI:0000:00:0x): xx" format is displayed, collect the error code and identify the cause based on NVIDIA Xid Errors. Collect the error information and detailed cause and contact customer service based on the type of the node (ECS or BMS) where the GPU device resides.
  • The available memory of xGPU devices is far less than the physical GPU memory.
    1. Log in to the xGPU node.
    2. Run the /usr/local/nvidia/bin/nvidia-smi command to obtain the physical GPU memory of the target GPU and record its serial number.
    3. Run the cat /proc/xgpu/{GPU serial number}/meminfo command to obtain the available xGPU memory. Replace {GPU serial number} with the one obtained in preceding step.
    4. Compare the obtained GPU memory.
      NOTE:

      The driver of the GPU vendor occupies a certain amount of physical GPU memory, which is about 300 MiB. This is normal. For example, if Tesla T4 GPUs run with NVIDIA driver 510.47.03, the driver occupies the GPU memory of 280 MiB by default. The value varies depending on the driver version. For example, the 535 series driver occupies more memory than the 470 series driver.

      If the available xGPU memory is far less than the physical GPU memory, some containers that are not provisioned using GPU virtualization occupy the GPU memory.

    5. In this case, clear the GPU load on the target node through the CCE console or by using kubectl.
    6. Run the rmmod xgpu_km command to delete GPU virtualization.
    7. Delete the nvidia-gpu-device-plugin pods on the target node through the CCE console or by using kubectl.
    8. After the nvidia-gpu-device-plugin pods are rebuilt, perform steps 2 and 3 again to verify the result.

We use cookies to improve our site and your experience. By continuing to browse our site you accept our cookie policy. Find out more

Feedback

Feedback

Feedback

0/500

Selected Content

Submit selected content with the feedback