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

GPU Slot For Intel iGPU Downloads CPU WU #1434

Open
PantherX opened this issue Apr 29, 2020 · 2 comments
Open

GPU Slot For Intel iGPU Downloads CPU WU #1434

PantherX opened this issue Apr 29, 2020 · 2 comments
Labels
1.Type - Defect Reported issue is a defect. 3.Component - FAHClient Reported issue relates to FAHClient. 3.Component - Servers (AS/WS/CS) Reported issue relates to F@H Server Infrastructure. 4.OS - All Reported issue occurs on all supported OS platforms.

Comments

@PantherX
Copy link
Contributor

Using V7.6.9 (Trimmed Log):

11:27:26:             OS: Windows 10 Home
11:27:26:        OS Arch: AMD64
11:27:26:           GPUs: 2
11:27:26:          GPU 0: Bus:0 Slot:2 Func:0 INTEL:1 [xxx]
11:27:26:          GPU 1: Bus:1 Slot:0 Func:0 NVIDIA:5 GP107M [GeForce GTX 1050 Ti Max-Q]
11:27:26:  CUDA Device 0: Platform:0 Device:0 Bus:1 Slot:0 Compute:6.1 Driver:10.2
11:27:26:OpenCL Device 0: Platform:0 Device:0 Bus:1 Slot:0 Compute:1.2 Driver:442.59
11:27:26:OpenCL Device 1: Platform:1 Device:0 Bus:NA Slot:NA Compute:2.1 Driver:26.20
11:27:26:  <!-- Folding Slots -->
11:27:26:  <slot id='0' type='CPU'/>
11:27:26:  <slot id='1' type='GPU'/>
11:27:26:Enabled folding slot 00: READY cpu:10
11:27:26:Enabled folding slot 01: READY gpu:0:[xxx]
11:27:27:WU00:FS00:Connecting to 65.254.110.245:80
11:27:27:WU01:FS01:Connecting to 65.254.110.245:80
11:28:00:WU01:FS01:Download complete
11:28:00:WU01:FS01:Received Unit: id:01 state:DOWNLOAD error:NO_ERROR project:13851 run:0 clone:38694 gen:62 core:0xa7 unit:0x0000004e287234c95e787a95fb3b45cf
11:28:00:WU01:FS01:Starting
11:28:00:WU01:FS01:Running FahCore: "C:\Program Files (x86)\FAHClient/FAHCoreWrapper.exe" C:\Users\Admin\AppData\Roaming\FAHClient\cores/cores.foldingathome.org/v7/win/64bit/avx/Core_a7.fah/FahCore_a7.exe -dir 01 -suffix 01 -version 706 -lifeline 14764 -checkpoint 15 -gpu-vendor intel -opencl-platform 1 -opencl-device 0 -gpu 0
11:28:01:WU01:FS01:Started FahCore on PID 7952
11:28:02:WU01:FS01:Core PID:2480
11:28:02:WU01:FS01:FahCore 0xa7 started
11:30:27:WU00:FS00:Download complete
11:30:27:WU00:FS00:Received Unit: id:00 state:DOWNLOAD error:NO_ERROR project:16416 run:0 clone:248 gen:100 core:0xa7 unit:0x0000007196880e6e5e8255e2a977a58b
11:30:27:WU00:FS00:Starting
11:30:27:WARNING:WU00:FS00:AS lowered CPUs from 10 to 9
11:30:27:WU00:FS00:Running FahCore: "C:\Program Files (x86)\FAHClient/FAHCoreWrapper.exe" C:\Users\Admin\AppData\Roaming\FAHClient\cores/cores.foldingathome.org/v7/win/64bit/avx/Core_a7.fah/FahCore_a7.exe -dir 00 -suffix 01 -version 706 -lifeline 14764 -checkpoint 15 -np 9
11:30:27:WU00:FS00:Started FahCore on PID 4428

This seems to happen when the system has a dGPU and an iGPU in the same system and drivers are installed for both GPUs. The client correctly identified them but doesn't set-up the slots correctly. There are two issues here:

  1. The AS/WS providing a CPU WU to a GPU Slot
  2. The GPU Slot running a CPU WU.

Issue 2 Potential Solution
Ensure that the GPU Slot can't run FahCore_a4 and FahCore_a7.
Ensure that the CPU Slot can't run FahCore_21 and FahCore22.
If we start with a blacklist, new versions of the FahCore will not require a new release of the client and the names can change without any issues. The next version can update the blacklist. Since new FahCores are not frequently released, it seems like a good sanity check IMO.

Details are in this post: https://foldingforum.org/viewtopic.php?p=330796#p330796

@PantherX PantherX added the 3.Component - FAHClient Reported issue relates to FAHClient. label Apr 29, 2020
@shorttack shorttack added 3.Component - API Reported issue relates to 3rd party APIs. 1.Type - Defect Reported issue is a defect. labels May 2, 2020
@PantherX
Copy link
Contributor Author

It seems that if a new dGPU was added manually to the GPUs.txt file on the local system, it produces the similar result, a FahCore_a7 WU running on the GPU Slot: https://foldingforum.org/viewtopic.php?f=83&t=35325

@bb30994
Copy link

bb30994 commented May 22, 2020

Manual changes to the local GPUs.txt are prohibited -- but folks still try to hack FAH. Whatever the local cached copy says is checked by the server and that master copy should always take precedence. Inasmuch as no Intel GPUs are currently supported, it becomes a question of what the server is supposed to do when a device (that from FAH's perspective) doesn't exist requests a new WU assignment.

  1. IF DEVICE=[a supported GPU] THEN Assign a GPU WU. Condition = false so the server handled this correctly.
  2. ELSE IF DEVICE=[CPU:n] THEN Assign a CPU WU. This condition should never happen here. Since it is ambiguous it was incorrectly handled.
  3. OTHERWISE issue a message message "No WUs can be assigned to your hardware configuration."

The third condition needs to be added to the code.

@PantherX PantherX added 4.OS - All Reported issue occurs on all supported OS platforms. 3.Component - Servers (AS/WS/CS) Reported issue relates to F@H Server Infrastructure. and removed 3.Component - API Reported issue relates to 3rd party APIs. labels Jun 7, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
1.Type - Defect Reported issue is a defect. 3.Component - FAHClient Reported issue relates to FAHClient. 3.Component - Servers (AS/WS/CS) Reported issue relates to F@H Server Infrastructure. 4.OS - All Reported issue occurs on all supported OS platforms.
Projects
None yet
Development

No branches or pull requests

3 participants