Folding Forum

Even using...
sudo systemctl restart fah-client

...it doesn't move beyond 1%
...any input appreciated...
ubuntu 24.04.3

If this is the wrong place for this post, please feel free to move it.

--Tom


18:25:27:I3:WU384:Loading work unit 384 with ID IM7tFpkRS-cyYsajZOq-iq3qASOaQ00IJXaZGlyFmwk
18:25:28:I3:WU384:Started FahCore on PID 3890
18:25:28:I1:WU384:*********************** Log Started 2025-12-28T18:25:28Z ***********************
18:25:28:I1:WU384:*************************** Core27 Folding@home Core ***************************
18:25:28:I1:WU384: Core: Core27
18:25:28:I1:WU384: Type: 0x27
18:25:28:I1:WU384: Version: 8.2.1
18:25:28:I1:WU384: Author: Joseph Coffland <joseph@cauldrondevelopment.com>
18:25:28:I1:WU384: Copyright: 2022 foldingathome.org
18:25:28:I1:WU384: Homepage: https://foldingathome.org/
18:25:28:I1:WU384: Date: Mar 27 2025
18:25:28:I1:WU384: Time: 04:28:24
18:25:28:I1:WU384: Revision: 84019442387121f2bed4ed52e05c53b7b7b52a72
18:25:28:I1:WU384: Branch: HEAD
18:25:28:I1:WU384: Compiler: GNU 7.5.0
18:25:28:I1:WU384: Options: -faligned-new -std=c++14 -fsigned-char -ffunction-sections
18:25:28:I1:WU384: -fdata-sections -O3 -funroll-loops -fno-pie
18:25:28:I1:WU384: -DOPENMM_VERSION="\"8.2.0\""
18:25:28:I1:WU384: Platform: linux 6.8.0-1021-azure
18:25:28:I1:WU384: Bits: 64
18:25:28:I1:WU384: Mode: Release
18:25:28:I1:WU384:Maintainers: John Chodera <john.chodera@choderalab.org> and Peter Eastman
18:25:28:I1:WU384: <peastman@stanford.edu>
18:25:28:I1:WU384: Args: -dir IM7tFpkRS-cyYsajZOq-iq3qASOaQ00IJXaZGlyFmwk -suffix 01
18:25:28:I1:WU384: -version 8.5.5 -lifeline 3884 -gpu-uuid
18:25:28:I1:WU384: e7c57ed1-177c-5578-6057-dbec69f54ef5 -gpu-platform cuda -gpu-vendor
18:25:28:I1:WU384: nvidia -opencl-platform 0 -opencl-device 0 -cuda-platform 0
18:25:28:I1:WU384: -cuda-device 0 -gpu 0
18:25:28:I1:WU384:************************************ libFAH ************************************
18:25:28:I1:WU384: Date: Mar 27 2025
18:25:28:I1:WU384: Time: 04:23:18
18:25:28:I1:WU384: Revision: c7d2824a47eb025fa8cda8968c7a5e971585d90c
18:25:28:I1:WU384: Branch: HEAD
18:25:28:I1:WU384: Compiler: GNU 7.5.0
18:25:28:I1:WU384: Options: -faligned-new -std=c++11 -fsigned-char -ffunction-sections
18:25:28:I1:WU384: -fdata-sections -O3 -funroll-loops -fno-pie
18:25:28:I1:WU384: Platform: linux 6.8.0-1021-azure
18:25:28:I1:WU384: Bits: 64
18:25:28:I1:WU384: Mode: Release
18:25:28:I1:WU384:************************************ CBang *************************************
18:25:28:I1:WU384: Version: 1.7.2
18:25:28:I1:WU384: Author: Joseph Coffland <joseph@cauldrondevelopment.com>
18:25:28:I1:WU384: Org: Cauldron Development LLC
18:25:28:I1:WU384: Copyright: Cauldron Development LLC, 2003-2024
18:25:28:I1:WU384: Homepage: https://cauldrondevelopment.com/
18:25:28:I1:WU384: License: LGPL-2.1-or-later
18:25:28:I1:WU384: Date: Mar 27 2025
18:25:28:I1:WU384: Time: 04:22:53
18:25:28:I1:WU384: Revision: f1cd4c791e8c40a35dcfeab3ab85d910949cc0cb
18:25:28:I1:WU384: Branch: HEAD
18:25:28:I1:WU384: Compiler: GNU 7.5.0
18:25:28:I1:WU384: Options: -faligned-new -std=c++11 -fsigned-char -ffunction-sections
18:25:28:I1:WU384: -fdata-sections -O3 -funroll-loops -fno-pie -fPIC
18:25:28:I1:WU384: Platform: linux 6.8.0-1021-azure
18:25:28:I1:WU384: Bits: 64
18:25:28:I1:WU384: Mode: Release
18:25:28:I1:WU384:************************************ System ************************************
18:25:28:I1:WU384: CPU: Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz
18:25:28:I1:WU384: CPU ID: GenuineIntel Family 6 Model 15 Stepping 11
18:25:28:I1:WU384: CPUs: 4
18:25:28:I1:WU384: Memory: 7.75GiB
18:25:28:I1:WU384:Free Memory: 3.90GiB
18:25:28:I1:WU384: OS Version: 6.14
18:25:28:I1:WU384:Has Battery: false
18:25:28:I1:WU384: On Battery: false
18:25:28:I1:WU384: Hostname: Bigblack
18:25:28:I1:WU384: UTC Offset: -5
18:25:28:I1:WU384: PID: 3890
18:25:28:I1:WU384: CWD: /var/lib/fah-client/work
18:25:28:I1:WU384: Exec: /var/lib/fah-client/cores/openmm-core-27/centos-7.9.2009-64bit/release/fahcore-27-centos-7.9.2009-64bit-release-8.2.1/FahCore_27
18:25:28:I1:WU384:************************************ OpenMM ************************************
18:25:28:I1:WU384: Version: 8.2.0
18:25:28:I1:WU384:********************************************************************************
18:25:28:I1:WU384:Project: 18262 (Run 109, Clone 3, Gen 267)
18:25:28:I1:WU384:Digital signatures verified
18:25:28:I1:WU384:Folding@home GPU Core27 Folding@home Core
18:25:28:I1:WU384:Version 8.2.1
18:25:28:I1:WU384: GPU info: Platform: OpenCL: NVIDIA CUDA
18:25:28:I1:WU384: GPU info: PlatformIndex: 0
18:25:28:I1:WU384: GPU info: Device: NVIDIA GeForce RTX 3070
18:25:28:I1:WU384: GPU info: DeviceIndex: 0
18:25:28:I1:WU384: GPU info: Vendor: 0x10de
18:25:28:I1:WU384: GPU info: PCI: 01:00:00
18:25:28:I1:WU384: GPU info: Compute: 3.0
18:25:28:I1:WU384: GPU info: Driver: 580.95
18:25:28:I1:WU384: GPU info: GPU: true
18:25:28:I1:WU384: GPU info: Platform: CUDA
18:25:28:I1:WU384: GPU info: PlatformIndex: 0
18:25:28:I1:WU384: GPU info: Device: NVIDIA GeForce RTX 3070
18:25:28:I1:WU384: GPU info: DeviceIndex: 0
18:25:28:I1:WU384: GPU info: Vendor: 0x10de
18:25:28:I1:WU384: GPU info: PCI: 01:00:00
18:25:28:I1:WU384: GPU info: Compute: 8.6
18:25:28:I1:WU384: GPU info: Driver: 13.0
18:25:28:I1:WU384: GPU info: GPU: true
18:25:28:I1:WU384: Checkpoint write interval: 12500 steps (5%) [20 total]
18:25:28:I1:WU384: JSON viewer frame write interval: 2500 steps (1%) [100 total]
18:25:28:I1:WU384: XTC frame write interval: 5000 steps (2%) [50 total]
18:25:28:I1:WU384: TRR frame write interval: disabled
18:25:28:I1:WU384: Global context and integrator variables write interval: disabled
18:25:28:I1:WU384:There are 3 platforms available.
18:25:28:I1:WU384:Platform 0: Reference
18:25:28:I1:WU384:Platform 1: OpenCL
18:25:28:I1:WU384: opencl-device 0 specified
18:25:28:I1:WU384:Platform 2: CUDA
18:25:28:I1:WU384: cuda-device 0 specified
18:27:14:I1:WU384:Attempting to create CUDA context:
18:27:14:I1:WU384: Configuring platform CUDA
18:58:43:I1:WU384: Using CUDA on CUDA Platform and gpu 0
18:58:43:I1:WU384: GPU info: Platform: CUDA
18:58:43:I1:WU384: GPU info: PlatformIndex: 0
18:58:43:I1:WU384: GPU info: Device: NVIDIA GeForce RTX 3070
18:58:43:I1:WU384: GPU info: DeviceIndex: 0
18:58:43:I1:WU384: GPU info: Vendor: 0x10de
18:58:43:I1:WU384: GPU info: PCI: 01:00:00
18:58:43:I1:WU384: GPU info: Compute: 8.6
18:58:43:I1:WU384: GPU info: Driver: 13.0
18:58:43:I1:WU384: GPU info: GPU: true
18:58:43:I1:WU384:Completed 0 out of 250000 steps (0%)

