원클릭으로
amdsmi-output-verification
A checklist for verifying whether AMD SMI is reporting GPU information correctly.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
메뉴
A checklist for verifying whether AMD SMI is reporting GPU information correctly.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Check and generate changelog entries for amd-smi. Use when: reviewing PRs for changelog updates, generating release notes, checking CHANGELOG.md compliance.
Use when writing or restructuring git commits or opening/updating a pull request for amd-smi — composing commit titles, commit message bodies, PR titles, or PR descriptions. Defines the Conventional Commits `type(amdsmi):` title convention enforced by the Systems PR Bot, the rocm-systems PR template sections, the unit-test and JIRA/ISSUE-reference gates, brevity caps, and the rule that JIRA tickets appear only in the PR JIRA ID section, never in code comments or commit bodies.
Use when finishing an amd-smi development branch — consolidating commits into logical groups with clean messages AND deciding how to integrate the work (merge to develop, push and open PR, keep as-is, or discard). Covers commit restructuring plus the merge/PR/cleanup workflow.
Use when an approved spec exists and you need a bite-sized, file-level implementation plan before any code is written. Produces a plan ready for executing-plans or subagent dispatch.
Build and install RDC from source. Use when: building locally, installing before tests, pre-review build verification, build + install + verify. Requires GRPC_ROOT to be set.
Use when writing, planning, or improving unit tests for low-level transport or systems code — especially when reasoning about branch coverage, test gaps, identifying which uncovered paths are worth pursuing, or deciding when a feature's test suite is ready to merge.
| name | amdsmi-output-verification |
| description | A checklist for verifying whether AMD SMI is reporting GPU information correctly. |
Use this checklist whenever AMD SMI appears to report incorrect GPU information. The goal is to distinguish a real AMD SMI defect from a driver, firmware, environment, documentation, or expectation mismatch.
When running a test, include the following metadata to help with triage and debugging:
Capture raw output, without editing values.
amd-smi version
amd-smi list
amd-smi static
amd-smi metric
amd-smi monitor
rocminfo
rocm-smi
lspci -nn
lspci -vv
dmesg
Also capture relevant sysfs values:
find /sys/class/drm -maxdepth 4 -type f
For each tested GPU, inspect the matching card path under:
/sys/class/drm/card*/device
Useful files often include:
vendordevicesubsystem_vendorsubsystem_devicerevisionproduct_nameproduct_numberserial_numbermem_info_vram_totalmem_info_vram_usedgpu_busy_percentpp_dpm_sclkpp_dpm_mclkpp_power_profile_modeAvailability varies by GPU, driver, kernel, and permission level.
| Field | AMD SMI value | Baseline value | Baseline source | Result | Notes |
|---|---|---|---|---|---|
| GPU name | |||||
| ASIC name | |||||
| Vendor ID | |||||
| Device ID | |||||
| Subsystem ID | |||||
| Revision ID | |||||
| PCI BDF | |||||
| VRAM total | |||||
| Memory type | |||||
| VBIOS version | |||||
| Firmware versions | |||||
| Driver version | |||||
| ROCm version | |||||
| Temperature | |||||
| Power | |||||
| Clocks | |||||
| Utilization | |||||
| ECC/RAS support | |||||
| Process reporting |