SOLVED: Core 22 crashes at startup

If you think it might be a driver problem, see viewforum.php?f=79

Moderators: Site Moderators, FAHC Science Team

Post Reply
Markus_Laker
Posts: 20
Joined: Sun Dec 01, 2019 11:36 am

SOLVED: Core 22 crashes at startup

Post by Markus_Laker »

Hi! I'm running Fedora 33 with the RPM Fusion NVIDIA drivers and Cuda libraries. I have an Nvidia GeForce GT1030, which isn't going to set the world alight, but I'd like to share what I have. `clinfo' says that I Cuda 11.2 and OpenCL 1.2 are installed. I've added a GPU slot. I found I had to reboot before FAHClient would accept it: before the reboot, it disabled the slot because it couldn't find Cuda or OpenCL 1.2+, but, after the boot, the slot is enabled. F@H has downloaded a WU for the GPU slot. However, Core 22 crashes on startup:

Code: Select all

19:15:34:WU02:FS08:Starting
19:15:34:WU02:FS08:Running FahCore: /usr/bin/FAHCoreWrapper /var/lib/fahclient/cores/cores.foldingathome.org/lin/64bit/22-0.0.13/Core_22.fah/FahCore_22 -dir 02 -suffix 01 -version 706 -lifeline 2685 -checkpoint 15 -opencl-platform 0 -opencl-device 0 -cuda-device 0 -gpu-vendor nvidia -gpu 0 -gpu-usage 100
19:15:34:WU02:FS08:Started FahCore on PID 5459
19:15:34:WU02:FS08:Core PID:5463
19:15:34:WU02:FS08:FahCore 0x22 started
19:15:35:WU02:FS08:0x22:*********************** Log Started 2021-02-23T19:15:34Z ***********************
19:15:35:WU02:FS08:0x22:*************************** Core22 Folding@home Core ***************************
19:15:35:WU02:FS08:0x22:       Core: Core22
19:15:35:WU02:FS08:0x22:       Type: 0x22
19:15:35:WU02:FS08:0x22:    Version: 0.0.13
19:15:35:WU02:FS08:0x22:     Author: Joseph Coffland <[email protected]>
19:15:35:WU02:FS08:0x22:  Copyright: 2020 foldingathome.org
19:15:35:WU02:FS08:0x22:   Homepage: https://foldingathome.org/
19:15:35:WU02:FS08:0x22:       Date: Sep 19 2020
19:15:35:WU02:FS08:0x22:       Time: 01:10:35
19:15:35:WU02:FS08:0x22:   Revision: 571cf95de6de2c592c7c3ed48fcfb2e33e9ea7d3
19:15:35:WU02:FS08:0x22:     Branch: core22-0.0.13
19:15:35:WU02:FS08:0x22:   Compiler: GNU 4.8.2 20140120 (Red Hat 4.8.2-15)
19:15:35:WU02:FS08:0x22:    Options: -std=c++11 -fsigned-char -ffunction-sections -fdata-sections -O3
19:15:35:WU02:FS08:0x22:             -funroll-loops -DOPENMM_GIT_HASH="\"189320d0\""
19:15:35:WU02:FS08:0x22:   Platform: linux2 4.19.76-linuxkit
19:15:35:WU02:FS08:0x22:       Bits: 64
19:15:35:WU02:FS08:0x22:       Mode: Release
19:15:35:WU02:FS08:0x22:Maintainers: John Chodera <[email protected]> and Peter Eastman
19:15:35:WU02:FS08:0x22:             <[email protected]>
19:15:35:WU02:FS08:0x22:       Args: -dir 02 -suffix 01 -version 706 -lifeline 5459 -checkpoint 15
19:15:35:WU02:FS08:0x22:             -opencl-platform 0 -opencl-device 0 -cuda-device 0 -gpu-vendor
19:15:35:WU02:FS08:0x22:             nvidia -gpu 0 -gpu-usage 100
19:15:35:WU02:FS08:0x22:************************************ libFAH ************************************
19:15:35:WU02:FS08:0x22:       Date: Sep 15 2020
19:15:35:WU02:FS08:0x22:       Time: 05:14:43
19:15:35:WU02:FS08:0x22:   Revision: 44301ed97b996b63fe736bb8073f22209cb2b603
19:15:35:WU02:FS08:0x22:     Branch: HEAD
19:15:35:WU02:FS08:0x22:   Compiler: GNU 4.8.2 20140120 (Red Hat 4.8.2-15)
19:15:35:WU02:FS08:0x22:    Options: -std=c++11 -fsigned-char -ffunction-sections -fdata-sections -O3
19:15:35:WU02:FS08:0x22:             -funroll-loops
19:15:35:WU02:FS08:0x22:   Platform: linux2 4.19.76-linuxkit
19:15:35:WU02:FS08:0x22:       Bits: 64
19:15:35:WU02:FS08:0x22:       Mode: Release
19:15:35:WU02:FS08:0x22:************************************ CBang *************************************
19:15:35:WU02:FS08:0x22:       Date: Sep 15 2020
19:15:35:WU02:FS08:0x22:       Time: 05:11:04
19:15:35:WU02:FS08:0x22:   Revision: 33fcfc2b3ed2195a423606a264718e31e6b3903f
19:15:35:WU02:FS08:0x22:     Branch: HEAD
19:15:35:WU02:FS08:0x22:   Compiler: GNU 4.8.2 20140120 (Red Hat 4.8.2-15)
19:15:35:WU02:FS08:0x22:    Options: -std=c++11 -fsigned-char -ffunction-sections -fdata-sections -O3
19:15:35:WU02:FS08:0x22:             -funroll-loops -fPIC
19:15:35:WU02:FS08:0x22:   Platform: linux2 4.19.76-linuxkit
19:15:35:WU02:FS08:0x22:       Bits: 64
19:15:35:WU02:FS08:0x22:       Mode: Release
19:15:35:WU02:FS08:0x22:************************************ System ************************************
19:15:35:WU02:FS08:0x22:        CPU: AMD Ryzen Threadripper 1920X 12-Core Processor
19:15:35:WU02:FS08:0x22:     CPU ID: AuthenticAMD Family 23 Model 1 Stepping 1
19:15:35:WU02:FS08:0x22:       CPUs: 24
19:15:35:WU02:FS08:0x22:     Memory: 62.71GiB
19:15:35:WU02:FS08:0x22:Free Memory: 55.97GiB
19:15:35:WU02:FS08:0x22:    Threads: POSIX_THREADS
19:15:35:WU02:FS08:0x22: OS Version: 5.10
19:15:35:WU02:FS08:0x22:Has Battery: false
19:15:35:WU02:FS08:0x22: On Battery: false
19:15:35:WU02:FS08:0x22: UTC Offset: 0
19:15:35:WU02:FS08:0x22:        PID: 5463
19:15:35:WU02:FS08:0x22:        CWD: /var/lib/fahclient/work
19:15:35:WU02:FS08:0x22:************************************ OpenMM ************************************
19:15:35:WU02:FS08:0x22:   Revision: 189320d0
19:15:35:WU02:FS08:0x22:********************************************************************************
19:15:35:WU02:FS08:0x22:Project: 17800 (Run 65, Clone 133, Gen 44)
19:15:35:WU02:FS08:0x22:Unit: 0x00000000000000000000000000000000
19:15:35:WU02:FS08:0x22:Reading tar file core.xml
19:15:35:WU02:FS08:0x22:Reading tar file integrator.xml.bz2
19:15:35:WU02:FS08:0x22:Reading tar file state.xml.bz2
19:15:35:WU02:FS08:0x22:Reading tar file system.xml.bz2
19:15:35:WU02:FS08:0x22:Digital signatures verified
19:15:35:WU02:FS08:0x22:Folding@home GPU Core22 Folding@home Core
19:15:35:WU02:FS08:0x22:Version 0.0.13
19:15:35:WU02:FS08:FahCore returned: INTERRUPTED (102 = 0x66)
It does this once a minute, without any intervention from me.

