[GSD-13651] Level Zero Sysman gaps on Arc Pro B70 (BMG, PCI id 0xe223): temperature, memory bandwidth, device health, firmware version
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 48/100
- Issue 类型
- 缺陷
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- cpp, linux
- 领域
- api, operating-systems
调研方向
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.
由索引模型根据 Issue 内容生成。
描述
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, GuCbmg_guc_70.bin v70.58.0, HuCbmg_huc.bin v8.2.10, DMCbmg_dmc.bin) - Observed on 8×
0xe223on 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 readingsenergy1_input,energy2_input→ monotonic card + package energy countersfan1_input→ RPMin*_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!
- 主要语言
- C++
- 星标
- 1.5k
- 派生
- 303
- PR 合并指标
- 30 天内没有已合并 PR
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
intel/compute-runtime 的其他 Issue
-
难度 2/5 1-3 小时 新手友好度 78/100
intel/compute-runtime#943 ·
-
难度 5/5 一周以上 新手友好度 12/100
intel/compute-runtime#1026 ·
-
难度 5/5 一周以上 新手友好度 15/100
intel/compute-runtime#1024 ·
-
难度 1/5 1 小时以内 新手友好度 1/100
intel/compute-runtime#1022 ·
-
难度 4/5 3-5 天 新手友好度 35/100
intel/compute-runtime#1019 ·
查看 intel/compute-runtime 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 72/100
维护者通常 1 天内回复
-
accessibility good first issue hacktoberfest help wanted
难度 2/5 1-3 小时 新手友好度 74/100
OpenChemistry/avogadrolibs#3184 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 68/100
Tracktion/tracktion_engine#475 ·
维护者通常 1 天内回复
-
难度 1/5 1 小时以内 新手友好度 62/100
orbiternassp/NASSP#1701 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 72/100
redis/memtier_benchmark#732 ·
维护者通常 1 天内回复