[GSD-12963] [BMG/B60] OpenVINO benchmark_app SIGABRT in enqueue_svm.h on dual Arc Pro B60 — Windows fix status unknown
- Dominant language
- C++
- Stars
- 1.4k
- Forks
- 300
- PR merge metrics
- No merged PRs in 30d
Description
### Pre-submission Checklist
- [x] I am using the latest GPU driver version ([download center](https://www.intel.com/content/www/us/en/search.html#sortCriteria=%40lastmodifieddt%20descending&f-downloadtype=Drivers&cf-tabfilter=Downloads&cf-downloadsppth=Graphics))
- [x] I have searched for similar issues and found none
### GPU Hardware
2× Intel Arc Pro B60 (BMG-G21, 24 GB each, PCI 0x0e211)
### GPU Detailed Information
**Summary**
An OpenVINO `benchmark_app` run targeting dual Intel Arc Pro B60 GPUs produces a hard abort in `enqueue_svm.h` at line 308 on some input resolutions. This is a confirmed known issue on Linux, fixed in compute-runtime 26.18.38308.1. The Windows fix status is unknown — this issue is raised to track it.
---
**Reproduction**
Hardware: 2× Intel Arc Pro B60 (BMG-G21, 24 GB each, PCI 0x0e211)
OS tested on Linux: Ubuntu 24.04, kernel 6.17 (crash confirmed + fixed)
OS with unknown status: Windows 10 / Windows 11 (native, not WSL)
OpenVINO toolkit: 2026.1
Command:
benchmark_app -m yolov11n_640x640.xml -d MULTI:GPU.0,GPU.1
**Observed behaviour**
Works at 320×320. Crashes at 640×640 with:
Abort was called at 308 line in file:
./opencl/source/command_queue/enqueue_svm.h
**Linux fix**
Upgrading to compute-runtime 26.18.38308.1 resolves the crash on Linux.
Release: https://github.com/intel/compute-runtime/releases/tag/26.18.38308.1
**Question for the team**
1. Is the same fix present in any released Windows Arc Graphics driver?
2. If yes, which driver version (e.g. 32.0.101.XXXX)?
3. If not yet released, is there an ETA or a workaround recommended for Windows users?
The release notes for 26.18.38308.1 reference Windows host driver 101.8629 for WSL validation only — this does not confirm the fix is present for native Windows inference.
Latest public Arc Windows driver at time of filing: 32.0.101.8826 (released 2026-06-03)
Driver download: https://www.intel.com/content/www/us/en/download/785597/intel-arc-graphics-windows.html
### Driver Installation Details
https://www.intel.com/content/www/us/en/download/785597/intel-arc-graphics-windows.html
### Windows Build Information
Windows 11 Pro
### Actual Behavior
**Linux fix**
Upgrading to compute-runtime 26.18.38308.1 resolves the crash on Linux.
Release: https://github.com/intel/compute-runtime/releases/tag/26.18.38308.1
**Question for the team**
1. Is the same fix present in any released Windows Arc Graphics driver?
2. If yes, which driver version (e.g. 32.0.101.XXXX)?
3. If not yet released, is there an ETA or a workaround recommended for Windows users?
### Expected Behavior
Application should not crash
### Reproduction Rate
Always reproduces - 100%
### Steps to Reproduce
Follow : https://github.com/openvinotoolkit/model_server/issues/4273
### 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_
### Windows Event Viewer Logs
_No response_
### Crash Dumps / Minidumps
_No response_
### Source Code / Reproducer
_No response_
### Command Line / Application Details
_No response_
### oneAPI Version (if applicable)
_No response_
### System Configuration
_No response_
### Screenshots / Video
_No response_
### Intel System Support Utility Report
_No response_
### Additional Notes
_No response_
Contributor guide
Research direction
Start by reproducing the OpenVINO benchmark_app command with dual GPUs and inspect the abort at opencl/source/command_queue/enqueue_svm.h:308. Compare the Linux fix in compute-runtime 26.18.38308.1 with native Windows driver behavior, using the reported Windows 10/11 setup. Done means documenting whether a released Windows driver contains the fix, its version, or a confirmed workaround.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, linux
- Domain
- computer-graphics, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100