Hacktoberfest 2026: die Issues, die Maintainer für den Oktober markiert haben – offen und einsteigerfreundlich. Hacktoberfest-Issues durchsuchen

[GSD-13016] Sysman events are not supported with the release packages

Offen
  • Stimmt etwas nicht?
#950 2 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
3/5
Geschätzter Aufwand
1-2 Tage
Anfängerfreundlichkeit
58/100
Issue-Typ
Bug
Klarheit
Größtenteils klar
Aktivitätsstatus
Ruhig
Tech-Stack
cmake, cpp, linux
Bereich
build-system, operating-systems

Rechercherichtung

Beginne mit level_zero/tools/source/sysman/linux/udev/CMakeLists.txt und der Konfiguration für das Release-Paketieren, und baue dann zello_sysman unter Ubuntu 24.04 gegen die Release-Bibliotheken. Vergleiche die Release-Binärdateien mit den lokal gebauten Binärdateien auf libudev-Unterstützung und führe zello_sysman mit ZELLO_SYSMAN_USE_ZESINIT=1 aus; abgeschlossen ist die Aufgabe, wenn Release-Pakete sysman-Ereignisse unterstützen und das Warten auf Ereignisse sich wie beim lokalen Build verhält.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

Component: Level Zero Sysman OS: Linux Type: Bug
Pre-submission Checklist
  • I am using the latest GPU driver version (releases)
  • I have searched for similar issues and found none
GPU Hardware

Intel Arc B580

DRI Devices Information

n/a

GPU Detailed Information (lspci output)

n/a

Driver Version

26.22.38646.4

Installed GPU Driver Packages

$ dpkg --list | grep -iE "libze"
ii libze-dev 1.31.0 amd64 oneAPI Level Zero
ii libze-intel-gpu1 26.22.38646.4-0 amd64 Intel(R) Graphics Compute Runtime for oneAPI Level Zero.
ii libze1 1.31.0 amd64 oneAPI Level Zero

Driver Installation Details

With dpkg/apt

Linux Distribution

Ubuntu 24.04 LTS

Other Linux Distribution

No response

Kernel Version & Boot Parameters

n/a

Actual Behavior

I installed the latest release packages to a 24.04 Ubuntu system (https://github.com/intel/compute-runtime/releases/tag/26.22.38646.4) and built the zello_sysman tool from the same sources.

When I run the tool against the release packages I get this behavior:

$ export PrintDebugMessages=1
$ export NEOReadDebugKeys=1
$ sudo -E ZELLO_SYSMAN_USE_ZESINIT=1 ./workspace/compute-runtime/build/bin/zello_sysman -E
ZES_ENABLE_SYSMAN environment variable Not Set
WARNING: Failed to request OCL Turbo Boost
WARNING: Failed to request OCL Turbo Boost
Sysman Initialization done via zesInit
libudev library instantiation failed

The key line being the last libudev library instantiation failed. The execution also takes only <1sec, while it should wait for events.

When I run the same tool against compute-runtime libraries that I built myself:

$ sudo -E LD_LIBRARY_PATH=./workspace/compute-runtime/build/bin ZELLO_SYSMAN_USE_ZESINIT=1 ./workspace/compute-runtime/build/bin/zello_sysman -E
ZES_ENABLE_SYSMAN environment variable Not Set
WARNING: Failed to request OCL Turbo Boost
WARNING: Failed to request OCL Turbo Boost
Sysman Initialization done via zesInit

No line about libudev and the execution takes 10 seconds.

When checking the binaries for udev strings:

$ strings /usr/lib/x86_64-linux-gnu/libze_intel_gpu.so.1 | grep -E udev
libudev library instantiation failed

:~/workspace/compute-runtime/build$ strings bin/libze_intel_gpu.so | grep -E "udev"
libudev.
libudev.
udev_monitor_new_from_netlink
udev_monitor_enable_receiving
udev_monitor_get_fd
udev_monitor_receive_device
udev_device_get_devnum
udev_device_get_action
udev_device_unref
libudev library instantiation failed
udev_monitor_filter_add_match_subsystem_devtype
udev_device_get_property_value
udev_new
udev_new
...

My binary has udev strings while the release binary does not. Looking at the level_zero/tools/source/sysman/linux/udev/CMakeLists.txt file, the compilation is conditional based on if libudev is found. Most likely the build env doesn't have libudev-dev thus the releases never support sysman events.

Expected Behavior

Release version of compute runtime should support sysman events.

Reproduction Rate

Always reproduces - 100%

Steps to Reproduce
  • Install compute-runtime and its dependencies
  • Build zello_sysman
  • Run zello_sysman
$ export PrintDebugMessages=1
$ export NEOReadDebugKeys=1
$ sudo -E ZELLO_SYSMAN_USE_ZESINIT=1 ./zello_sysman -E
  • The execution should wait for events (~10sec) or stop on an event.
Is this a regression?
  • Yes, this is a regression - functionality that previously worked is now broken
Last Known Working Driver Version

No response

First Known Failing Driver Version

No response

API Call Logs

No response

strace Logs

No response

System Logs / dmesg Output

No response

Backtrace (if crash or hang occurred)

No response

Source Code / Reproducer

No response

Command Line / Application Details

No response

oneAPI Version (if applicable)

No response

Screenshots / Video

No response

Additional Notes

No response

Vorherrschende Sprache
C++
Sterne
1.5k
Forks
303
Keine gemergten PRs in 30 T.

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus intel/compute-runtime

Alle Issues in intel/compute-runtime

Ähnliche Issues

Weitere Issues zu C++

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.