GPU work never completes on Snapdragon X2 (Adreno X2-45): GL draws produce nothing, VA-API decode and Wayland EGL hang
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 34/100
- Issue 类型
- 缺陷
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- linux, ubuntu
- 领域
- backend
调研方向
Start with the supplied diagnostic logs and the GPU rendering and VA-API reproductions; compare the Snapdragon X2 behavior with the X Elite report in #13370. The issue does not identify a WSL source file or failing test, so first narrow down whether the hang is in WSL, WSLg, or the Windows GPU driver. Done means shader draws, Wayland EGL, and VA-API decode complete on the X2.
由索引模型根据 Issue 内容生成。
描述
Windows Version
Microsoft Windows [Version 10.0.28000.3231] (Windows 11 Home 26H1, ARM64)
WSL Version
3.0.3.0
Are you using WSL 1, WSL 2, or WSLC?
- WSL 2
- WSL 1
- WSLC
Kernel Version
6.18.54.1-1 (stock). Also reproduced with a custom build of the same 6.18.54.1 source with only binder added.
Distro Version
Ubuntu 26.04.1 LTS
Other Software
- Device: Surface Pro 12-inch 2nd Edition (Snapdragon X2 Plus).
- GPU: Qualcomm Adreno X2-45, driver 32.0.163.3 (2026-07-23).
- WSL loads driver package
qcdx8480.inf_arm64_d5d90950f5d5b257, which containslibqcdx12arm64wslum.soandqcgpuarm64compilercore.so. - Mesa 26.0.8-1ubuntu0.3, libva 2.23.0.
- WSLg 1.0.79, MSRDC 1.2.7391, Direct3D 1.611.1-81528511, DXCore 10.0.26100.1-240331-1435.ge-release.
Repro Steps
Right after wsl --shutdown, in Ubuntu:
sudo apt install -y mesa-utils vainfo ffmpeg
export GALLIUM_DRIVER=d3d12 LIBVA_DRIVER_NAME=d3d12
# 1. Device and context creation work:
eglinfo -B -p surfaceless | grep 'OpenGL core profile renderer'
# -> OpenGL core profile renderer: D3D12 (Qualcomm(R) Adreno(TM) X2-45 GPU)
# 2. EGL on the WSLg Wayland display hangs:
timeout -s KILL 15 eglinfo -B -p wayland; echo "exit $?"
# -> exit 124 (still blocked after 15 s, in a futex wait)
# 3. Rendering never completes a frame (no "FPS" lines, no gears shown):
timeout -s KILL 10 stdbuf -oL es2gears_wayland
# With GALLIUM_DRIVER=llvmpipe the same command renders normally.
# 4. VA-API lists hardware decode profiles, but decoding never finishes:
vainfo --display drm --device /dev/dri/renderD128 | grep VLD
ffmpeg -loglevel error -f lavfi -i testsrc2=size=1920x1080:rate=60 -t 4 -c:v libx264 -y /tmp/test.mp4
timeout -s KILL 40 ffmpeg -loglevel error -hwaccel vaapi -hwaccel_device /dev/dri/renderD128 -hwaccel_output_format vaapi -i /tmp/test.mp4 -f null -; echo "exit $?"
# -> exit 124 (killed after 40 s). Software decoding of the same clip takes about a second.
Expected Behavior
OpenGL rendering and VA-API decoding run on the GPU through Mesa's d3d12 driver, as they do on x64 GPUs. On the Snapdragon X Elite, per #13370, they work once GALLIUM_DRIVER=d3d12 is set.
Actual Behavior
The GPU is found and contexts are created, but any real GPU work never completes:
- Draws: anything that runs shaders produces no output.
- Fence waits:
eglinfoon Wayland, the firstes2gearsframe, and VA-API decoding all block forever in futex waits. The stuckffmpegdoesn't even respond to SIGTERM. - What works: clears, copies and readbacks. Through virglrenderer (
virgl_test_serverwithGALLIUM_DRIVER=d3d12),glClearplusglReadPixelsreturn correct values, but every draw call is silently dropped, with no GL errors. With llvmpipe on the server side, the same draws are pixel-perfect.
Things ruled out:
- It reproduces right after
wsl --shutdownon Microsoft's stock kernel, so it's not the kernel or a long-running session. - Windows logs no display driver resets (TDR) in the System event log during the hangs.
- Windows Developer Mode is on, and
D3D12_DEBUG=experimentalmakes no difference.
dmesg shows the same lines on the stock and custom kernels:
misc dxg: dxgk: dxgkio_query_adapter_info: Ioctl failed: -22
misc dxg: dxgk: dxgkio_query_adapter_info: Ioctl failed: -2
misc dxg: dxgk: dxgkio_is_feature_enabled: Ioctl failed: -22
Possibly related:
- #13370: on the X Elite (Adreno X1-85),
GALLIUM_DRIVER=d3d12restores acceleration. On the X2 it selects the GPU, but work never completes. - microsoft/wslg#1513: on the Adreno X1-85, GPU processes hang or crash at exit inside
qcgpuarm64compilercore.so.
Diagnostic Logs
- 主要语言
- C++
- 星标
- 34.4k
- 派生
- 1.9k
- 平均合并
- 1 天 23 小时
- 30 天内合并 PR
- 166
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
microsoft/WSL 的其他 Issue
-
feature wsl2
难度 2/5 1-3 小时 新手友好度 80/100
维护者通常 1 天内回复
-
feature
难度 2/5 1-3 小时 新手友好度 72/100
维护者通常 1 天内回复
-
feature kernel wsl2
难度 2/5 1-3 小时 新手友好度 68/100
microsoft/WSL#41107 · 3 条评论 · 1 个 reaction ·
维护者通常 1 天内回复
-
feature kernel
难度 2/5 1-3 小时 新手友好度 82/100
microsoft/WSL#41054 · 9 条评论 · 1 个 reaction ·
维护者通常 1 天内回复
-
feature GPU
难度 1/5 1-3 小时 新手友好度 70/100
维护者通常 1 天内回复
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 82/100
HarperFast/rocksdb-js#1131 ·
维护者通常 1 天内回复
-
area/daemon bug good first issue platform/linux priority/p2
难度 2/5 1-3 小时 新手友好度 72/100
ToshiNamura/Deimos#5 ·
-
needs-format
难度 2/5 1-3 小时 新手友好度 82/100
Niko1221/Strata#6251 · 1 条评论 ·
维护者通常 5 天内回复
-
bug
难度 2/5 1-3 小时 新手友好度 65/100
metasequoiaime/msime#11666 ·
维护者通常 1 天内回复
-
bug
难度 2/5 1-3 小时 新手友好度 70/100
patrick-hudson/put.gd-desktop#1679 · 1 条评论 ·
维护者通常 1 天内回复