** Description changed:
## SRU ##
[ Impact ]
- * amdsmi 7.2.4 (libamd-smi26) ships four CLI/library bug fixes over the
- 7.2.0 release already in resolute:
+ * amdsmi 7.2.4 (libamd-smi26) ships four CLI/library bug fixes over the
+ 7.2.0 release already in resolute:
- 1. [SWDEV-560235] gpu_board and base_board temperature monitoring was
- implemented inline in amdsmi_commands.py, duplicating ~80 lines of
- identical logic in both the `metric` and `monitor` code paths. The
- refactored helpers get_gpu_board_temperatures /
get_base_board_temperatures
- are extracted to amdsmi_helpers.py and two new `amd-smi monitor` flags
- are exposed: `--base-board-temps` (-b) and `--gpu-board-temps` (-o).
- Systems without the relevant sensors (e.g. MI100, consumer GPUs) see
- all values reported as N/A; no behaviour change for existing
invocations.
+ 1. [SWDEV-560235] gpu_board and base_board temperature monitoring was
+ implemented inline in amdsmi_commands.py, duplicating ~80 lines of
+ identical logic in both the `metric` and `monitor` code paths. The
+ refactored helpers get_gpu_board_temperatures /
get_base_board_temperatures
+ are extracted to amdsmi_helpers.py and two new `amd-smi monitor` flags
+ are exposed: `--base-board-temps` (-b) and `--gpu-board-temps` (-o).
+ Systems without the relevant sensors (e.g. MI100, consumer GPUs) see
+ all values reported as N/A; no behaviour change for existing
invocations.
- 2. [SWDEV-566465] `amd-smi reset --pptpowerusage` produced malformed JSON
- when run across multiple GPUs. In the multi-device path print_output()
- was called before store_multiple_device_output(), so each GPU's result
- was flushed and the accumulation buffer was cleared prematurely. The
- fix moves the early-return guard after store_multiple_device_output().
- Single-GPU usage and non-JSON output are unaffected.
+ 2. [SWDEV-566465] `amd-smi reset --pptpowerusage` produced malformed JSON
+ when run across multiple GPUs. In the multi-device path print_output()
+ was called before store_multiple_device_output(), so each GPU's result
+ was flushed and the accumulation buffer was cleared prematurely. The
+ fix moves the early-return guard after store_multiple_device_output().
+ Single-GPU usage and non-JSON output are unaffected.
- 3. Fix for CPER AFID list printing garbage values on invalid CPER files —
- When amdsmi_cper_decode encountered an unrecognised section type it fell
- through to the else branch (logging an error) but then unconditionally
- called afids.emplace_back() on the uninitialised afid variable. The fix
- initialises afid = -1 before the if/else chain and only appends when
- afid >= 0. Symptom: `amd-smi ras --cper` could print spurious integer
- values in the AFID column when fed a CPER file with unknown section
types.
+ 3. Fix for CPER AFID list printing garbage values on invalid CPER files —
+ When amdsmi_cper_decode encountered an unrecognised section type it fell
+ through to the else branch (logging an error) but then unconditionally
+ called afids.emplace_back() on the uninitialised afid variable. The fix
+ initialises afid = -1 before the if/else chain and only appends when
+ afid >= 0. Symptom: `amd-smi ras --cper` could print spurious integer
+ values in the AFID column when fed a CPER file with unknown section
types.
- 4. [SWDEV-560828] `amd-smi ras --cper --follow --file <path>` sent all
- output to stdout instead of to the specified file. The CPER display
- helpers (display_cper_files_generated, _print_header, dump_cper_entries)
- were unconditionally calling print(); they now check the logger's
- destination and write to the file when one is set.
+ 4. [SWDEV-560828] `amd-smi ras --cper --follow --file <path>` sent all
+ output to stdout instead of to the specified file. The CPER display
+ helpers (display_cper_files_generated, _print_header, dump_cper_entries)
+ were unconditionally calling print(); they now check the logger's
+ destination and write to the file when one is set.
- On top of the above, the 7.2.4-1 packaging carries the following
- packaging-only changes, with no runtime behaviour impact on the binary
- packages shipped today:
+ On top of the above, the 7.2.4-1 packaging carries the following
+ packaging-only changes, with no runtime behaviour impact on the binary
+ packages shipped today:
- - d/patches: add DEP-3 Forwarded: not-needed to
- 0004-modify-shared-lib-loading-path.
- - d/patches: drop malformed "yes, <url>" prefix from Forwarded in
0005/0006.
- - d/libamd-smi26-tests.install: fix stale libamd-smi25-tests path (the
- libamd-smi26-tests binary is not currently built, so this has no effect
- on the packages actually shipped).
- - d/upstream/metadata: add Repository field.
- - d{control,*lintian-overrides}: remove XBSC-Comment field and use plain
- comment instead.
- - debian/watch and debian/copyright now track amdsmi from the
- ROCm/rocm-systems monorepo release assets instead of the standalone
- upstream repository.
+ - d/patches: add DEP-3 Forwarded: not-needed to
+ 0004-modify-shared-lib-loading-path.
+ - d/patches: drop malformed "yes, <url>" prefix from Forwarded in
0005/0006.
+ - d/libamd-smi26-tests.install: fix stale libamd-smi25-tests path (the
+ libamd-smi26-tests binary is not currently built, so this has no effect
+ on the packages actually shipped).
+ - d/upstream/metadata: add Repository field.
+ - d{control,*lintian-overrides}: remove XBSC-Comment field and use plain
+ comment instead.
+ - debian/watch and debian/copyright now track amdsmi from the
+ ROCm/rocm-systems monorepo release assets instead of the standalone
+ upstream repository.
[ Test Plan ]
- 1. Build:
- - dpkg-buildpackage succeeds, both source-only (-S) and binary (-b),
- built locally in an igor-resolute LXC container and pushed through a
- full autopkgtest build cycle (see item 3).
- - dpkg --compare-versions 7.2.4-1~26.04.1 gt 7.2.0-3 confirms the new
- version is greater.
- - abigail (abipkgdiff) comparing the newly built libamd-smi26 and
- libgoamdsmi-shim64-1 against the binaries currently published in
- resolute (7.2.0-3): 0 functions and 0 variables removed, changed, or
- added in either library. The only differences reported are internal
- libstdc++ template-instantiation symbols not referenced by debug info
- (std::regex/std::vector internals), attributable to a compiler/
- libstdc++ version difference between build environments, not a change
- to the libraries' public ABI.
- - lintian run on both the source and binary packages: no errors. Only
- pre-existing warning/pedantic/experimental-level tags: groff-message
- on the amd-smi man page, two spelling-error-in-binary hits for
- upstream string typos baked into libamd_smi.so.26 ("retreive",
- "wTH"), debian-revision-not-well-formed (expected, from the ~ppa/
- ~26.04 SRU version suffix), and newer-standards-version.
+ 1. Build:
+ - dpkg-buildpackage succeeds, both source-only (-S) and binary (-b),
+ built locally in an igor-resolute LXC container and pushed through a
+ full autopkgtest build cycle (see item 3).
+ - dpkg --compare-versions 7.2.4-1~26.04.1 gt 7.2.0-3 confirms the new
+ version is greater.
+ - abigail (abipkgdiff) comparing the newly built libamd-smi26 and
+ libgoamdsmi-shim64-1 against the binaries currently published in
+ resolute (7.2.0-3). 0 functions and 0 variables removed, changed, or
+ added in either library. Output:
- 2. Installability:
- - apt install amd-smi libamd-smi26 libamd-smi-dev libgoamdsmi-shim64-1
- libgoamdsmi-shim64-dev — confirmed installable as part of the
- autopkgtest run below.
- - Confirm reverse dependencies remain installable without rebuild.
+ $ abipkgdiff --d1 <old> --d2 <new> libamd-smi26_7.2.0-3_amd64.deb
+ libamd-smi26_7.2.4-1~26.04.1_amd64.deb
- 3. Autopkgtest:
- - Ran the autopkgtest suite (run-amdsmi) on real AMD Strix Halo GPU
- hardware (gfx1151) in an igor-resolute LXC container (null backend).
- All tests pass. Output:
+ ================ changes of 'libamd_smi.so.26.2.1'===============
+ Functions changes summary: 0 Removed, 0 Changed, 0 Added function
+ Variables changes summary: 0 Removed, 0 Changed, 0 Added variable
+ Function symbols changes summary: 6 Removed, 6 Added function symbols
not referenced by debug info
+ Variable symbols changes summary: 0 Removed, 0 Added variable symbol
not referenced by debug info
- autopkgtest [12:42:47]: starting date and time: 2026-07-08 12:42:47+0000
- autopkgtest [12:42:47]: version 5.55
- autopkgtest [12:42:47]: host igor-resolute; command line:
/usr/bin/autopkgtest 'amdsmi_7.2.4-1~26.04.1.dsc' -- null
- autopkgtest [12:42:47]: testbed release detected to be: resolute
- autopkgtest [12:43:15]: test run-amdsmi: /bin/bash
debian/tests/amdsmi.sh
- autopkgtest [12:43:16]: test run-amdsmi: -----------------------]
- run-amdsmi PASS
- autopkgtest [12:43:17]: test run-amdsmi: - - - - - - - - - - results -
- - - - - - - - -
- autopkgtest [12:43:17]: @@@@@@@@@@@@@@@@@@@@ summary
- run-amdsmi PASS
+ 6 Removed function symbols not referenced by debug info:
+
+ [D] _ZNSt6vectorIiSaIiEE17_M_realloc_appendIJiEEEvDpOT_
+ [D]
_ZNSt8__detail9_ExecutorIN9__gnu_cxx17__normal_iteratorIPKcNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEEESaINS5_9sub_matchISB_EEENS5_12regex_traitsIcEELb0EE17_M_handle_backrefENSH_11_Match_modeEl
+ [D]
_ZNSt8__detail9_ExecutorIPKcSaINSt7__cxx119sub_matchIS2_EEENS3_12regex_traitsIcEELb0EE17_M_handle_backrefENS9_11_Match_modeEl
+ [D]
_ZZNKSt8__detail15_BracketMatcherINSt7__cxx1112regex_traitsIcEELb0ELb1EE8_M_applyEcSt17integral_constantIbLb0EEENKUlvE_clEv
+ [D]
_ZZNKSt8__detail15_BracketMatcherINSt7__cxx1112regex_traitsIcEELb1ELb0EE8_M_applyEcSt17integral_constantIbLb0EEENKUlvE_clEv
+ [D]
_ZZNKSt8__detail15_BracketMatcherINSt7__cxx1112regex_traitsIcEELb1ELb1EE8_M_applyEcSt17integral_constantIbLb0EEENKUlvE_clEv
+
+ 6 Added function symbols not referenced by debug info:
+
+ [A]
_ZNSt8__detail9_ExecutorIN9__gnu_cxx17__normal_iteratorIPKcNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEEESaINS5_9sub_matchISB_EEENS5_12regex_traitsIcEELb1EE17_M_handle_backrefENSH_11_Match_modeEl
+ [A]
_ZNSt8__detail9_ExecutorIPKcSaINSt7__cxx119sub_matchIS2_EEENS3_12regex_traitsIcEELb1EE17_M_handle_backrefENS9_11_Match_modeEl
+ [A]
_ZZNKSt8__detail15_BracketMatcherINSt7__cxx1112regex_traitsIcEELb0ELb0EE8_M_applyEcENKUlvE_clEv
+ [A]
_ZZNKSt8__detail15_BracketMatcherINSt7__cxx1112regex_traitsIcEELb0ELb1EE8_M_applyEcENKUlvE_clEv
+ [A]
_ZZNKSt8__detail15_BracketMatcherINSt7__cxx1112regex_traitsIcEELb1ELb0EE8_M_applyEcENKUlvE_clEv
+ [A]
_ZZNKSt8__detail15_BracketMatcherINSt7__cxx1112regex_traitsIcEELb1ELb1EE8_M_applyEcENKUlvE_clEv
+
+ ================ end of changes of
+ 'libamd_smi.so.26.2.1'===============
+
+ (all 12 are libstdc++ std::regex/std::vector template-instantiation
+ symbols not referenced by debug info — a compiler/libstdc++ version
+ artifact between build environments, not a change to the library's
+ public ABI; 0 Functions/Variables changed confirms no public ABI break)
+
+ $ abipkgdiff --d1 <old> --d2 <new>
libgoamdsmi-shim64-1_7.2.0-3_amd64.deb
libgoamdsmi-shim64-1_7.2.4-1~26.04.1_amd64.deb
+ (no output — exit code 0, no ABI changes at all)
+ - lintian run on both the source and binary packages: no errors. Only
+ pre-existing warning/pedantic/experimental-level tags: groff-message
+ on the amd-smi man page, two spelling-error-in-binary hits for
+ upstream string typos baked into libamd_smi.so.26 ("retreive",
+ "wTH"), debian-revision-not-well-formed (expected, from the ~ppa/
+ ~26.04 SRU version suffix), and newer-standards-version.
+
+ 2. Installability:
+ - apt install amd-smi libamd-smi26 libamd-smi-dev libgoamdsmi-shim64-1
+ libgoamdsmi-shim64-dev — confirmed installable as part of the
+ autopkgtest run below.
+ - Confirm reverse dependencies remain installable without rebuild.
+
+ 3. Autopkgtest:
+ - Ran the autopkgtest suite (run-amdsmi) on real AMD Strix Halo GPU
+ hardware (gfx1151) in an igor-resolute LXC container (null backend).
+ All tests pass. Output:
+
+ autopkgtest [12:42:47]: starting date and time: 2026-07-08 12:42:47+0000
+ autopkgtest [12:42:47]: version 5.55
+ autopkgtest [12:42:47]: host igor-resolute; command line:
/usr/bin/autopkgtest 'amdsmi_7.2.4-1~26.04.1.dsc' -- null
+ autopkgtest [12:42:47]: testbed release detected to be: resolute
+ autopkgtest [12:43:15]: test run-amdsmi: /bin/bash
debian/tests/amdsmi.sh
+ autopkgtest [12:43:16]: test run-amdsmi: -----------------------]
+ run-amdsmi PASS
+ autopkgtest [12:43:17]: test run-amdsmi: - - - - - - - - - - results -
- - - - - - - - -
+ autopkgtest [12:43:17]: @@@@@@@@@@@@@@@@@@@@ summary
+ run-amdsmi PASS
[ Where problems could occur ]
- 1. JSON reset output (fix 2, low risk): Applications parsing the JSON output
- of `amd-smi reset --pptpowerusage` on multi-GPU systems were receiving
- incomplete or duplicated per-GPU blocks. The fix corrects the ordering;
- any code that was working around the broken output may need updating.
+ 1. JSON reset output (fix 2, low risk): Applications parsing the JSON output
+ of `amd-smi reset --pptpowerusage` on multi-GPU systems were receiving
+ incomplete or duplicated per-GPU blocks. The fix corrects the ordering;
+ any code that was working around the broken output may need updating.
- 2. CPER AFID list (fix 3, very low risk): Systems that were relying on the
- garbage AFID values to detect unknown section types will no longer see
them.
- The correct behaviour is to omit invalid AFIDs entirely.
+ 2. CPER AFID list (fix 3, very low risk): Systems that were relying on the
+ garbage AFID values to detect unknown section types will no longer see
them.
+ The correct behaviour is to omit invalid AFIDs entirely.
- 3. CPER --follow --file redirection (fix 4, low risk): The change redirects
- CPER output away from stdout when --file is specified; any pipeline that
- was capturing stdout from `amd-smi ras --cper --follow --file` will now
- receive an empty stream (output goes to the file instead). This is the
- intended behaviour.
+ 3. CPER --follow --file redirection (fix 4, low risk): The change redirects
+ CPER output away from stdout when --file is specified; any pipeline that
+ was capturing stdout from `amd-smi ras --cper --follow --file` will now
+ receive an empty stream (output goes to the file instead). This is the
+ intended behaviour.
- 4. New monitor flags (fix 1, no risk for existing invocations): The new
- --base-board-temps and --gpu-board-temps flags are purely additive;
default
- monitor output is unchanged. On GPUs that do not expose these sensors all
- values will be N/A.
+ 4. New monitor flags (fix 1, no risk for existing invocations): The new
+ --base-board-temps and --gpu-board-temps flags are purely additive;
default
+ monitor output is unchanged. On GPUs that do not expose these sensors all
+ values will be N/A.
- 5. libamd-smi26-tests install path fix (packaging, no risk): corrects a
- stale install path that only affects the libamd-smi26-tests binary
- package, which is not currently built or shipped.
+ 5. libamd-smi26-tests install path fix (packaging, no risk): corrects a
+ stale install path that only affects the libamd-smi26-tests binary
+ package, which is not currently built or shipped.
[ Other Info ]
- * No ABI breakage: verified both by dpkg-gensymbols against
- debian/libgoamdsmi-shim64-1.symbols at build time (no symbols added,
- removed, or changed) and independently by abigail (abipkgdiff) comparing
the built
- libamd-smi26 and libgoamdsmi-shim64-1 against the binaries currently
- published in resolute (7.2.0-3): 0 function/variable ABI changes in
- either library. The SONAME of the main library remains libamd_smi.so.26;
- libgoamdsmi_shim64 remains .so.1.
- * This update is part of the coordinated ROCm 7.2.4 stack release.
- * PPA: https://launchpad.net/~igorluppi/+archive/ubuntu/amdsmi-7.2.3
- (build 7.2.4-1~26.04.1~ppa1~26.04 uploaded there for resolute. Link is
- old, it says 7.2.3, but it is 7.2.4)
- * Upstream version comparison:
- https://github.com/ROCm/amdsmi/compare/rocm-7.2.0...rocm-7.2.4
- * Packaging now tracks upstream releases from the ROCm/rocm-systems
- monorepo (https://github.com/ROCm/rocm-systems) as of this update.
- * Target: resolute 26.04 LTS
+ * No ABI breakage: verified both by dpkg-gensymbols against
+ debian/libgoamdsmi-shim64-1.symbols at build time (no symbols added,
+ removed, or changed) and independently by abigail (abipkgdiff) comparing
the built
+ libamd-smi26 and libgoamdsmi-shim64-1 against the binaries currently
+ published in resolute (7.2.0-3): 0 function/variable ABI changes in
+ either library. The SONAME of the main library remains libamd_smi.so.26;
+ libgoamdsmi_shim64 remains .so.1.
+ * This update is part of the coordinated ROCm 7.2.4 stack release.
+ * PPA: https://launchpad.net/~igorluppi/+archive/ubuntu/amdsmi-7.2.3
+ (build 7.2.4-1~26.04.1~ppa1~26.04 uploaded there for resolute)
+ * Upstream version comparison:
+ https://github.com/ROCm/amdsmi/compare/rocm-7.2.0...rocm-7.2.4
+ * Packaging now tracks upstream releases from the ROCm/rocm-systems
+ monorepo (https://github.com/ROCm/rocm-systems) as of this update.
+ * Target: resolute 26.04 LTS
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2153816
Title:
SRU: New upstream version 7.2.4
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/amdsmi/+bug/2153816/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