After a lot of searching around, I found that the work-around was to comment out the one and only line in /etc/OpenCL/vendors/pocl.icd by preceding it with a hash and a space ("# ").

I don't need any support at this point: I just wanted to put this here as search-engine fodder, all in one place, to make it easier for other people to find. I hope this helps someone.
Top
PantherX
Site Moderator
Posts: 6986
Joined: Wed Dec 23, 2009 9:33 am
Hardware configuration: V7.6.21 -> Multi-purpose 24/7
Windows 10 64-bit
CPU:2/3/4/6 -> Intel i7-6700K
GPU:1 -> Nvidia GTX 1080 Ti
§
Retired:
2x Nvidia GTX 1070
Nvidia GTX 675M
Nvidia GTX 660 Ti
Nvidia GTX 650 SC
Nvidia GTX 260 896 MB SOC
Nvidia 9600GT 1 GB OC
Nvidia 9500M GS
Nvidia 8800GTS 320 MB

Intel Core i7-860
Intel Core i7-3840QM
Intel i3-3240
Intel Core 2 Duo E8200
Intel Core 2 Duo E6550
Intel Core 2 Duo T8300
Intel Pentium E5500
Intel Pentium E5400
Location: Land Of The Long White Cloud
Contact:
Contact PantherX

Re: SOLVED: Core 22 crashes at startup

Post by PantherX »

Thanks for sharing that information here :)

By chance, do you what's unique about your system that required this workaround?
ETA:
Now ↞ Very Soon ↔ Soon ↔ Soon-ish ↔ Not Soon ↠ End Of Time

Welcome To The F@H Support Forum Ӂ Troubleshooting Bad WUs Ӂ Troubleshooting Server Connectivity Issues
Top
bruce
Posts: 20824
Joined: Thu Nov 29, 2007 10:13 pm
Location: So. Cal.

Re: SOLVED: Core 22 crashes at startup

Post by bruce »

I think the answer is here.
RPM Fusion NVIDIA drivers and Cuda libraries.
Markus_Laker has installed the Cuda toolkit with the libraries.

Whatever version he has installed is incompatible with whatever libraries are downloaded and linked with Core_22.

@Markus_Laker: Perhaps this also be solved by uninstalling the CUDA toolkit?
Top
Post Reply

Return to “GPU Projects and FahCores”