Skip to content

[DO NOT MERGE] docs(amdsmi): update the changelog (check M) #14799

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
adam360x wants to merge 1 commit into from
Closed

[DO NOT MERGE] docs(amdsmi): update the changelog (check M) #14799

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions projects/amdsmi/CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -171,8 +171,8 @@ Full documentation for amd_smi_lib is available at [https://rocm.docs.amd.com/pr

### Resolved Issues

- **Fixed GPU metrics returning no data on integrated GPUs**.
- `amdsmi_get_gpu_metrics_info()` and `amdsmi_get_gpu_activity()` failed on APUs such as gfx1103, leaving PLX temperature, GPU utilization and `amd-smi metric` empty. Those devices now report the values they provide with the rest marked N/A, and any GPU without a PLX sensor now reports N/A there instead of a placeholder reading.
- **Fixed GPU metrics returning no data on integrated GPUs (ROCM-29548)**.
- `lookup_header_flag_version()` in `rocm_smi_gpu_metrics.cc` now routes APU gpu_metrics tables to the `kApuMetricV24` reader, so `amdsmi_get_gpu_metrics_info()` and `amdsmi_get_gpu_activity()` no longer fail on APUs such as gfx1103.

- **Fixed `amd-smi` printing a Python traceback when an unknown NIC or switch is selected**.
- `amd-smi static --nic 999` and `--switch 999` failed while building the "device not found" error, so the command exited `1` with a traceback and no readable message. `--json` and `--csv` produced no parseable output.
Expand Down
Loading