OpenCL error: CL_MEM_OBJECT_ALLOCATION_FAILURE

Keith Myers
Keith Myers
Joined: 11 Feb 11
Posts: 5023
Credit: 18931175004
RAC: 6472156

Use a  gpu_exclude statement

Use a  gpu_exclude statement in your cc_config.xml file to keep that application off the 1050.

 

Mike
Mike
Joined: 26 Dec 20
Posts: 45
Credit: 6247692683
RAC: 10166206

I was doing this with my amd

I was doing this with my amd cpu (and amdgpu PCI) to keep it from trying to run jobs on the ryzan cpu.  The PCI gpu has 20g mem but the client would die trying to run on the internal cpu's video process as well that has only 1/2 g or so of memory?  I used the 'ignore' option as the integral video was id'd as '1' I think and the PCI amdgpu was id '0'.  So in my case I used  '1'  for 'N'. ID's as shown in the boinc-client log or clinfo as well I think.  Then the boinc client showed a line about 'ignoring gpu dev 1 per cc_config' or some such info line.  And it would not crash.

under 'options' in the cc_config -

<ignore_ati_dev>N</ignore_ati_dev>

--- remarks ---

Ignore (don't use) a specific ATI GPU. You can ignore more than one. Requires a client restart.

--------

 The only reason I went with this instead of the 'exclude gpu' was there was only 1 line needed. (lazy)

for more granularity to be able to specify by project running I think you want the exclude option where you can specify all of that.

https://boinc.berkeley.edu/wiki/Client_configuration

Keith Myers
Keith Myers
Joined: 11 Feb 11
Posts: 5023
Credit: 18931175004
RAC: 6472156

Yes you would need to be

Yes you would need to be specific about which app you want to exclude.  Something like this:

<exclude_gpu>
   <url>https://einstein.phys.uwm.edu/</url>
   <device_num>0</device_num>
   <app>hsgamma_FGRPB1G</app>
</exclude_gpu>

Or in your case, change the app to O3AS or whatever the proper app_name is in the client_state.xml for the task type.

And match up the correct gpu number for the 1050 for its position in the Boinc discovery process at startup.

Goes in the <Options> section.

That just keeps the GW app off the 1050 but allows other apps to run on it just fine.

 

Greg_BE
Greg_BE
Joined: 15 Aug 08
Posts: 90
Credit: 107123735
RAC: 32975

I thought I had put that in

I thought I had put that in the cc_config, but I had not copied it from the creation folder to the data folder.

I just need to add the application name now for open sky and I think everything will be in order again.

 

Greg_BE
Greg_BE
Joined: 15 Aug 08
Posts: 90
Credit: 107123735
RAC: 32975

So this is what I ended up

So this is what I ended up with:

<cc_config>
<options>
<exclude_gpu>
<url>http://einstein.phys.uwm.edu/</url>
<device_num>1</device_num>
<app>einstein_O3MDF</app>
</exclude_gpu>
</options>
</cc_config>

The project reports this:

7/28/2023 7:02:25 PM | Einstein@Home | Config: excluded GPU.  Type: all.  App: einstein_O3MDF.  Device: 1

 

Keith Myers
Keith Myers
Joined: 11 Feb 11
Posts: 5023
Credit: 18931175004
RAC: 6472156

Are you sure of the

Are you sure of the app_name?  Wasn't O3MDF the old application tasks that have been deprecated.  I only see O3MD1 and O3AS in that application list now.

Haven't seen any O3MD1 tasks for a month.  I think that app is deprecated too now.  Should be nothing but O3AS gpu tasks for Gravity Wave being sent out now.

 

Ian&Steve C.
Ian&Steve C.
Joined: 19 Jan 20
Posts: 4045
Credit: 48077401052
RAC: 33866068

Yeah it’s O3AS 

Yeah it’s O3AS 

_________________________________________________________________________

Greg_BE
Greg_BE
Joined: 15 Aug 08
Posts: 90
Credit: 107123735
RAC: 32975

Well ok..a few letters to

Well ok..a few letters to change. Thanks

7/28/2023 9:07:04 PM | Einstein@Home | Config: excluded GPU.  Type: all.  App: einstein_O3AS.  Device: 1

 

 

Greg_BE
Greg_BE
Joined: 15 Aug 08
Posts: 90
Credit: 107123735
RAC: 32975

I've ran a few tasks,

I've ran a few tasks, everything seems ok.

Thanks guys.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.