Graphics
Intel® graphics drivers and software, compatibility, troubleshooting, performance, and optimization
21224 Discussions

Compute shader produces incorrect output on Iris 6100 graphics

Evan_O_
Beginner
1,850 Views

I have a simple GLSL compute shader that performs a parallel reduction on an array, which works as expected on Nvidia and AMD gpus but on my macbook with Iris 6100 graphics it produces slightly wrong results.

I've attached a simple test program, if you inspect the code at the end of main.cpp you can see it reads back the buffer that the shader wrote to, and expects every vec4 entry to be (96, 96, 96, 0). On the Iris 6100 the values that are supposed to be 96, will end up being randomly 95, 96, 97, 98, etc, throughout the array.

System Used: Apple, Macbook Pro Retina 13" (2015)
CPU SKU: i7-5557U
GPU SKU: Iris 6100
Processor Line: U series?
System BIOS Version: 
CMOS settings:
Graphics Driver Version: 20.19.15.4352
GOP/VBIOS Version:
Operating System: Windows 10
OS Version: 64-bit
API: OpenGL
Occurs on non-Intel GPUs?: No

Steps to Reproduce:
-------------------------------
1. Build and run attached sample program in debug. 
2.

Expected Results:
Assert at end of main function should not fire (because all compute shader outputs match expected result).

Actual Results:

Compute shader produces incorrect results and assert in test program will fire.

Additional Information:
-------------------------------

0 Kudos
6 Replies
Michael_C_Intel2
Employee
1,850 Views

Hi Evan,

Got the issue filed, and will get the investigation started.

-Michael

0 Kudos
Evan_O_
Beginner
1,850 Views

Hi Michael, 

My test program still seems to be failing after installing that driver. Windows is showing driver version 20.19.15.4444, dated 4/22/2016. Is that the version I should be at?

Thanks,

Evan

 

0 Kudos
Michael_C_Intel2
Employee
1,850 Views

Hi Evan,

Yes that is the latest version available. Thanks for checking I will let the engineer know. 

-Michael 

0 Kudos
Michael_C_Intel2
Employee
1,850 Views

Hi Evan,

We have fixed the issue, the next driver release should include the fix.

0 Kudos
Evan_O_
Beginner
1,850 Views

Thanks for the update, I'll keep an eye out for the next driver release. 

0 Kudos
Reply