Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

examine: Strix Halo APU (gfx1151, Ryzen AI Max+ 395) misclassified as discrete GPU (has_apu=false)

Aperta
  • Qualcosa non va?
#449 1 commento 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 2 giorni

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
55/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
rust
Ambito
cli

Direzione di ricerca

Start with the rocm examine --json entry point and trace how GPU metadata, gfx_target, is_apu, and has_apu are derived; compare that path with the gfx-target lookup discussed in #393. Reproduce against the Strix Halo evidence in the issue, then verify that gfx1151 is classified as an APU without misclassifying discrete AMD GPUs.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Summary

On an AMD Ryzen AI Max+ 395 (Strix Halo, gfx1151), rocm examine --json classifies the machine as having no APU ("has_apu": false, GPU entry "is_apu": false, "has_discrete_amd": true). This is a discrete-GPU-only misclassification of an iGPU-with-unified-memory APU, and it feeds wrong routing to consumers that branch on has_apu (APU-specific diagnostics and GTT/memory-tuning flows get skipped on exactly the machines where GTT tuning is the whole point).

Environment

  • OS: Ubuntu 24.04, kernel 6.17.0-1032-oem (Ubuntu OEM)
  • APU: AMD Ryzen AI Max+ 395 w/ Radeon 8060S (Strix Halo, gfx1151)
  • rocm-cli: 0.1.0 (main, 8788394) (nightly channel installer)

Observed

"gpus": [
  {
    "name": "Advanced Micro Devices, Inc. [AMD/ATI] Device",
    "gfx_target": "",
    "pci_id": "0000:66:00.0",
    "is_apu": false,
    "is_amd": true
  }
],
"has_amd_gpu": true,
"has_apu": false,
"has_discrete_amd": true

Ground truth from other official tools on the same machine:

  • amd-smi static: MARKET_NAME: AMD Radeon 8060S Graphics, TARGET_GRAPHICS_VERSION: gfx1151, MEM_CARVEOUT present, VRAM 8192 MB (DRAM-backed)
  • rocminfo: agent Name: gfx1151
  • Unified-memory evidence: mem_info_vram_total=8589934592 alongside a 96 GiB GTT (ttm.pages_limit=25165824) — classic UMA APU split

Expected

has_apu / is_apu should be true for Strix Halo and other Radeon-A APUs.

Suggested fix

PCI-topology heuristics alone miss APUs whose iGPU enumerates on a separate host bridge (Strix Halo exposes the GPU at 0000:66:00.0). Consider classifying by one of:

  • gfx target set: gfx1150 / gfx1151 / gfx1152 are APU-only LLVM targets — a whitelist here is cheap and precise
  • UMA detection: VRAM carve-out is DRAM-backed (no separate HBM/GDDR instance) — amd-smi already exposes this shape

Note: gfx_target being empty in examine output (see #393) is likely also feeding this — fixing the gfx-target lookup would give this classification the cheap precise signal.

Impact

Downstream consumers branching on has_apu misroute: e.g. the official rocm-doctor skill's APU flows and GTT-related diagnostics are skipped on this machine even though GTT tuning (currently 8 GiB carve-out + 96 GiB GTT) is this platform's headline feature.

Lingua principale
Rust
Stelle
45
Fork
11
Merge medio
3g 23h
PR unite (30g)
145

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di ROCm/rocm-cli

Tutte le issue di ROCm/rocm-cli

Issue simili

Altre issue su Rust

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.