#5914 [Engine] Windows SYCL: the Level Zero V2 adapter fails at startup with UR_RESULT_ERROR_UNKNOWN; the legacy adapter works (Arc Pro B70, oneAPI 2026.2)

open · @demetree · 5 commentaires · Sur GitHub

Setup & installAMD / HIPModels & quantsWindowsLinux

Description

## Summary

On Windows, with oneAPI 2026.2 and the current Arc driver, the SYCL engine cannot start when the runtime picks its **Level Zero V2** adapter. Device enumeration is enough to fail:

```
> strata.exe --list-devices
level_zero backend failed with error: 2147483646 (UR_RESULT_ERROR_UNKNOWN)
```

With the V2 adapter switched off, the same binary enumerates the card and serves normally:

```
> set SYCL_UR_USE_LEVEL_ZERO_V2=0
> set UR_LOADER_USE_LEVEL_ZERO_V2=0
> strata.exe --list-devices
[{"index":0,"name":"Intel(R) Arc(TM) Pro B70 Graphics","vram_gb":31.159,"arch":"sycl",
  "driver":"level_zero","free_memory_supported":true,"command_graph_supported":true,"devid":"e223"}, ...]
```

A plain SYCL program built by the same toolkit **does** enumerate the card on the V2 platform, so the device and the platform are reachable; the difference is in what the engine does at startup.

## Environment

- Arc Pro B70 32 GB, driver 32.0.101.8976 (2026-08-27), Level Zero loader 1.32.0.
- oneAPI 2026.2 (icx 2026.2.0, build 20261001).
- Windows 11 25H2 (10.0.26200), Core i9-9900, 64 GB.
- Engine **0.1.59.1** from the `windows-sycl` branch in #3607, built by `sycl/tools/build_windows.bat` (icx direct, 0 AOT).

One thing that belongs in the history, because it is what exposed this: Windows updates KB5132061/KB5132688 left `C:\Windows\System32\ze_loader.dll` at v1.2.3 (2021) while the driver ships v1.32.0, and the engine then died with `0xC0000005` inside `sycl9.dll` on the first device call. Pointing `HKLM\SOFTWARE\Intel\oneAPI\LevelZero\1\LevelZeroLoaderPath` at a folder holding the driver's own v1.32.0 fixed that crash. The V2 failure is the next step up, and it is what this report is about.

## Reproduce

```
:: fails
call "<oneAPI>\setvars.bat" intel64
strata.exe --list-devices

:: works
set SYCL_UR_USE_LEVEL_ZERO_V2=0
set UR_LOADER_USE_LEVEL_ZERO_V2=0
strata.exe --list-devices
```

The serving configuration that now works uses the second form in its `env` block, plus `ONEAPI_DEVICE_SELECTOR=level_zero:gpu`, `ZES_ENABLE_SYSMAN=1`, `STRATA_VERIFY_DEVICE_PLAN=1`, `STRATA_STAGGER_THREADS=12`. It serves 262,144 tokens of context and answered a request in 5.8 s on a cold cache.

## Second symptom, probably the same cause

With V2 active, the device-type selector is not understood:

```
> set ONEAPI_DEVICE_SELECTOR=level_zero:gpu
> strata.exe --list-devices
error parsing device number: gpu
```

The same selector is accepted when V2 is off, and `level_zero:*` is rejected either way. So the V2 platform appears to take only numeric device indices, while the engine's setup writes the type form.

## Plain SYCL, for contrast (V2 active)

```cpp
#include <sycl/sycl.hpp>
#include <cstdio>
int main() {
    for (auto &p : sycl::platform::get_platforms()) {
        std::printf("platform: %s\n", p.get_info<sycl::info::platform::name>().c_str());
        for (auto &d : p.get_devices())
            std::printf("  device: %s gpu=%d\n", d.get_info<sycl::info::device::name>().c_str(), (int) d.is_gpu());
    }
}
```

```
platform: Intel(R) OpenCL Graphics
  device: Intel(R) Arc(TM) Pro B70 Graphics gpu=1
platform: Intel(R) oneAPI Unified Runtime over Level-Zero V2
  device: Intel(R) Arc(TM) Pro B70 Graphics gpu=1
```

## What I think is happening (hypothesis, not traced)

The engine's startup touches things a plain enumeration does not: the free-VRAM query through sysman, command-graph support and capture, and dpct's context/queue helpers. Any of those could be unimplemented or different on the V2 adapter. I have not isolated which call fails; I only know it is inside the engine's device setup, because `strata --version` works and the plain program above works.

## Limits

- One machine, one card, Windows only. Not tried on Linux, on other Arc models, or with an older oneAPI.
- The engine here is the unmerged Windows port (#3607); the same binary is the one that runs this configuration correctly on the legacy adapter.
- I did not measure whether V2 is faster, so I cannot say what is being given up by pinning the legacy adapter.

## Related

#3607 (the Windows SYCL port and its measurements), #5236 (whether a Windows engine ships at all), #4698 (a separate correctness problem in the host-arena path).

The practical question is whether the engine is expected to run on the V2 adapter on Windows, and if so whether it should fall back to the legacy one automatically when V2 initialisation fails, rather than exiting with `UR_RESULT_ERROR_UNKNOWN`.

Sur le site

Liens install, modèles, releases.