,,,and doesn't seem to move any farther...

How much time did you wait ?
On a 3070 those 182xx WUs can need a few minutes to initialize

(in the past)

...hours...

21 minutes to configure CUDA at startup seems long, but you use a Q6600 to feed the GPU
After the 0% line, did you get the first successful checkpoint completed and if yes, at which timestamp?

...this is what appeared next...

18:58:43:I1:WU384:Completed 0 out of 250000 steps (0%)
19:08:45:I1:WU384:Watchdog triggered, requesting soft shutdown down
19:13:24:I1:WU384:Checkpoint completed at step 0
19:13:25:I1:WU384:Folding@home Core Shutdown: INTERRUPTED
19:13:39:I1:WU384:Core returned INTERRUPTED (102)
19:13:39:I3:WU384:Started FahCore on PID 5298
19:13:39:I1:WU384:*********************** Log Started 2025-12-28T19:13:39Z *
.
.
.
19:13:39:I1:WU384:Platform 2: CUDA
19:13:39:I1:WU384: cuda-device 0 specified
19:15:21:I1:WU384:Attempting to create CUDA context:
19:15:21:I1:WU384: Configuring platform CUDA
19:46:23:I1:WU384: Using CUDA on CUDA Platform and gpu 0
19:46:23:I1:WU384: GPU info: Platform: CUDA
19:46:23:I1:WU384: GPU info: PlatformIndex: 0
19:46:23:I1:WU384: GPU info: Device: NVIDIA GeForce RTX 3070
19:46:23:I1:WU384: GPU info: DeviceIndex: 0
19:46:23:I1:WU384: GPU info: Vendor: 0x10de
19:46:23:I1:WU384: GPU info: PCI: 01:00:00
19:46:23:I1:WU384: GPU info: Compute: 8.6
19:46:23:I1:WU384: GPU info: Driver: 13.0
19:46:23:I1:WU384: GPU info: GPU: true
19:46:26:I1:WU384:Completed 0 out of 250000 steps (0%)
19:56:27:I1:WU384:Watchdog triggered, requesting soft shutdown down
20:01:04:I1:WU384:Checkpoint completed at step 0
20:01:05:I1:WU384:Folding@home Core Shutdown: INTERRUPTED
20:01:19:I1:WU384:Core returned INTERRUPTED (102)
20:01:19:I3:WU384:Started FahCore on PID 6592
20:01:19:I1:WU384:*********************** Log Started 2025-12-28T20:01:19Z **
.
.
...and so on...

