Skip to content

test(amdsmi): blacklist unsupported temp/frequency subtests on gfx1103 - #10695

Merged
marifamd merged 1 commit into
developfrom
users/adam360x/ROCM-29359
Aug 31, 2026
Merged

marifamd merged 1 commit into
developfrom
users/adam360x/ROCM-29359

Conversation

@adam360x

@adam360x adam360x commented Aug 25, 2026 •

Copy link
Copy Markdown
Contributor

Summary

Extends the amdsmitst device-specific blacklist (added in #3210 for gfx115X / Strix Point) to cover gfx1103 / Hawk Point APUs, which reproduce the same 3-subtest failure signature.

Background

gfx1103 (Hawk Point) APUs expose the same unsupported driver metrics v3.0 read/write paths as the gfx115X APUs. The driver returns AMDSMI_STATUS_UNEXPECTED_DATA (43) instead of NOT_SUPPORTED for HBM/VRAM temperatures and several clock domains, so these subtests fail:

  • GpuFunctionalReadOnly.TempRead
  • GpuFunctionalReadOnly.TestFrequenciesRead
  • GpuFunctionalReadWrite.TestFrequenciesReadWrite

Observed on AMD Radeon 780M, gfx1103 with a TheRock 10.1.0 build: 63 pass / 3 fail / 1 skip.

Changes

  • tests/amd_smi_test/amdsmitst.exclude: add FILTER[hawk_point] (identical 3-test set to strix_point) plus a FILTER[gfx1103] alias.
  • tests/amd_smi_test/detect_asic_filter.sh: map the gfx1103 target-graphics string to the new filter so ASIC detection selects it (the box's amd-smi reports gfx1103).

Validation

  • bash -n syntax check passes; sourcing yields FILTER[gfx1103] == FILTER[hawk_point] == FILTER[strix_point].
  • End-to-end gfx1103 -> GFX_TO_ASIC -> FILTER resolves to the device-specific blacklist.

Notes

JIRA ID: ROCM-29359

…3 (Hawk Point)

Hawk Point (gfx1103) APUs expose the same unsupported driver metrics v3.0 read/write paths as the gfx115X (Strix Point) APUs, causing GpuFunctionalReadOnly.TempRead, GpuFunctionalReadOnly.TestFrequenciesRead and GpuFunctionalReadWrite.TestFrequenciesReadWrite to fail (driver returns UNEXPECTED_DATA instead of NOT_SUPPORTED).

Add a device-specific amdsmitst blacklist for hawk_point/gfx1103 mirroring the existing gfx115X entry, and map the gfx1103 target-graphics string to it in detect_asic_filter.sh so ASIC detection selects the filter.
@adam360x
adam360x requested review from a team and a lite review from Copilot August 25, 2026 15:00
@therock-pr-bot

Copy link
Copy Markdown

✅ All Policy Checks Passed

Check Status Details
📝 PR Description ✅ Pass —
⛔ Forbidden Files ✅ Pass —
🧪 Unit Test ✅ Pass PR does not contain code files — Unit Test auto-passed
🚫 Draft PR 🔜 To Be Enabled —
🚩 Feature Flag 🔜 To Be Enabled —
📊 Code Coverage 🔜 To Be Enabled —

🎉 All policy checks passed!

📖 Need help? See the Policy FAQ for details on every check and how to fix failures.

🙋 Wish to Override Policy?

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Extends AMD SMI test filtering for Hawk Point (gfx1103) APUs by excluding known unsupported temperature and frequency subtests.

Changes:

  • Adds Hawk Point and gfx1103 blacklist filters.
  • Maps gfx1103 detection to the device-specific filter.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File Summary
projects/amdsmi/tests/amd_smi_test/detect_asic_filter.sh Maps gfx1103 to its filter.
projects/amdsmi/tests/amd_smi_test/amdsmitst.exclude Defines Hawk Point exclusions and alias.

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

@marifamd marifamd changed the title test(amdsmi): blacklist unsupported temp/frequency subtests on gfx1103 (Hawk Point) test(amdsmi): blacklist unsupported temp/frequency subtests on gfx1103 Aug 25, 2026
@marifamd
marifamd merged commit 599174c into develop Aug 31, 2026
173 of 189 checks passed
@marifamd
marifamd deleted the users/adam360x/ROCM-29359 branch August 31, 2026 18:37
@systems-assistant

Copy link
Copy Markdown
Contributor

TheRock Submodule Bump Activity

Newest first

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants