OpenCL build failure with NVIDIA GeForce GTX 980 Ti GPU #48972

Closed
opened 2016-07-29 18:08:24 +02:00 by Rob-ART Morgan · 12 comments

System Information
OS X 10.11.5, 2013 Mac Pro 8-core, Dual FirePro D700 internal GPUs, Single GTX 980 Ti in BizonBOX connected via Thunderbolt 2 port

Blender Version
Broken: 2.77a
Worked: (optional)

Short description of error
OpenCL build failure

Exact steps for others to reproduce the error
If the NVIDIA GeForce GTX 980 Ti is selected as CUDA device the scene renders normally, but build fails with OpenCL render selected. This GTX 980 Ti does support OpenCL because it is successfully used in OpenCL mode on other apps like DaVinci Resolve.

**System Information** OS X 10.11.5, 2013 Mac Pro 8-core, Dual FirePro [D700](https://archive.blender.org/developer/D700) internal GPUs, Single GTX 980 Ti in BizonBOX connected via Thunderbolt 2 port **Blender Version** Broken: 2.77a Worked: (optional) **Short description of error** OpenCL build failure **Exact steps for others to reproduce the error** If the NVIDIA GeForce GTX 980 Ti is selected as CUDA device the scene renders normally, but build fails with OpenCL render selected. This GTX 980 Ti does support OpenCL because it is successfully used in OpenCL mode on other apps like DaVinci Resolve.
Rob-ART Morgan self-assigned this 2016-07-29 18:08:24 +02:00
Author

Changed status to: 'Open'

Changed status to: 'Open'
Author

Added subscriber: @barefeats

Added subscriber: @barefeats

Added subscriber: @ThomasDinges

Added subscriber: @ThomasDinges

There is no real point in using OpenCL on a nvidia card, as CUDA is usually faster and supports more features. I suspect the issue is the Apple driver here, which we cannot fix.

You can attach the error log if there is any (start Blender from the Terminal).

There is no real point in using OpenCL on a nvidia card, as CUDA is usually faster and supports more features. I suspect the issue is the Apple driver here, which we cannot fix. You can attach the error log if there is any (start Blender from the Terminal).
Author

Agree that CUDA is preferred for NVIDIA GPUs, but in my situation, I have two internal FirePro GPUs and one external GTX 980 Ti (in GPU expander). The only way to get Blender to render with all three is to designate all three as OpenCL devices.

This scenario works just fine with DaVinci Resolve when rendering GPU intensive Noise Reduction. Using all three provides a performance gain in that case.

Agree that CUDA is preferred for NVIDIA GPUs, but in my situation, I have two internal FirePro GPUs and one external GTX 980 Ti (in GPU expander). The only way to get Blender to render with all three is to designate all three as OpenCL devices. This scenario works just fine with DaVinci Resolve when rendering GPU intensive Noise Reduction. Using all three provides a performance gain in that case.

I understand the issue. As suggested, you can try to start Blender from a Terminal and see if there is an error message. Also you may want to try a new build from builder.blender.org, 2.77 is pretty old by now, maybe the issue has been fixed (if on our side).

I understand the issue. As suggested, you can try to start Blender from a Terminal and see if there is an error message. Also you may want to try a new build from builder.blender.org, 2.77 is pretty old by now, maybe the issue has been fixed (if on our side).
Rob-ART Morgan was unassigned by Bastien Montagne 2016-07-29 19:04:01 +02:00
Author

Hmm. I went to builder.blender.org and 2.77 is the latest build version. What am I missing?

Meanwhile, here is the error message that showed up when launched in Terminal:

Device init success
Compiling OpenCL kernel ...
Build flags:
OpenCL error (GeForce GTX 980 Ti): [CL_DEVICE_NOT_AVAILABLE] : OpenCL Error : Error: Build Program driver returned (10007)
OpenCL error (GeForce GTX 980 Ti): OpenCL Warning : clBuildProgram failed: could not build program for 0x1022700 (GeForce GTX 980 Ti) (err:-2)
OpenCL error (GeForce GTX 980 Ti): [CL_BUILD_ERROR] : OpenCL Build Error : Compiler build log:
Error getting function data from server

OpenCL kernel build output:
Error getting function data from server
OpenCL build failed: errors in console
Error: OpenCL build failed: errors in console

Hmm. I went to builder.blender.org and 2.77 is the latest build version. What am I missing? Meanwhile, here is the error message that showed up when launched in Terminal: Device init success Compiling OpenCL kernel ... Build flags: OpenCL error (GeForce GTX 980 Ti): [CL_DEVICE_NOT_AVAILABLE] : OpenCL Error : Error: Build Program driver returned (10007) OpenCL error (GeForce GTX 980 Ti): OpenCL Warning : clBuildProgram failed: could not build program for 0x1022700 (GeForce GTX 980 Ti) (err:-2) OpenCL error (GeForce GTX 980 Ti): [CL_BUILD_ERROR] : OpenCL Build Error : Compiler build log: Error getting function data from server OpenCL kernel build output: Error getting function data from server OpenCL build failed: errors in console Error: OpenCL build failed: errors in console

Added subscriber: @Denis-3

Added subscriber: @Denis-3

I need gtx 980ti OpenCl to work too, so what is the problem with that error?

I need gtx 980ti OpenCl to work too, so what is the problem with that error?

Added subscriber: @Sergey

Added subscriber: @Sergey

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'
Sergey Sharybin self-assigned this 2016-10-11 11:39:25 +02:00

This is a bug in the compiler. It's possibly to try working something around in the code, but overall it is not officially supported configuration and fixing this will happen outside of the bug tracker.

Please also note that we are starting to push split kernel to a product level now (and as a side effect make all related code easier for maintenance) so that work should solve OpenCL errors on all platforms (or at least make them much easier to investigate).

This is a bug in the compiler. It's possibly to try working something around in the code, but overall it is not officially supported configuration and fixing this will happen outside of the bug tracker. Please also note that we are starting to push split kernel to a product level now (and as a side effect make all related code easier for maintenance) so that work should solve OpenCL errors on all platforms (or at least make them much easier to investigate).
Sign in to join this conversation.
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
4 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#48972
No description provided.