Skip to content

Conversation

sarnex
Copy link
Contributor

@sarnex sarnex commented Apr 2, 2025

Reverts #17778

Same problem

@sarnex sarnex requested a review from a team as a code owner April 2, 2025 21:26
@sarnex sarnex merged commit 363faec into sycl Apr 2, 2025
14 checks passed
@sarnex sarnex temporarily deployed to WindowsCILock April 2, 2025 21:26 — with GitHub Actions Inactive
@sarnex
Copy link
Contributor Author

sarnex commented Apr 2, 2025

@npmiller @kbenzie @pbalcer Can you guys help us look into this? 1.20.6 also has no device found.

@sarnex sarnex temporarily deployed to WindowsCILock April 2, 2025 21:49 — with GitHub Actions Inactive
@sarnex sarnex temporarily deployed to WindowsCILock April 2, 2025 21:49 — with GitHub Actions Inactive
@bader bader deleted the revert-17778-l0up branch April 3, 2025 00:01
@npmiller
Copy link
Contributor

npmiller commented Apr 3, 2025

I don't have experience with level zero, so I can't help much on this unfortunately

@pbalcer
Copy link
Contributor

pbalcer commented Apr 3, 2025

@npmiller @kbenzie @pbalcer Can you guys help us look into this? 1.20.6 also has no device found.

I ran this exact combination of driver/loader/igc and it worked fine. Admittedly I built it all from source.

@nrspruit any ideas?

@sarnex
Copy link
Contributor Author

sarnex commented Apr 3, 2025

ok ill try to repro locally and do a deep dive, might need help from you guys as i dont know anything about level zero :P

@pbalcer
Copy link
Contributor

pbalcer commented Apr 3, 2025

ok ill try to repro locally and do a deep dive, might need help from you guys as i dont know anything about level zero :P

We have driver build automated in benchmark scripts.

You can test this like so:
./main.py ~/workdir --compute-runtime 25.09.32961.7 --build-igc --filter api_overhead_benchmark_sycl --sycl /path/to/llvm/build

This will first build the entire compute-runtime from source, with matching IGC, gmmlib and level-zero versions, and then run a simple test to verify whether it worked (there's a --verbose option if you want to see the commands it executes).

I just ran it and it worked.

@sarnex
Copy link
Contributor Author

sarnex commented Apr 3, 2025

thanks, let me try that on the runner inside docker to see if the problem lies there somewhere

@sarnex
Copy link
Contributor Author

sarnex commented Apr 8, 2025

@pbalcer @nrspruit I found the problem, and it's way simplier than I imagined.

The L0 releases no longer have any binaries. We use the deb binaries to install L0. Since there are no binaries the install fails and thus we have no L0 so no devices are found.

@nrspruit Is it intended that the newer L0 releases have no binaries?

Last good example (1.20.2) here
Bad example here

If this is intentional I'll change our scripts to build L0 from source.

@sarnex
Copy link
Contributor Author

sarnex commented Apr 10, 2025

@nrspruit Can you comment on the above finding? Thx

@sarnex
Copy link
Contributor Author

sarnex commented Apr 14, 2025

Fixed in #18016, thx all!

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants