Welcome to MilkyWay@home

Posts by neofob

1) Questions and Answers : Unix/Linux : CL_OUT_OF_HOST_MEMORY with AMD RX 6600 XT on Xubuntu 20.04 (Message 73052)
Posted 20 Apr 2022 by neofob
Post:
Is there anyone running Milkyway@Home with AMD RX 6600 XT in Ubuntu 20.04?

I run into a lot of error of computing. It turns out that it's the error "CL_OUT_OF_HOST_MEMORY".

Computer info:
* Xubuntu 20.04, kernel 5.13.19
* AMD OpenCL (ROCM 5.1.1) installed with amdgpu-install from: https://repo.radeon.com/amdgpu-install/22.10.1/ubuntu/focal/
* 32GB of RAM
* GPU: AMD Radeon 6600 XT 8 GB

* I do not have the APU (AMD integrated GPU) enabled in BIOS. Only the discrete Graphics card 6600 XT is used.

Interestingly, Einstein@Home project can run apps that use GPU without errors.
2) Message boards : Number crunching : CL_OUT_OF_HOST_MEMORY with AMD RX 6600 XT on Xbuntu 20.04 (Message 73050)
Posted 20 Apr 2022 by neofob
Post:
I'm not sure if this could cause issues but are you sure ROCm is supported by your GPU? It kind of doesn't look like it by looking at https://docs.amd.com/bundle/ROCm-Getting-Started-Guide-v5.1.1/page/Overview_of_ROCm_Installation.html. What if you uninstall it and try running Separation tasks without ROCm?

Are you able to run both of the Einstein GPU apps (O3AS & FGRPB1G)?


Officially, AMD RX 6600 XT is not supported by ROCm :(

What is other way to get OpenCL for AMD GPU now?

As for Einstein GPU apps. For some reasons, I get mostly O3AS work units. They finish without error.
3) Message boards : Number crunching : CL_OUT_OF_HOST_MEMORY with AMD RX 6600 XT on Xbuntu 20.04 (Message 72802)
Posted 14 Apr 2022 by neofob
Post:
A couple of ideas to investigate: One is driver/driver installation issue. That error kind of sounds like not enough memory can be assigned to run the tasks. Two - your CPU has an integrated GPU in addition to the dedicated one. Could they be interfering with each other? Can the integrated one be disabled (via BIOS maybe)?


Thanks for the ideas. I'll look into the memory & driver issue.

As for the integrated graphics, I think that it is disabled. The command clinfo only shows 6600 XT card.

On another thought, Einstein@Home can run tasks on this GPU just fine.
4) Message boards : Number crunching : CL_OUT_OF_HOST_MEMORY with AMD RX 6600 XT on Xbuntu 20.04 (Message 72770)
Posted 14 Apr 2022 by neofob
Post:
Is there anyone running Milkyway@Home with AMD RX 6600 XT in Ubuntu 20.04?

I run into a lot of error of computing. It turns out that it's the error "CL_OUT_OF_HOST_MEMORY".

Computer info:
* Xubuntu 20.04, kernel 5.13.19
* AMD OpenCL (ROCM 5.1.1) installed with amdgpu-install from: https://repo.radeon.com/amdgpu-install/22.10.1/ubuntu/focal/
* 32GB of RAM
* GPU: AMD Radeon 6600 XT 8 GB

Here is a sample of the work unit with error:
https://milkyway.cs.rpi.edu/milkyway/result.php?resultid=210500363
5) Message boards : Number crunching : AMD FirePro S9150 (Message 68829)
Posted 2 Jun 2019 by neofob
Post:

I use a watercool with Kraken G12 adapter for my S9150. The temperature is around 40s Celcius. It's a good drop from


I thought I might expand on this seeing as lot of users are into water cooling.

You cant got wrong with a closed kit. I used a number of those kits: hybrid adapters for NVidia, water blocks for ATI and kits for CPU. OTOH I built several custom systems w/o a problem, then I got cheap and on my last build I had run out of 1/2- 3/8 soft tubing so I got Ez-Flow from (it seems) Lowes. I failed to notice it was rated at 70f and the output of my dual xeons was closers to 112f and frequently higher. It ran fine for several weeks but I noticed the pump flowmeter was turning slower and slower. System is disassembled and I am waiting for new parts. Fortunately, the electronics are ok, but the pumps and tubing and probably the radiator are shot. Very difficult to lean up the melted vinyl. Details here
https://www.reddit.com/r/watercooling/comments/bugb19/need_fix_to_pump_eventually_stopping_corrosion/


You might want to put a piece of silver coil into your water reservoir. I heard that it will keep the bacteria from growing in your water.
6) Message boards : Number crunching : AMD FirePro S9150 (Message 68823)
Posted 1 Jun 2019 by neofob
Post:
@BeemerBiker: No, I do not use any shim for my S9150. The AMD bracket from my Thermaltake cpu cooler works
great. I need to use zip tie to hold the back plate in place to cool down the memory chips in the back though.
7) Message boards : Number crunching : AMD FirePro S9150 (Message 68809)
Posted 31 May 2019 by neofob
Post:
SOLVED!

So I installed the .deb packages from AMD's downloaded driver (amdgpu-pro-19.10-785425-ubuntu-18.04.tar.xz).


https://linuxconfig.org/install-opencl-for-the-amdgpu-open-source-drivers-on-debian-and-ubuntu

This is such a mess!

----

I use a watercool with Kraken G12 adapter for my S9150. The temperature is around 40s Celcius. It's a good drop from
over 70s with fan cooling.

Is anyone else using Kraken G12 for for this card?
8) Message boards : Number crunching : AMD FirePro S9150 (Message 68750)
Posted 18 May 2019 by neofob
Post:
FYI, I upgraded my 18.30 driver to 19.10 driver in Linux and now
clinfo
does not show any device. :-/
9) Message boards : Number crunching : AMD recently announced Radeon VII with 6.9TFLOPS of FP64 (1:2) for only $699???!!! (Message 68482)
Posted 6 Apr 2019 by neofob
Post:
Yeah, the path to opencl library and others are for Linux.
I've never done this cross-compiling thingy, Linux -> Windows. It's a mess.
I used to cross-compile Linux x86 -> ARM but no more! Farewell to ARM. :)

Goodluck!
10) Message boards : Number crunching : AMD recently announced Radeon VII with 6.9TFLOPS of FP64 (1:2) for only $699???!!! (Message 68471)
Posted 3 Apr 2019 by neofob
Post:
I have a patch ready for Radeon VII. If anyone wants to send me a video card, I'm more than happy to test it out. :)

https://github.com/neofob/milkywayathome_client/commit/c9111eb2dd90865cc2a4451260f6613714610277


I tried to cross-compile this using MinGW and it failed. I have sense checked the git periodically and status remains "failing" for MinGW and "error" for Linux. Are there any plans to continue with getting this to compile? I do not own a Vii I am trying to do this for a couple of friends.

Thanks!


What is your error? Compiling Milkyway at home could be tricky, at least on Linux system.
Here is the steps (you might need to to modify the directory path to your system)
github gist
#!/bin/bash

mkdir /tmp/MW /tmp/MW/build
cd /tmp/MW
git clone --depth=10 https://github.com/Milkyway-at-home/milkywayathome_client
cd milkywayathome_client
git submodule init
git submodule update --recursive
cd ../build
cmake -DBUILD_32=OFF -DSEPARATION=ON -DNBODY=OFF -DSEPARATION_OPENCL=ON \
  -DOPENCL_LIBRARIES=/opt/amdgpu-pro/lib/x86_64-linux-gnu/libOpenCL.so.1 \
  -DOPENCL_INCLUDE_DIRS=/opt/amdgpu-pro/include/CL/ ../milkywayathome_client
make

Note: I updated the Radeon patch with another commit from eyeballing some posts here. So you could try to patch that. Something like this after you git clone/checkout from the official repo.
git remote add neofob https://github.com/neofob/milkywayathome_client
git fetch neofob
git merge neofob/tp-radeon7


Have fun!
11) Message boards : Number crunching : AMD FirePro S9150 (Message 68232)
Posted 8 Mar 2019 by neofob
Post:
Would be nice if @Jake Weiss fixed it in the client code and pushed it out already. He asked someone to put a pull request in and neofob was kind enough to do it and do the fix. So next step is Jake's.


Actually Jake merged my PR. The binary is not pushed out to public for some reason.
The current one 1.46 is built way back in March 2017.
12) Message boards : News : Micromanaging CPU vs GPU Workunit Limits (Message 68231)
Posted 8 Mar 2019 by neofob
Post:
I wonder if there is a way to set the number of cached WU based on the rate of processed WU in the past 1-3 days? This might be better than basing on the number of GPU.
13) Message boards : Number crunching : AMD FirePro S9150 (Message 68177)
Posted 20 Feb 2019 by neofob
Post:
@BeemerBiker: There is thread somewhere about Nvidia Titan V running MH. In that thread, the author mentions about each WU uses about 1.5GB of VRAM. So you can run about 6 WUs on a S9100 (12GB) or 8-10 WUs on S9150 (16GB).

As for compiling, here is roughly how I do it in Linux:
https://gist.github.com/neofob/8a73e2f44787541c11c0445763953950
14) Message boards : Number crunching : AMD FirePro S9150 (Message 68175)
Posted 20 Feb 2019 by neofob
Post:
So is the MilkyWay code fixed to include "Hawaii" based GPUs now? Or is this still a manual fix?

Thanks,
blue


It's in the public github source repo but not in the public binary release yet.

I compile and overwrite the current installed binary with this latest one.
15) Message boards : Number crunching : AMD recently announced Radeon VII with 6.9TFLOPS of FP64 (1:2) for only $699???!!! (Message 68159)
Posted 15 Feb 2019 by neofob
Post:
Look like this card needs some serious cooling if you want to run 24/7.
Maybe a Kraken G12 adapter and a Thermaltake Water 3.0 would be sufficient.
16) Message boards : Number crunching : W9100 (Message 68131)
Posted 10 Feb 2019 by neofob
Post:
I run 4 concurrently.
17) Message boards : Number crunching : AMD recently announced Radeon VII with 6.9TFLOPS of FP64 (1:2) for only $699???!!! (Message 68129)
Posted 10 Feb 2019 by neofob
Post:
I have a patch ready for Radeon VII. If anyone wants to send me a video card, I'm more than happy to test it out. :)

https://github.com/neofob/milkywayathome_client/commit/c9111eb2dd90865cc2a4451260f6613714610277
18) Message boards : Number crunching : W9100 (Message 68128)
Posted 10 Feb 2019 by neofob
Post:
Not likely. Each WU consumes about 1.5GB of VRAM.

https://www.reddit.com/r/gridcoin/comments/7ytw2n/my_quest_to_use_an_nvidia_titan_v_for_boinc_titan/

Have fun with your W9100!
19) Message boards : Number crunching : W9100 (Message 68123)
Posted 9 Feb 2019 by neofob
Post:
W9100 is similar to S9100, S9150..etc.

So you should get good result with 5-6 WU at the same time.
https://milkyway.cs.rpi.edu/milkyway/forum_thread.php?id=4268&postid=67331
20) Message boards : Number crunching : AMD FirePro S9150 (Message 67929)
Posted 7 Dec 2018 by neofob
Post:
FYI, here is a snippet of the output from the newly merged code from github, sample from 82465335

Platform 0 information:
  Name:       AMD Accelerated Parallel Processing
  Version:    OpenCL 2.1 AMD-APP (2671.3)
  Vendor:     Advanced Micro Devices, Inc.
  Extensions: cl_khr_icd cl_amd_event_callback cl_amd_offline_devices 
  Profile:    FULL_PROFILE
Using device 0 on platform 0
Found 1 CL device
Device 'Hawaii' (Advanced Micro Devices, Inc.:0x1002) (CL_DEVICE_TYPE_GPU)
Board: AMD Radeon FirePro W9100
Driver version:      2671.3
Version:             OpenCL 1.2 AMD-APP (2671.3)
Compute capability:  0.0
Max compute units:   44
Clock frequency:     900 Mhz
Global mem size:     16790622208
Local mem size:      32768
Max const buf size:  4244635648
Double extension:    cl_khr_fp64
Build log:
--------------------------------------------------------------------------------
/tmp/OCL16522T3.cl:183:72: warning: unknown attribute 'max_constant_size' ignored
                            __constant real* _ap_consts __attribute__((max_constant_size(18 * sizeof(real)))),
                                                                       ^
/tmp/OCL16522T3.cl:185:62: warning: unknown attribute 'max_constant_size' ignored
                            __constant SC* sc __attribute__((max_constant_size(NSTREAM * sizeof(SC)))),
                                                             ^
/tmp/OCL16522T3.cl:186:67: warning: unknown attribute 'max_constant_size' ignored
                            __constant real* sg_dx __attribute__((max_constant_size(256 * sizeof(real)))),
                                                                  ^
3 warnings generated.

--------------------------------------------------------------------------------
Estimated AMD GPU GFLOP/s: 5069 SP GFLOP/s, 2534 DP FLOP/s
Using a target frequency of 60.0
Using a block size of 11264 with 49 blocks/chunk
Using clWaitForEvents() for polling (mode -1)
Range:          { nu_steps = 320, mu_steps = 800, r_steps = 700 }
Iteration area: 560000
Chunk estimate: 1
Num chunks:     2
Chunk size:     551936
Added area:     543872
Effective area: 1103872
Initial wait:   0 ms
Integration time: 15.889514 s. Average time per iteration = 49.654731 ms
Integral 0 time = 16.441450 s
Running likelihood with 84044 stars
Likelihood time = 1.241216 s



Build steps:

mkdir /tmp/MW /tmp/MW/build
cd /tmp
git clone https://github.com/Milkyway-at-home/milkywayathome_client
cd milkywayathome_client
git submodule init
git submodule update --recursive
cd ../build
cmake -DBUILD_32=OFF -DSEPARATION=ON -DNBODY=OFF -DSEPARATION_OPENCL=ON \
  -DOPENCL_LIBRARIES=/opt/amdgpu-pro/lib/x86_64-linux-gnu/libOpenCL.so.1 \
  -DOPENCL_INCLUDE_DIRS=/opt/amdgpu-pro/include/CL/ ../milkywayathome_client
make


Next 20

©2024 Astroinformatics Group