Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Runtime error with cn/r algo on OSX : Error CL_BUILD_PROGRAM_FAILURE when calling clBuildProgram #228

Closed
LeChatNoir69 opened this issue Mar 4, 2019 · 15 comments
Labels
Milestone

Comments

@LeChatNoir69
Copy link

LeChatNoir69 commented Mar 4, 2019

Hi,

I'm updating Cryptomac to be ready for upcoming fork and encountered issue when testing new algo (with current algo, it's ok) :

  • ABOUT XMRig-AMD/2.13.0 clang/9.1.0
  • LIBS libuv/1.20.0 OpenCL/1.2 OpenSSL/1.0.2n microhttpd/0.9.59
  • CPU Intel(R) Core(TM) i7-4770HQ CPU @ 2.20GHz x64 AES
  • ALGO cryptonight, donate=1%
  • POOL Update README links and build instruction #1 killallasics.moneroworld.com:3333 variant=auto
  • API BIND 0.0.0.0:42096
  • COMMANDS 'h' hashrate, 'p' pause, 'r' resume
    [2019-03-04 22:53:06] compiling code and initializing GPUs. This will take a while...
    [2019-03-04 22:53:06] AMD GPU #0: intensity is not a multiple of 'worksize', auto reduce intensity to 96
    [2019-03-04 22:53:06] #00, GPU #00 (Iris Pro), i:96 (8/512), si:2/2, u:8, cu:40
    [2019-03-04 22:53:06] 0.19/0.38/2 GB
    [2019-03-04 22:53:06] use pool killallasics.moneroworld.com:3333 66.85.74.134
    [2019-03-04 22:53:06] new job from killallasics.moneroworld.com:3333 diff 5000 algo cn/r height 1166895
    [2019-03-04 22:53:06] Error CL_BUILD_PROGRAM_FAILURE when calling clBuildProgram.
    [2019-03-04 22:53:06] CryptonightR: clBuildProgram returned error CL_BUILD_PROGRAM_FAILURE
    [2019-03-04 22:53:06] Error CL_INVALID_KERNEL when calling clSetKernelArg for kernel 17, argument 0.
    [2019-03-04 22:53:06] Error CL_INVALID_KERNEL when calling clEnqueueNDRangeKernel for kernel 1.
@SomethingGettingWrong
Copy link

SomethingGettingWrong commented Mar 5, 2019

image
New versions doing this for me. Not sure if its similar

@SChernykh
Copy link
Contributor

[2019-03-04 22:53:06] #00, GPU #00 (Iris Pro), i:96 (8/512), si:2/2, u:8, cu:40

I think you're trying to run OpenCL code on Intel integrated GPU. Set proper platform index in config.json (if it's set to 0, try 1).

@LeChatNoir69
Copy link
Author

Nope. It's the right index. If I choose 1, it fails :
[2019-03-05 21:23:20] compiling code and initializing GPUs. This will take a while...
[2019-03-05 21:23:21] Selected OpenCL device index 1 doesn't exist.
[2019-03-05 21:23:21] Failed to start threads.

If I run on other pool with current cn algo and variant -1, everything is fine.

@LeChatNoir69
Copy link
Author

Same issue on OS X with release 2.14

@LeChatNoir69 LeChatNoir69 changed the title Runtime error with cn/r algo : Error CL_INVALID_KERNEL when calling clSetKernelArg for kernel 17, argument 0. Runtime error with cn/r algo on OSX : Error CL_BUILD_PROGRAM_FAILURE when calling clBuildProgram Mar 8, 2019
@LeChatNoir69
Copy link
Author

The issue seems to be in OclGPU.cpp and the first error messages are :
[2019-03-04 22:53:06] Error CL_BUILD_PROGRAM_FAILURE when calling clBuildProgram.
[2019-03-04 22:53:06] CryptonightR: clBuildProgram returned error CL_BUILD_PROGRAM_FAILURE

then

[2019-03-04 22:53:06] Error CL_INVALID_KERNEL when calling clSetKernelArg for kernel 17, argument 0.

17 is the argument for Cryptonight R algo.

@CR4DL
Copy link

CR4DL commented Mar 10, 2019

Same Issue here with Version 2.14 on OS X 10.14.3, AMD FirePro, correct GPU selected.

  • ABOUT XMRig-AMD/2.14.0 clang/10.0.0
  • LIBS libuv/1.26.0 OpenCL/1.2 OpenSSL/1.0.2q
  • CPU Intel(R) Xeon(R) CPU E5-1620 v2 @ 3.70GHz x64 AES
  • ALGO cryptonight, donate=3%
  • POOL Update README links and build instruction #1 localhost:3333 variant auto
  • COMMANDS hashrate, pause, resume
    [2019-03-10 16:20:28] compiling code and initializing GPUs. This will take a while...
    [2019-03-10 16:20:28] #00, GPU #00 AMD Radeon HD - FirePro D500 Compute Engine, i:1024 (8/256), si:2/2, u:8, cu:24
    [2019-03-10 16:20:28] 2.00/0.75/3 GB
    [2019-03-10 16:20:28] use pool localhost:3333 127.0.0.1
    [2019-03-10 16:20:28] new job from localhost:3333 diff 9450 algo cn/r height 1788091
    [2019-03-10 16:20:28] Error CL_BUILD_PROGRAM_FAILURE when calling clBuildProgram.
    [2019-03-10 16:20:28] CryptonightR: clBuildProgram returned error CL_BUILD_PROGRAM_FAILURE
    [2019-03-10 16:20:28] Error CL_INVALID_KERNEL when calling clSetKernelArg for kernel 20, argument 0.
    [2019-03-10 16:20:28] Error CL_INVALID_KERNEL when calling clEnqueueNDRangeKernel for kernel 1.
    [2019-03-10 16:20:29] Error CL_INVALID_KERNEL when calling clEnqueueNDRangeKernel for kernel 1.

@GrigoryMel
Copy link

{
"algo":
"cryptonight",

"background": false,

"colors": true,

"donate-level": 1,

"log-file": null,

"print-time": 60,

"retries": 5,

"retry-pause": 5,

"opencl-platform": 0,

"threads": [{ "index": 0,
"intensity": 768,
"worksize": 10,
"affine_to_cpu": false
},

        {

"index": 1,
"intensity": 768,
"worksize": 10,
"affine_to_cpu": false
},

        { "index": 2,

"intensity": 768,
"worksize": 10,
"affine_to_cpu": false
},

        { "index": 3,

"intensity": 768,
"worksize": 10,
"affine_to_cpu": false
},

       ],

"pools": [
{
"url": "pool.supportxmr.com:7777",

"user": "49FoFSdxuZk46MFMiHXFZv7KPy14pv4cwACkyZSGtvciDFKU6goJgbkeZhnwafFbE9ZSzCZL6LAmx9EgPKxHD9ve5sdBNAJ+30000",
"pass": "HD6991:akademija_trevel@ukr.net",
"keepalive": true,

"nicehash": false,

"variant": -1
}
],

"api": {
"port": 0,

"access-token": null,

"worker-id": null
}
}

@GrigoryMel
Copy link

  • ABOUT XMRig-AMD/2.14.0 MSVC/2017
  • LIBS libuv/1.24.1 OpenCL/2.0 OpenSSL/1.1.1a microhttpd/0.9.61
  • CPU Intel(R) Xeon(R) CPU E5420 @ 2.50GHz x64 -AES
  • ALGO cryptonight, donate=1%
  • POOL Update README links and build instruction #1 pool.supportxmr.com:7777 variant auto
  • COMMANDS hashrate, pause, resume
    [2019-03-10 21:33:50] compiling code and initializing GPUs. This will take a whi
    le...
    [2019-03-10 21:33:51] AMD GPU #0: intensity is not a multiple of 'worksize', aut
    o reduce intensity to 760
    [2019-03-10 21:33:51] #00, GPU #00 AMD Radeon HD 6900 Series (Cayman), i:760 (10
    /256), si:2/2, u:8, cu:24
    [2019-03-10 21:33:51] 1.48/1.75/2 GB
    [2019-03-10 21:33:51] AMD GPU Update README links and build instruction #1: intensity is not a multiple of 'worksize', aut
    o reduce intensity to 760
    [2019-03-10 21:33:51] Update README links and build instruction #1, GPU Update README links and build instruction #1 AMD Radeon HD 6900 Series (Cayman), i:760 (10
    /256), si:2/2, u:8, cu:24
    [2019-03-10 21:33:51] 1.48/1.75/2 GB
    [2019-03-10 21:33:51] AMD GPU build error with rocm #2: intensity is not a multiple of 'worksize', aut
    o reduce intensity to 760
    [2019-03-10 21:33:51] build error with rocm #2, GPU build error with rocm #2 AMD Radeon HD 6900 Series (Cayman), i:760 (10
    /256), si:2/2, u:8, cu:24
    [2019-03-10 21:33:51] 1.48/1.75/2 GB
    [2019-03-10 21:33:51] AMD GPU macOS 10.13.1: Error when building (GpuContext.h implicit instantiation of undefined template) #3: intensity is not a multiple of 'worksize', aut
    o reduce intensity to 760
    [2019-03-10 21:33:51] macOS 10.13.1: Error when building (GpuContext.h implicit instantiation of undefined template) #3, GPU macOS 10.13.1: Error when building (GpuContext.h implicit instantiation of undefined template) #3 AMD Radeon HD 6900 Series (Cayman), i:760 (10
    /256), si:2/2, u:8, cu:24
    [2019-03-10 21:33:51] 1.48/1.75/2 GB
    [2019-03-10 21:33:52] use pool pool.supportxmr.com:7777 178.63.100.197
    [2019-03-10 21:33:52] new job from pool.supportxmr.com:7777 diff 30000 algo cn/r
    height 1788111
    [2019-03-10 21:33:52] Error CL_BUILD_PROGRAM_FAILURE when calling clBuildProgram
    .
    [2019-03-10 21:33:52] CryptonightR: clBuildProgram returned error CL_BUILD_PROGR
    AM_FAILURE
    [2019-03-10 21:33:52] Error CL_INVALID_KERNEL when calling clSetKernelArg for ke
    rnel 20, argument 0.
    [2019-03-10 21:33:52] Error CL_INVALID_KERNEL when calling clEnqueueNDRangeKerne
    l for kernel 1.
    [2019-03-10 21:33:52] Error CL_BUILD_PROGRAM_FAILURE when calling clBuildProgram
    .
    [2019-03-10 21:33:52] CryptonightR: clBuildProgram returned error CL_BUILD_PROGR
    AM_FAILURE
    [2019-03-10 21:33:52] Error CL_INVALID_KERNEL when calling clSetKernelArg for ke
    rnel 20, argument 0.
    [2019-03-10 21:33:52] Error CL_BUILD_PROGRAM_FAILURE when calling clBuildProgram
    .
    [2019-03-10 21:33:52] CryptonightR: clBuildProgram returned error CL_BUILD_PROGR
    AM_FAILURE
    [2019-03-10 21:33:52] Error CL_INVALID_KERNEL when calling clSetKernelArg for ke
    rnel 20, argument 0.
    [2019-03-10 21:33:52] Error CL_INVALID_KERNEL when calling clEnqueueNDRangeKerne
    l for kernel 1.
    [2019-03-10 21:33:52] Error CL_INVALID_KERNEL when calling clEnqueueNDRangeKerne
    l for kernel 1.
    [2019-03-10 21:33:52] Error CL_BUILD_PROGRAM_FAILURE when calling clBuildProgram
    .
    [2019-03-10 21:33:52] CryptonightR: clBuildProgram returned error CL_BUILD_PROGR
    AM_FAILURE
    [2019-03-10 21:33:52] Error CL_INVALID_KERNEL when calling clSetKernelArg for ke
    rnel 20, argument 0.
    [2019-03-10 21:33:52] Error CL_INVALID_KERNEL when calling clEnqueueNDRangeKerne
    l for kernel 1.
    [2019-03-10 21:33:52] Error CL_INVALID_KERNEL when calling clEnqueueNDRangeKerne
    l for kernel 1.
    [2019-03-10 21:33:52] Error CL_INVALID_KERNEL when calling clEnqueueNDRangeKerne
    l for kernel 1.
    [2019-03-10 21:33:52] Error CL_INVALID_KERNEL when calling clEnqueueNDRangeKerne
    l for kernel 1.
    [2019-03-10 21:33:52] Error CL_INVALID_KERNEL when calling clEnqueueNDRangeKerne
    l for kernel 1.
    [2019-03-10 21:33:52] Error CL_INVALID_KERNEL when calling clEnqueueNDRangeKerne
    l for kernel 1.
    [2019-03-10 21:33:52] Error CL_INVALID_KERNEL when calling clEnqueueNDRangeKerne
    l for kernel 1.
    [2019-03-10 21:33:52] Error CL_INVALID_KERNEL when calling clEnqueueNDRangeKerne
    l for kernel 1.
    [2019-03-10 21:33:52] Error CL_INVALID_KERNEL when calling clEnqueueNDRangeKerne
    l for kernel 1.
    [2019-03-10 21:33:52] Error CL_INVALID_KERNEL when calling clEnqueueNDRangeKerne
    l for kernel 1.
    [2019-03-10 21:33:52] Error CL_INVALID_KERNEL when calling clEnqueueNDRangeKerne
    l for kernel 1.
    [2019-03-10 21:33:52] Error CL_INVALID_KERNEL when calling clEnqueueNDRangeKerne
    l for kernel 1.
    [2019-03-10 21:33:52] Error CL_INVALID_KERNEL when calling clEnqueueNDRangeKerne
    l for kernel 1.
    [2019-03-10 21:33:52] Error CL_INVALID_KERNEL when calling clEnqueueNDRangeKerne
    l for kernel 1.
    [2019-03-10 21:33:52] Error CL_INVALID_KERNEL when calling clEnqueueNDRangeKerne
    l for kernel 1.
    [2019-03-10 21:33:52] Error CL_INVALID_KERNEL when calling clEnqueueNDRangeKerne
    l for kernel 1.
    [2019-03-10 21:33:53] Error CL_INVALID_KERNEL when calling clEnqueueNDRangeKerne
    l for kernel 1.
    [2019-03-10 21:33:53] Error CL_INVALID_KERNEL when calling clEnqueueNDRangeKerne
    l for kernel 1.
    [2019-03-10 21:33:53] Error CL_INVALID_KERNEL when calling clEnqueueNDRangeKerne
    l for kernel 1.
    [2019-03-10 21:33:53] Error CL_INVALID_KERNEL when calling clEnqueueNDRangeKerne
    l for kernel 1.
    [2019-03-10 21:33:53] Error CL_INVALID_KERNEL when calling clEnqueueNDRangeKerne
    l for kernel 1.
    [2019-03-10 21:33:53] Error CL_INVALID_KERNEL when calling clEnqueueNDRangeKerne
    l for kernel 1.
    [2019-03-10 21:33:53] Error CL_INVALID_KERNEL when calling clEnqueueNDRangeKerne
    l for kernel 1.
    [2019-03-10 21:33:53] Error CL_INVALID_KERNEL when calling clEnqueueNDRangeKerne
    l for kernel 1.
    [2019-03-10 21:33:53] Error CL_INVALID_KERNEL when calling clEnqueueNDRangeKerne
    l for kernel 1.
    [2019-03-10 21:33:53] Error CL_INVALID_KERNEL when calling clEnqueueNDRangeKerne
    l for kernel 1.
    [2019-03-10 21:33:53] Error CL_INVALID_KERNEL when calling clEnqueueNDRangeKerne
    l for kernel 1.
    [2019-03-10 21:33:53] Error CL_INVALID_KERNEL when calling clEnqueueNDRangeKerne
    l for kernel 1.
    [2019-03-10 21:33:53] Error CL_INVALID_KERNEL when calling clEnqueueNDRangeKerne
    l for kernel 1.
    [2019-03-10 21:33:53] Error CL_INVALID_KERNEL when calling clEnqueueNDRangeKerne
    l for kernel 1.
    [2019-03-10 21:33:53] Error CL_INVALID_KERNEL when calling clEnqueueNDRangeKerne
    l for kernel 1.
    [2019-03-10 21:33:53] Error CL_INVALID_KERNEL when calling clEnqueueNDRangeKerne
    l for kernel 1.
    [2019-03-10 21:33:53] Error CL_INVALID_KERNEL when calling clEnqueueNDRangeKerne
    l for kernel 1.
    [2019-03-10 21:33:53] Error CL_INVALID_KERNEL when calling clEnqueueNDRangeKerne
    l for kernel 1.
    [2019-03-10 21:33:53] Error CL_INVALID_KERNEL when calling clEnqueueNDRangeKerne
    l for kernel 1.
    [2019-03-10 21:33:53] Error CL_INVALID_KERNEL when calling clEnqueueNDRangeKerne
    l for kernel 1.
    [2019-03-10 21:33:53] Error CL_INVALID_KERNEL when calling clEnqueueNDRangeKerne
    l for kernel 1.
    [2019-03-10 21:33:53] Error CL_INVALID_KERNEL when calling clEnqueueNDRangeKerne
    l for kernel 1.
    [2019-03-10 21:33:53] Error CL_INVALID_KERNEL when calling clEnqueueNDRangeKerne
    l for kernel 1.
    [2019-03-10 21:33:53] Error CL_INVALID_KERNEL when calling clEnqueueNDRangeKerne
    l for kernel 1.
    [2019-03-10 21:33:53] Error CL_INVALID_KERNEL when calling clEnqueueNDRangeKerne
    l for kernel 1.
    [2019-03-10 21:33:53] Error CL_INVALID_KERNEL when calling clEnqueueNDRangeKerne
    l for kernel 1.
    [2019-03-10 21:33:53] Error CL_INVALID_KERNEL when calling clEnqueueNDRangeKerne
    l for kernel 1.
    [2019-03-10 21:33:53] Error CL_INVALID_KERNEL when calling clEnqueueNDRangeKerne
    l for kernel 1.
    [2019-03-10 21:33:54] Error CL_INVALID_KERNEL when calling clEnqueueNDRangeKerne
    l for kernel 1.
    [2019-03-10 21:33:54] Error CL_INVALID_KERNEL when calling clEnqueueNDRangeKerne
    l for kernel 1.
    [2019-03-10 21:33:54] Error CL_INVALID_KERNEL when calling clEnqueueNDRangeKerne
    l for kernel 1.
    [2019-03-10 21:33:54] Error CL_INVALID_KERNEL when calling clEnqueueNDRangeKerne
    l for kernel 1.
    [2019-03-10 21:33:54] Error CL_INVALID_KERNEL when calling clEnqueueNDRangeKerne
    l for kernel 1.
    [2019-03-10 21:33:54] Error CL_INVALID_KERNEL when calling clEnqueueNDRangeKerne
    l for kernel 1.
    [2019-03-10 21:33:54] Error CL_INVALID_KERNEL when calling clEnqueueNDRangeKerne
    l for kernel 1.
    [2019-03-10 21:33:54] Error CL_INVALID_KERNEL when calling clEnqueueNDRangeKerne
    l for kernel 1.
    [2019-03-10 21:33:54] Error CL_INVALID_KERNEL when calling clEnqueueNDRangeKerne
    l for kernel 1.
    [2019-03-10 21:33:54] Error CL_INVALID_KERNEL when calling clEnqueueNDRangeKerne
    l for kernel 1.
    [2019-03-10 21:33:54] Error CL_INVALID_KERNEL when calling clEnqueueNDRangeKerne
    l for kernel 1.
    [2019-03-10 21:33:54] Error CL_INVALID_KERNEL when calling clEnqueueNDRangeKerne
    l for kernel 1.
    [2019-03-10 21:33:54] Error CL_INVALID_KERNEL when calling clEnqueueNDRangeKerne
    l for kernel 1.
    [2019-03-10 21:33:54] Error CL_INVALID_KERNEL when calling clEnqueueNDRangeKerne
    l for kernel 1.
    [2019-03-10 21:33:54] Error CL_INVALID_KERNEL when calling clEnqueueNDRangeKerne
    l for kernel 1.
    [2019-03-10 21:33:54] Error CL_INVALID_KERNEL when calling clEnqueueNDRangeKerne
    l for kernel 1.
    [2019-03-10 21:33:54] Error CL_INVALID_KERNEL when calling clEnqueueNDRangeKerne
    l for kernel 1.
    [2019-03-10 21:33:54] Error CL_INVALID_KERNEL when calling clEnqueueNDRangeKerne
    l for kernel 1.
    [2019-03-10 21:33:54] Error CL_INVALID_KERNEL when calling clEnqueueNDRangeKerne
    l for kernel 1.
    [2019-03-10 21:33:54] Error CL_INVALID_KERNEL when calling clEnqueueNDRangeKerne
    l for kernel 1.
    [2019-03-10 21:33:54] Error CL_INVALID_KERNEL when calling clEnqueueNDRangeKerne
    l for kernel 1.
    [2019-03-10 21:33:54] Error CL_INVALID_KERNEL when calling clEnqueueNDRangeKerne
    l for kernel 1.
    [2019-03-10 21:33:54] Error CL_INVALID_KERNEL when calling clEnqueueNDRangeKerne
    l for kernel 1.
    [2019-03-10 21:33:54] Error CL_INVALID_KERNEL when calling clEnqueueNDRangeKerne
    l for kernel 1.
    [2019-03-10 21:33:54] Error CL_INVALID_KERNEL when calling clEnqueueNDRangeKerne
    l for kernel 1.
    [2019-03-10 21:33:54] Error CL_INVALID_KERNEL when calling clEnqueueNDRangeKerne
    l for kernel 1.
    [2019-03-10 21:33:54] Error CL_INVALID_KERNEL when calling clEnqueueNDRangeKerne

@GrigoryMel
Copy link

Maybe goto has a solution, thanks!

@Nashatyrev
Copy link

Nashatyrev commented Mar 12, 2019

+1 (the same issue with both 2.13 & 2.14 versions)

 * ABOUT        XMRig-AMD/2.13.0 MSVC/2017
 * LIBS         libuv/1.24.1 OpenCL/2.0 microhttpd/0.9.61
 * CPU          Intel(R) Pentium(R) CPU G4400 @ 3.30GHz x64 AES
 * ALGO         cryptonight/r, donate=5%
 * POOL #1      xmr-eu1.nanopool.org:14444 variant r
 * COMMANDS     hashrate, pause, resume
[2019-03-12 15:30:44] compiling code and initializing GPUs. This will take a while...
[2019-03-12 15:30:44] found AMD platform index: 1, name: Advanced Micro Devices, Inc.
[2019-03-12 15:30:44] found OpenCL GPU: Radeon RX 560 Series (Baffin), cu: 16
[2019-03-12 15:30:44] found OpenCL GPU: Radeon RX 560 Series (Baffin), cu: 16
[2019-03-12 15:30:44] #00, GPU #00 Radeon RX 560 Series (Baffin), i:448 (8/256), si:1/2, u:8, cu:16
[2019-03-12 15:30:44]              0.88/3.19/4 GB
[2019-03-12 15:30:45] GPU #0 compiling...
[2019-03-12 15:30:58] GPU #0 compilation completed, elapsed time 13.024s
[2019-03-12 15:30:58] #01, GPU #00 Radeon RX 560 Series (Baffin), i:448 (8/256), si:1/2, u:8, cu:16
[2019-03-12 15:30:58]              0.88/3.19/4 GB
[2019-03-12 15:30:58] #02, GPU #01 Radeon RX 560 Series (Baffin), i:448 (8/256), si:1/2, u:8, cu:16
[2019-03-12 15:30:58]              0.88/3.19/4 GB
[2019-03-12 15:30:58] #03, GPU #01 Radeon RX 560 Series (Baffin), i:448 (8/256), si:1/2, u:8, cu:16
[2019-03-12 15:30:58]              0.88/3.19/4 GB
[2019-03-12 15:30:58] use pool xmr-eu1.nanopool.org:14444  217.182.169.148
[2019-03-12 15:30:58] new job from xmr-eu1.nanopool.org:14444 diff 120001 algo cn/r height 1789086
[2019-03-12 15:31:16] new job from xmr-eu1.nanopool.org:14444 diff 120001 algo cn/r height 1789086
[2019-03-12 15:31:47] speed 10s/60s/15m n/a n/a n/a H/s max n/a H/s
[2019-03-12 15:32:05] Error CL_BUILD_PROGRAM_FAILURE when calling clBuildProgram.
[2019-03-12 15:32:05] CryptonightR: clBuildProgram returned error CL_BUILD_PROGRAM_FAILURE
[2019-03-12 15:32:05] Error CL_BUILD_PROGRAM_FAILURE when calling clBuildProgram.
[2019-03-12 15:32:05] CryptonightR: clBuildProgram returned error CL_BUILD_PROGRAM_FAILURE
[2019-03-12 15:32:06] Error CL_BUILD_PROGRAM_FAILURE when calling clBuildProgram.
[2019-03-12 15:32:06] CryptonightR: clBuildProgram returned error CL_BUILD_PROGRAM_FAILURE
[2019-03-12 15:32:06] Error CL_BUILD_PROGRAM_FAILURE when calling clBuildProgram.
[2019-03-12 15:32:06] CryptonightR: clBuildProgram returned error CL_BUILD_PROGRAM_FAILURE
[2019-03-12 15:32:06] Error CL_BUILD_PROGRAM_FAILURE when calling clBuildProgram.
[2019-03-12 15:32:06] CryptonightR: clBuildProgram returned error CL_BUILD_PROGRAM_FAILURE
[2019-03-12 15:32:07] Error CL_BUILD_PROGRAM_FAILURE when calling clBuildProgram.
[2019-03-12 15:32:07] CryptonightR: clBuildProgram returned error CL_BUILD_PROGRAM_FAILURE
[2019-03-12 15:32:15] new job from xmr-eu1.nanopool.org:14444 diff 120001 algo cn/r height 1789086
[2019-03-12 15:32:47] speed 10s/60s/15m n/a 74.7 n/a H/s max n/a H/s

@xmrig xmrig added the bug label Mar 13, 2019
@xmrig
Copy link
Owner

xmrig commented Mar 13, 2019

For everyone who get error CryptonightR: clBuildProgram returned error CL_BUILD_PROGRAM_FAILURE please update miner to recent version from dev branch. Miner will print build log for this error, it helps understand what exactly wrong.
Thank you.

@CR4DL
Copy link

CR4DL commented Mar 13, 2019

Commit 4a89448 already fixed the error for me (OS X 10.14.3, clang/10.0.0, libuv/1.26.0 OpenCL/1.2 OpenSSL/1.0.2q). Thanks!

@xmrig
Copy link
Owner

xmrig commented Mar 14, 2019

@LeChatNoir69
Copy link
Author

Yeah 👍 Fixed. Thank you

@GrigoryMel
Copy link

ell me why my cards on the old algorithm were given out 760-800 p / s, and on the new 400, and then it does not hold out, the video card hd 6990?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

7 participants