I am not certain, but I did come across mention that the newer GPU folding cores may require SSE4 support on the CPU which your Q6600 does not have. It only supports up to SSE3 and SSSE3. I will see if I can find some verification of that.

I remember reading this somewhere, too, but in that instance client throws an error

Yes, Q6600 doesn't have SSE4.2 which is required for GPU folding. Please disable your GPU in your client on this system.

In Intel world, you need at least a first generation i7 (Nehalem).

"...<a> Q6600 doesn't have SSE4.2 which is required for GPU folding. Please disable your GPU in your client on this system..."

Noted...I'll swap the card into a "newer" rig.

Thank you all...

--Tom

toTOW wrote: ↑Mon Dec 29, 2025 1:50 pm Yes, Q6600 doesn't have SSE4.2 which is required for GPU folding. Please disable your GPU in your client on this system.

Well, it's not "required"
My Q9650 is still GPU folding , without SSE4.2 ... Sure, "only" on a GTX 1660 Super , but it's "folding" .
And it folded a couple 18262 this week.


Maybe there's an heat issue that triggered the watchdog ?

JWhy wrote: ↑Mon Dec 29, 2025 2:12 pm My Q9650 is still GPU folding , without SSE4.2

Your Q9650 may not support SSE4.2, but it is listed as supporting SSE4.1. That may be enough for all current Core_27 folding, or you might run into an error condition if some WUs cause a call to use one of the instructions added with SSE4.2.

SSE4.2 just adds several new instructions on already existing SSE4 and SSE4.1. It is possible to get away with things working on SSE4.1 capable CPU. q6600 does not even support SSE4. SSE4+SSE4.1+SSE4.2 is quite an extensive instruction set, when combined