Opened 7 years ago

Closed 6 years ago

Last modified 6 years ago

#974 closed defect (obsolete)

blacklist Intel HD 620/630 for double precision

Reported by: pkienzle Owned by:
Priority: major Milestone: SasView 4.2.0
Component: SasView Keywords:
Cc: Work Package: SasView Bug Fixing


Double precision models are failing for the new Kaby Lake processor series from Intel (HD 620/630). Until the drivers are fixed we need to avoid using this GPU for double precision.

We cannot reliably identify the GPU device from OpenCL; on Ubuntu it identifies only as Intel HD Graphics, not the particular model number. Instead we will need to to extend sasmodels.kernelcl so that we can indicate which device should be used for single precision and which should be used for double precision, and extend sas.sasgui.perspectives.fitting.gui_options so that we can indicate which device to use for single precision and which device to use for double precision.

We could use the code from the following to identify processor:

which has Win32CPUInfo, DarwinCPUInfo, LinuxCPUInfo; from there we can get family/model/stepping for intel processors, and by knowing the Kaby Lake processor family, exclude them by default from double precsion devices.

Change History (5)

comment:1 Changed 7 years ago by pkienzle

Don't need to identify the processor just yet. For now reject fp64 on a GPU device if the vendor is Intel. That will get around the problems on HD 620/630 but won't address the problems with Iris 6100, HD 4400 and HD 5500 identified in OpenClTest.

Kaby Lake CPU IDs extracted from

Family-model-stepping Processor
6-142-9 Intel Core i3-7100U @ 2.40 GHz
6-142-9 Intel Core i5-7200U @ 2.69 GHz
6-142-9 Intel Core i5-7300U @ 2.69 GHz
6-142-9 Intel Core i7-7600U @ 2.89 GHz
6-158-9 Intel Core i3-7100 @ 800 MHz
6-158-9 Intel Core i5-7400 @ 2.99 GHz
6-158-9 Intel Core i5-7600 @ 3.50 GHz
6-158-9 Intel Core i7-7700 @ 3.60GHz
6-158-9 Intel Core i7-7700K @ 4.20 GHz
6-158-9 Intel Core i7-7700HQ @ 2.79 GHz
6-158-9 Intel Xeon E3-1505M v6 @ 2.99 GHz

comment:2 Changed 6 years ago by butler

  • Milestone changed from SasView 4.2.0 to SasView 4.3.0

comment:3 Changed 6 years ago by pkienzle

Newer Intel OpenCL drivers may have fixed the problem (at least it did on a HD 6100 GPU).

comment:4 Changed 6 years ago by krzywon

  • Resolution set to obsolete
  • Status changed from new to closed

I just tested this on my home laptop, one of the first computers to find this issue, and every test passes after checking I had the latest drivers.

Laptop specs: Intel Core i5-7200U, HD 620 GPU

comment:5 Changed 6 years ago by butler

  • Milestone changed from SasView 4.3.0 to SasView 4.2.0
Note: See TracTickets for help on using tickets.