Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

[GSD-13651] Level Zero Sysman gaps on Arc Pro B70 (BMG, PCI id 0xe223): temperature, memory bandwidth, device health, firmware version

Abierto
  • ¿Algo no está bien?
#1,013 1 comentario 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
48/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
cpp, linux
Área
api, operating-systems

Línea de trabajo

Reproduce the B70 behavior with zello_sysman or xpu-smi discovery -j and compare the failing Sysman calls with an Arc Pro B60. Start by locating the Sysman device-support table or per-device handlers mentioned in the report. Done means B70 temperature, bandwidth, health, RAS, and firmware queries no longer return unsupported or empty results, with appropriate coverage for the affected device ID.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

Component: Level Zero Sysman Status: Needs Feedback

Summary

On Arc Pro B70 workstation GPUs (BMG, PCI device id 0xe223), several Level Zero Sysman APIs return ZE_RESULT_ERROR_UNSUPPORTED_FEATURE or empty enumerations, even though the equivalent data is available at the kernel level through /sys/class/hwmon (xe driver). Arc Pro B60 (0xe211) on the same software stack is fully functional.

Environment

  • Host: Ubuntu 26.04.1 LTS, kernel 7.0.0-34-generic
  • GPU driver: in-tree xe (loaded, GuC bmg_guc_70.bin v70.58.0, HuC bmg_huc.bin v8.2.10, DMC bmg_dmc.bin)
  • Observed on 8× 0xe223 on the same host, consistent per device.

What xpumd / zes* reports (via https://github.com/intel/xpumanager)

Per-device during startup:

Device GetHealthStatusExt() failed: complete device health status not available
  error=ERROR_UNSUPPORTED_FEATURE  (zesDeviceGetState / zesDeviceGetSubState)
Memory GetBandwidth() failed: no BW metrics available
  error=ERROR_UNSUPPORTED_FEATURE  (zesMemoryGetBandwidth)
Sysman temperature sensors   created: 0, enumerated: 0  (zesDeviceEnumTemperatureSensors)
Sysman RAS error sets        created: 0, enumerated: 0  (zesDeviceEnumRasErrorSets)
hw.firmware_version          ""     (zesDeviceGetProperties → modelName OK, firmwareVersion empty)

Working on the same device: engine groups (14), frequency domains (2), power domains (2).

What the kernel exposes (same host, same device)

Every B70 has an xe-named hwmon device under /sys/class/hwmon with:

  • temp2..temp21 + temp*_label ("vram", "mctrl", "pcie", "vram_ch_0..3", ...) → 20+ live temperature sensors, sane readings
  • energy1_input, energy2_input → monotonic card + package energy counters
  • fan1_input → RPM
  • in*_input / curr*_input → voltages / currents (per card)

So the data is in-kernel; the gap is in the user-space Level Zero Sysman implementation for this device ID.

Comparison: B60 vs B70 on the same stack

Metric B60 (0xe211) B70 (0xe223)
zesDeviceGetState ✔ UNSUPPORTED_FEATURE
zesMemoryGetBandwidth ✔ UNSUPPORTED_FEATURE
zesDeviceEnumTemperatureSensors ✔ (N > 0) 0 enumerated
zesDeviceEnumRasErrorSets ✔ 0 enumerated
firmwareVersion string populated empty
zesDeviceEnumFrequencyDomains ✔ ✔
zesDeviceEnumEngineGroups ✔ ✔
zesDeviceEnumPowerDomains ✔ ✔

Same host OS, same compute-runtime, same xpumd / chart build — only the device id differs.

Reproducer

Any zesXxxEnum / zesXxxGet call against the B70's Sysman handle will reproduce. Easiest standalone: zello_sysman (or xpu-smi discovery -j) against an Arc Pro B70.

Likely area

Looks like the Sysman device-support table / per-device handlers haven't been extended for BMG workstation variants beyond the B60 range (0xe210..0xe212). The newer datacenter range (0xe220..0xe223) hits the fall-through path and returns UNSUPPORTED_FEATURE.

Impact

The gaps block xpumanager / xpu-smi / otelcol-intelxpu temperature, bandwidth, and health reporting on every B70 host, so Grafana dashboards source these metrics as "No data" even though the hardware is producing them.

Happy to collect anything else useful (strace/ltrace of a Sysman call, specific ze_result_t values, xpu-smi JSON dumps). Thanks!

Lenguaje dominante
C++
Estrellas
1.5k
Forks
304
Sin PR fusionados en 30 d

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de intel/compute-runtime

Todos los issues de intel/compute-runtime

Issues similares

Más issues de C++

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.