Skip to content

[L0] memory copy tests failing on DG2, when using level_zero v2 #23392

Open

Description

@cperkinsintel

Describe the bug

On DG2, the default driver configuration is V1 of level_zero. However, the CI does run the V2 variant and the latest L0 driver is failing on two of the tests.

Presently we see this on two PRs (possibly more):
#23375
#23385

To reproduce

$ llvm-lit ../llvm/sycl/test-e2e/USM/memops2d/ --param sycl_devices=level_zero_v2:gpu

********************
Failed Tests (2):
  SYCL :: USM/memops2d/copy2d_device_to_host.cpp
  SYCL :: USM/memops2d/memcpy2d_host_to_device.cpp

Environment

Linux. DG2 machine

$ sycl-ls
[level_zero:gpu][level_zero:0] Intel(R) oneAPI Unified Runtime over Level-Zero, Intel(R) Arc(TM) A770 Graphics 12.55.8 [1.17.39758+11]
[level_zero:gpu][level_zero:1] Intel(R) oneAPI Unified Runtime over Level-Zero, Intel(R) UHD Graphics 770 12.2.0 [1.17.39758+11]
[opencl:gpu][opencl:0] Intel(R) OpenCL Graphics (discrete), Intel(R) Arc(TM) A770 Graphics OpenCL 3.0 NEO  [26.35.39758.11]
[opencl:gpu][opencl:1] Intel(R) OpenCL Graphics (integrated), Intel(R) UHD Graphics 770 OpenCL 3.0 NEO  [26.35.39758.11]


Additional context

No response

Activity

  1. kekaczma commented on Oct 15, 2026

    @kekaczma
    Contributor

    I see similar issue with USM/memops2d/copy2d_host_to_device.cpp. Same environment (Linux, Arc/DG2, R_LOADER_USE_LEVEL_ZERO_V2=1) and same signature as the two files already tracked here — destination byte still holds the pre-copy memset value instead of the expected fill pattern:

    Test 5 (host USM allocation to device USM allocation, no shortcut and no depends_on)
    Value at 390 did not match the expected value; 0 != 1234
    

    Run: https://github.com/intel/llvm/actions/runs/38753395952/job/116500763453

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

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions