pershoot commented 6 years ago

Hi.

Windows: Receiving this (same configs from 2.3.0 and also let it re-create amd). Error CL_INVALID_BUFFER_SIZE when calling clCreateBuffer to create hash scratchpads buffer.

Also windows defender seems to not be happy with the .exe (i had to manually allow it).

Please look in to this.

Thank you.

pershoot commented 6 years ago

This is for Aeon.

psychocrypt commented 6 years ago

reduce the intensity until the error is gone. You must add a exeption for windows defender, someone is using the open source code for bad things, thats the reason for the detection

pershoot commented 6 years ago

I've tried multiple intensity reductions, thread/worksize reduction, etc.; same issue. Configs confirmed working on 2.3.0.

psychocrypt commented 6 years ago

Please fill out the issue template. Add your config files and a full log of the miner output. The output of clinfo, system hardware and OS.

pershoot commented 6 years ago

cpu.txt amd.txt config.txt clinfo.txt

Please provide as much as possible information to reproduce the issue.

Basic information

Type of the CPU: AMD FX-8350.
Type of the GPU (if you try to miner with the GPU): MSI Aero ITX 4G RX 560; Micron.

Compile issues

Which OS do you use?: Windows 10 (17133.1; Insider)

add **all** commands you used and the **full** compile output here

run `cmake -LA .` in the build folder and add the output here

Issue with the execution

Do you compiled the miner by our own?

run `./xmr-stak --version-long` and add the output here

AMD OpenCl issue

  run `clinfo` and add the output here: attached

Stability issue

Is the CPU or GPU overclocked? Both CPU and GPU are overclocked. Previous versions of xmr-stak tested ok.
Is the Main memory of the CPU or GPU undervolted? Nope.

<><><>

[2018-04-03 16:15:49] : Mining coin: aeon [2018-04-03 16:15:49] : Compiling code and initializing GPUs. This will take a while... [2018-04-03 16:15:50] : Device 0 work size 8 / 32. [2018-04-03 16:15:50] : Error CL_INVALID_BUFFER_SIZE when calling clCreateBuffer to create hash scratchpads buffer. [2018-04-03 16:15:50] : WARNING: AMD device not found [2018-04-03 16:15:50] : WARNING: backend AMD disabled. [2018-04-03 16:15:50] : Starting 2x thread, affinity: 0. [2018-04-03 16:15:50] : hwloc: memory pinned [2018-04-03 16:15:50] : Starting 2x thread, affinity: 2. [2018-04-03 16:15:50] : hwloc: memory pinned [2018-04-03 16:15:50] : Starting 2x thread, affinity: 4. [2018-04-03 16:15:50] : hwloc: memory pinned [2018-04-03 16:15:50] : Starting 2x thread, affinity: 6. [2018-04-03 16:15:50] : hwloc: memory pinned

psychocrypt commented 6 years ago

please remive amd.txt and start te miner. Please post the output and the generated amd.txt

pershoot commented 6 years ago

[2018-04-03 16:30:28] : Mining coin: aeon [2018-04-03 16:30:28] : Found AMD platform index id = 0, name = Advanced Micro Devices, Inc. [2018-04-03 16:30:28] : Found OpenCL GPU Baffin. [2018-04-03 16:30:28] : AMD: GPU configuration stored in file 'amd.txt' [2018-04-03 16:30:28] : Compiling code and initializing GPUs. This will take a while... [2018-04-03 16:30:28] : Device 0 work size 8 / 32. [2018-04-03 16:30:28] : Error CL_INVALID_BUFFER_SIZE when calling clCreateBuffer to create hash scratchpads buffer. [2018-04-03 16:30:28] : WARNING: AMD device not found [2018-04-03 16:30:28] : WARNING: backend AMD disabled. [2018-04-03 16:30:28] : Starting 2x thread, affinity: 0. [2018-04-03 16:30:28] : hwloc: memory pinned [2018-04-03 16:30:28] : Starting 2x thread, affinity: 2. [2018-04-03 16:30:28] : hwloc: memory pinned [2018-04-03 16:30:28] : Starting 2x thread, affinity: 4. [2018-04-03 16:30:28] : hwloc: memory pinned [2018-04-03 16:30:28] : Starting 2x thread, affinity: 6. [2018-04-03 16:30:28] : hwloc: memory pinned amd.txt

psychocrypt commented 6 years ago

could you please update youramd app sdk to 3.0 I tested aeon mining on my rx570 again and all works fine.

pershoot commented 6 years ago

I have re-installed AMD-APP-SDK-3.0 and have purged .openclcache; same issue.

psychocrypt commented 6 years ago

please run xmr-stak -V Also please try ro reduce the intensity to 32

danez commented 6 years ago

I have the same issue here with my rig when trying to mine aeon. For now I had to revert to 2.3.0

Basic information

Type of the CPU. Intel Celeron G3930
Type of the GPU (if you try to miner with the GPU). 6x AMD Radeon RX560

Issue with the execution

Do you compiled the miner by our own? Yes

Version: xmr-stak/2.4.1/737383a5/unknown/win/amd-cpu/aeon-cryptonight-monero/20 amd.txt

pershoot commented 6 years ago

Version: xmr-stak/2.4.1/737383a5/master/win/nvidia-amd-cpu/aeon-cryptonight-monero/20

32 intensity (2 threads): [2018-04-03 19:15:43] : Mining coin: aeon [2018-04-03 19:15:43] : Compiling code and initializing GPUs. This will take a while... [2018-04-03 19:15:43] : Device 0 work size 8 / 32. [2018-04-03 19:15:44] : Error CL_INVALID_BUFFER_SIZE when calling clCreateBuffer to create hash scratchpads buffer. [2018-04-03 19:15:44] : WARNING: AMD device not found [2018-04-03 19:15:44] : WARNING: backend AMD disabled. [2018-04-03 19:15:44] : Starting 2x thread, affinity: 0. [2018-04-03 19:15:44] : hwloc: memory pinned [2018-04-03 19:15:44] : Starting 2x thread, affinity: 2. [2018-04-03 19:15:44] : hwloc: memory pinned [2018-04-03 19:15:44] : Starting 2x thread, affinity: 4. [2018-04-03 19:15:44] : hwloc: memory pinned [2018-04-03 19:15:44] : Starting 2x thread, affinity: 6. [2018-04-03 19:15:44] : hwloc: memory pinned

Spudz76 commented 6 years ago

I have gotten this error when forgetting to set the environment var GPU_FORCE_64BIT_PTR=1

danez commented 6 years ago

I tired doing SET GPU_FORCE_64BIT_PTR 1 on windows before launching the miner, but it did not change anything.

Spudz76 commented 6 years ago

It's either SET GPU_FORCE_64BIT_PTR=1 (with the equal no space) or SETX GPU_FORCE_64BIT_PTR 1 (without equal YES space)

I usually stuff all of them into the System env var panel and reboot, to be absolutely sure.

danez commented 6 years ago

I tried all combinations of set and setx but it didn't change anything, it seems that 2.4 is just broken with some cards.

danez commented 6 years ago

Okay seems I figured it out the algo was renamed from aeon to aeon7. So the config from 2.3 is NOT compatible. After changing it in pools.txt it works.

Here is the diff that a pools.txt has when generated with aeon from 2.3 and 2.4

...
 /*
  * Currency to mine. Supported values:
  *
- *    aeon
+ *    aeon7 (use this for Aeon's new PoW)
  *    cryptonight (try this if your coin is not listed)
  *    cryptonight_lite
  *    edollar
  *    electroneum
  *    graft
  *    intense
  *    karbo
  *    monero7 (use this for Monero's new PoW)
  *    sumokoin
  *
  */

-"currency" : "aeon",
+"currency" : "aeon7",

...

I guess xmr-stak should warn about this similar to monero vs monero7 or reject aeon.

postalman commented 6 years ago

Same problem with Vega64 and CN Heavy algo. I asume heavy algo means twice less hashrate? Cause it dont work with old intensity.

BKdilse commented 6 years ago

I saw this today, and I cut my intensity by half to get it working, for sumokoin.

postalman commented 6 years ago

I cut it too for Vega, interesting facts RX480 with two threads got same hashrate as was but Vega not, blockchain drivers dont fix it.

randelsr commented 6 years ago

I know that Sumokoin team has acknowledged that GPUs (in general) are getting 30% less hashrate on Sumokoin.

I'm getting the same issues with mining Sumo on xmr-stak 2.4.2, CL_INVALID_BUFFER_SIZE. I have 8 GB of physical RAM with over 80GB of virtual, with 8 Vega 64s running. Lowering the intensity does resolve this issue, but obviously drastically reduces the hashrate. I wonder if lowering my intensity by ~30% will find a sweet spot.

To add constructive feedback to this thread, is anybody with "unlimited" memory running into these issues? I'm limited by memory & HD space for testing

1337c0d3d00d commented 6 years ago

I get this error too when switching to 'sumokoin' on my VEGA56/64 cards which have 8GB of DDR. However when I switch to the Frontier edition cards which have 16GB it gets past this error. At that point there is another issue as the hash rates are all over the place and much lower than usual.

psychocrypt commented 6 years ago

remive your amd.txt and let the miner create a config. Sumokoin uses now 4MB scratchpad therefore it is in the most cases not possible to use the old intensity.

vegaman64 commented 6 years ago

I see others mining sumo with higher intensity however max I can get is 944 with single or 2 threads getting CL_INVALID_BUFFER_SIZE with higher settings. Is it realy max we can get from Vega cards ~ 1400hs?

vegaman64 commented 6 years ago

I have 8x Vega 64 rig with poor celeron and 4 gb of ram (80Gb virtual memory). Maybe RAM or CPU is the case?

TurkishPower92 commented 6 years ago

yeah admin why giving 944 for sumo i before mining 2010 h :S vega 64

alanclark34 commented 6 years ago

Hi, That's the best config for me: 1xRX 580, 1x R9 290 and 3x RX VEGA 64 Up to intensity 1024 I have "CL_INVALID_BUFFER_SIZE" error.

RX 580: 900h/s // gpu: Ellesmere memory:3920 // compute units: 36 { "index" : 0, "intensity" : 768, "worksize" : 8, "affine_to_cpu" : false, "strided_index" : 1, "mem_chunk" : 2, "comp_mode" : true }, { "index" : 0, "intensity" : 768, "worksize" : 8, "affine_to_cpu" : false, "strided_index" : 1, "mem_chunk" : 2, "comp_mode" : true },

-R9 290 : 530 h/s // gpu: Hawaii memory:3712 // compute units: 40 { "index" : 1, "intensity" : 484, "worksize" : 8, "affine_to_cpu" : false, "strided_index" : 1, "mem_chunk" : 2, "comp_mode" : true }, { "index" : 1, "intensity" : 484, "worksize" : 8, "affine_to_cpu" : false, "strided_index" : 1, "mem_chunk" : 2, "comp_mode" : true },

RX VEGA 64 : 1440 h/s // gpu: gfx900 memory:3920 // compute units: 64 { "index" : 2, "intensity" : 976, "worksize" : 8, "affine_to_cpu" : false, "strided_index" : 2, "mem_chunk" : 16, "comp_mode" : true }, { "index" : 2, "intensity" : 976, "worksize" : 8, "affine_to_cpu" : false, "strided_index" : 2, "mem_chunk" : 16, "comp_mode" : true },

nuigru commented 6 years ago

Why with Vega FE xmr sees only // gpu: gfx900 memory:3920 and not 16GB ?

fireice-uk / xmr-stak

2.4.1 - CL_INVALID_BUFFER_SIZE when calling clCreateBuffer #1290

Basic information

Compile issues

Issue with the execution

AMD OpenCl issue

Stability issue

Basic information

Issue with the execution