(102 = 0x66) using sci-biology/foldingathome:Gentoo
Moderators: Site Moderators, FAHC Science Team
Re: (102 = 0x66) using sci-biology/foldingathome:Gentoo
OK Joe, fair enough. It's a semantic argument not related to my problem, anyhow.
I'll wait around and see if axs can help out, but maybe he'll suggest that I move this to the bugtracker anyhow, as here might not be the best place to get help.
I'll wait around and see if axs can help out, but maybe he'll suggest that I move this to the bugtracker anyhow, as here might not be the best place to get help.
Re: (102 = 0x66) using sci-biology/foldingathome:Gentoo
The content of that thread gives us permission to make folding@home available in Gentoo's package repository, but it's up to Gentoo to pick up any pieces and make sure things work as expected -- Folding@home would need to be the authors of the ebuild in order for it to be "officially supported" by them.ThunderRd wrote:And incidentally, I believe this is a 'supported' install method, according to special permissions issued to the Gentoo project by Pande: viewtopic.php?f=16&t=22524&p=242433&hilit=gentoo+folding#p242020
Now back to the issue at hand -- Gento's package is set up to run folding@home as a system daemon, rather than as a specific individual user. Generally on a Gentoo system, if you want to install something like this that will be used just by one user, you would install it into HOME instead of using a system package. That doesn't mean it has to be this way of course, and I'll certainly look into getting it to work properly when run as a user instead of just as a system daemon. In terms of the error itself, I'll try and reproduce it and see if I can help sort it out for you (HOMEdir install or not).
Re: (102 = 0x66) using sci-biology/foldingathome:Gentoo
Any suggestions would be great, axs. If I can't run it as a normal user, how is it supposed to be run as a daemon? Should I be starting it from .xinitrc or something like that?
And thank you for taking the time to check in here, it's appreciated. It's nearly 10PM here, so I'll check back tomorrow. Let me know if there is any more information you need about the problem.
And thank you for taking the time to check in here, it's appreciated. It's nearly 10PM here, so I'll check back tomorrow. Let me know if there is any more information you need about the problem.
Re: (102 = 0x66) using sci-biology/foldingathome:Gentoo
OK so a bit of information:
Gentoo's package does install folding@home to /opt/foldingathome , as generally /opt is the best location for self-contained prebuilt binaries. That directory and everything in it is installed with ownership of foldingathome:nogroup and 755 permissions (ie world executable). The system's init script launches FAHClient as user foldingathome and with /opt/foldingathome as the current directory.
While trying to reproduce your issue, I couldn't. I successfully ran FAHClient as my own user simply by:
1 - emerge foldingathome
2 - mkdir ${HOME}/randomsubdir && cd ${HOME}/randomsubdir
3 - /opt/foldingathome/FAHClient --configure # since it was an empty dir and I didn't have a config file to use anyhow
4 - /opt/foldingathome/FAHClient
...and FAHClient seems to have had no issues at all starting up, grabbing a dataset to work on, and starting to fold:
....so given that everything seems to work just fine as a new installation and new configuration, I'm going to take a guess that whatever this issue is that you're having has to do with the configuration and/or data files made by the old foldingathome client not being entirely compatible with 7.4.4. Either way, it doesn't seem to be a Gentoo-specific issue.
Where are your foldingathome support files located (config.xml, working directory, etc)? Maybe we can get to the bottom of this by sorting that out. In my specific test case, it seems FAHClient (by default at least) expects to have full rights in whatever the current directory is when you launch it.
Mod edit: changed Quote tags to Code on the log file
Gentoo's package does install folding@home to /opt/foldingathome , as generally /opt is the best location for self-contained prebuilt binaries. That directory and everything in it is installed with ownership of foldingathome:nogroup and 755 permissions (ie world executable). The system's init script launches FAHClient as user foldingathome and with /opt/foldingathome as the current directory.
While trying to reproduce your issue, I couldn't. I successfully ran FAHClient as my own user simply by:
1 - emerge foldingathome
2 - mkdir ${HOME}/randomsubdir && cd ${HOME}/randomsubdir
3 - /opt/foldingathome/FAHClient --configure # since it was an empty dir and I didn't have a config file to use anyhow
4 - /opt/foldingathome/FAHClient
...and FAHClient seems to have had no issues at all starting up, grabbing a dataset to work on, and starting to fold:
Code: Select all
14:11:15:************************* Folding@home Client *************************
14:11:15: Website: http://folding.stanford.edu/
14:11:15: Copyright: (c) 2009-2014 Stanford University
14:11:15: Author: Joseph Coffland <joseph@cauldrondevelopment.com>
14:11:15: Args:
14:11:15: Config: /home/ian/gfd/config.xml
14:11:15:******************************** Build ********************************
14:11:15: Version: 7.4.4
14:11:15: Date: Mar 4 2014
14:11:15: Time: 12:01:17
14:11:15: SVN Rev: 4130
14:11:15: Branch: fah/trunk/client
14:11:15: Compiler: GNU 4.1.2 20080704 (Red Hat 4.1.2-46)
14:11:15: Options: -std=gnu++98 -O3 -funroll-loops -mfpmath=sse -ffast-math
14:11:15: -fno-unsafe-math-optimizations -msse2
14:11:15: Platform: linux2 2.6.18-164.11.1.el5
14:11:15: Bits: 64
14:11:15: Mode: Release
14:11:15:******************************* System ********************************
14:11:15: CPU: Intel(R) Core(TM) i7-2760QM CPU @ 2.40GHz
14:11:15: CPU ID: GenuineIntel Family 6 Model 42 Stepping 7
14:11:15: CPUs: 8
14:11:15: Memory: 3.75GiB
14:11:15:Free Memory: 465.83MiB
14:11:15: Threads: POSIX_THREADS
14:11:15: OS Version: 3.14
14:11:15:Has Battery: true
14:11:15: On Battery: false
14:11:15: UTC Offset: -4
14:11:15: PID: 6657
14:11:15: CWD: /home/ian/gfd
14:11:15: OS: Linux 3.14.31-gentoo x86_64
14:11:15: OS Arch: AMD64
14:11:15: GPUs: 1
14:11:15: GPU 0: NVIDIA:2 GF108 [Quadro 1000M]
14:11:15: CUDA: Not detected
14:11:15:***********************************************************************
14:11:15:<config>
14:11:15: <!-- Folding Slot Configuration -->
14:11:15: <gpu v='false'/>
14:11:15:
14:11:15: <!-- Folding Slots -->
14:11:15: <slot id='0' type='CPU'/>
14:11:15:</config>
14:11:15:Trying to access database...
14:11:15:Successfully acquired database lock
14:11:15:Enabled folding slot 00: READY cpu:4
14:11:15:WU00:FS00:Starting
14:11:15:WU00:FS00:Running FahCore: /opt/foldingathome/FAHCoreWrapper /home/ian/gfd/cores/web.stanford.edu/~pande/Linux/AMD64/Core_a4.fah/FahCore_a4 -dir 00 -suffix 01 -version 704 -lifeline 6657 -checkpoint 15 -np 4
14:11:15:WU00:FS00:Started FahCore on PID 6670
14:11:15:WU00:FS00:Core PID:6675
14:11:15:WU00:FS00:FahCore 0xa4 started
14:11:16:WU00:FS00:0xa4:
14:11:16:WU00:FS00:0xa4:*------------------------------*
14:11:16:WU00:FS00:0xa4:Folding@Home Gromacs GB Core
14:11:16:WU00:FS00:0xa4:Version 2.27 (Dec. 15, 2010)
14:11:16:WU00:FS00:0xa4:
14:11:16:WU00:FS00:0xa4:Preparing to commence simulation
14:11:16:WU00:FS00:0xa4:- Looking at optimizations...
14:11:16:WU00:FS00:0xa4:- Files status OK
14:11:16:WU00:FS00:0xa4:- Expanded 628592 -> 868080 (decompressed 138.0 percent)
14:11:16:WU00:FS00:0xa4:Called DecompressByteArray: compressed_data_size=628592 data_size=868080, decompressed_data_size=868080 diff=0
14:11:16:WU00:FS00:0xa4:- Digital signature verified
14:11:16:WU00:FS00:0xa4:
14:11:16:WU00:FS00:0xa4:Project: 7812 (Run 2529, Clone 0, Gen 215)
14:11:16:WU00:FS00:0xa4:
14:11:16:WU00:FS00:0xa4:Assembly optimizations on if available.
14:11:16:WU00:FS00:0xa4:Entering M.D.
14:11:22:WU00:FS00:0xa4:Completed 0 out of 500000 steps (0%)
Reading file ./work/00/wudata_01.tpr, VERSION 4.5.3 (single precision)
Reading file ./work/00/wudata_01.tpr, VERSION 4.5.3 (single precision)
14:13:15:WU00:FS00:0xa4:Completed 5000 out of 500000 steps (1%)
14:15:19:WU00:FS00:0xa4:Completed 10000 out of 500000 steps (2%)
Where are your foldingathome support files located (config.xml, working directory, etc)? Maybe we can get to the bottom of this by sorting that out. In my specific test case, it seems FAHClient (by default at least) expects to have full rights in whatever the current directory is when you launch it.
Mod edit: changed Quote tags to Code on the log file
Re: (102 = 0x66) using sci-biology/foldingathome:Gentoo
Well, I removed all traces of previous install and started over. Created a new config.xml and ran from a home directory location . The client runs as regular user properly without further ownership/permission changes [the owner:group and perms are as you said they would be], but alas produces the same error message as before, the core failing to engage. Incidentally, I rebooted into both a 3.18 and 3.19 kernel with identical results, as well:
Code: Select all
>>> Installing (1 of 1) sci-biology/foldingathome-7.4.4::gentoo
* checking 5 files for package collisions
>>> Merging sci-biology/foldingathome-7.4.4 to /
--- /opt/
>>> /opt/foldingathome/
>>> /opt/foldingathome/initfolding
>>> /opt/foldingathome/FAHClient
>>> /opt/foldingathome/FAHCoreWrapper
--- /etc/
--- /etc/conf.d/
>>> /etc/conf.d/foldingathome
--- /etc/init.d/
>>> /etc/init.d/foldingathome
* To run Folding@home in the background at boot (with openrc):
* rc-update add foldingathome default
*
* No configuration found -- please run //opt/foldingathome/initfolding or
* emerge --config foldingathome-7.4.4 to configure your client and edit
* //etc/conf.d/foldingathome for options
*
* The original author encourages you to acquire a username and join team 36480.
* http://folding.stanford.edu/English/Download#ntoc2
*
>>> sci-biology/foldingathome-7.4.4 merged.
>>> Recording sci-biology/foldingathome in "world" favorites file...
* Messages for package sci-biology/foldingathome-7.4.4:
* No configuration found -- please run //opt/foldingathome/initfolding or
* emerge --config foldingathome-7.4.4 to configure your client and edit
* //etc/conf.d/foldingathome for options
>>> Auto-cleaning packages...
>>> No outdated packages were found on your system.
* GNU info directory index is up-to-date.
root@Q6600: ~# exit
logout
thunderrd@Q6600:~$ mkdir FAH7
thunderrd@Q6600:~$ cd FAH7
thunderrd@Q6600:~/FAH7$ /opt/foldingathome/FAHClient --configure
User name [Anonymous]: ThunderRd
Team number [0]: 45
Passkey: XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
Enable SMP [true]:
Enable GPU [true]: false
Name of configuration file [config.xml]:
thunderrd@Q6600:~/FAH7$ /opt/foldingathome/FAHClient
15:03:13:************************* Folding@home Client *************************
15:03:13: Website: http://folding.stanford.edu/
15:03:13: Copyright: (c) 2009-2014 Stanford University
15:03:13: Author: Joseph Coffland <joseph@cauldrondevelopment.com>
15:03:13: Args:
15:03:13: Config: /home/thunderrd/FAH7/config.xml
15:03:13:******************************** Build ********************************
15:03:13: Version: 7.4.4
15:03:13: Date: Mar 4 2014
15:03:13: Time: 12:01:17
15:03:13: SVN Rev: 4130
15:03:13: Branch: fah/trunk/client
15:03:13: Compiler: GNU 4.1.2 20080704 (Red Hat 4.1.2-46)
15:03:13: Options: -std=gnu++98 -O3 -funroll-loops -mfpmath=sse -ffast-math
15:03:13: -fno-unsafe-math-optimizations -msse2
15:03:13: Platform: linux2 2.6.18-164.11.1.el5
15:03:13: Bits: 64
15:03:13: Mode: Release
15:03:13:******************************* System ********************************
15:03:13: CPU: Intel(R) Core(TM)2 Extreme CPU X9650 @ 3.00GHz
15:03:13: CPU ID: GenuineIntel Family 6 Model 23 Stepping 6
15:03:13: CPUs: 4
15:03:13: Memory: 3.86GiB
15:03:13:Free Memory: 197.10MiB
15:03:13: Threads: POSIX_THREADS
15:03:13: OS Version: 4.0
15:03:13:Has Battery: false
15:03:13: On Battery: false
15:03:13: UTC Offset: 7
15:03:13: PID: 16822
15:03:13: CWD: /home/thunderrd/FAH7
15:03:13: OS: Linux 4.0.0-ck x86_64
15:03:13: OS Arch: AMD64
15:03:13: GPUs: 1
15:03:13: GPU 0: NVIDIA:1 G94 [GeForce 9600 GT]
15:03:13: CUDA: 1.1
15:03:13:CUDA Driver: 6050
15:03:13:***********************************************************************
15:03:13:<config>
15:03:13: <!-- Folding Slot Configuration -->
15:03:13: <gpu v='false'/>
15:03:13:
15:03:13: <!-- User Information -->
15:03:13: <passkey v='********************************'/>
15:03:13: <team v='45'/>
15:03:13: <user v='ThunderRd'/>
15:03:13:
15:03:13: <!-- Folding Slots -->
15:03:13:</config>
15:03:13:Trying to access database...
15:03:13:Successfully acquired database lock
15:03:13:FS00:Set client configured
15:03:13:Enabled folding slot 00: READY cpu:3
15:03:13:WU00:FS00:Connecting to 171.67.108.200:8080
15:03:15:WU00:FS00:Connecting to 171.67.108.200:8080
15:03:17:WU00:FS00:Assigned to work server 155.247.166.219
15:03:17:WU00:FS00:Requesting new work unit for slot 00: READY cpu:3 from 155.247.166.219
15:03:17:WU00:FS00:Connecting to 155.247.166.219:8080
15:03:18:WU00:FS00:Downloading 116.98KiB
15:03:19:WU00:FS00:Download complete
15:03:19:WU00:FS00:Received Unit: id:00 state:DOWNLOAD error:NO_ERROR project:6395 run:56 clone:20 gen:37 core:0xa4 unit:0x0000002c0002894b5462c761d71fc65a
15:03:19:WU00:FS00:Downloading core from http://web.stanford.edu/~pande/Linux/AMD64/Core_a4.fah
15:03:19:WU00:FS00:Connecting to web.stanford.edu:80
15:03:20:WU00:FS00:FahCore a4: Downloading 2.56MiB
15:03:26:WU00:FS00:FahCore a4: 41.52%
15:03:32:WU00:FS00:FahCore a4: 90.36%
15:03:33:WU00:FS00:FahCore a4: Download complete
15:03:33:WU00:FS00:Valid core signature
15:03:33:WU00:FS00:Unpacked 5.98MiB to cores/web.stanford.edu/~pande/Linux/AMD64/Core_a4.fah/FahCore_a4
15:03:33:WU00:FS00:Starting
15:03:33:WU00:FS00:Running FahCore: /opt/foldingathome/FAHCoreWrapper /home/thunderrd/FAH7/cores/web.stanford.edu/~pande/Linux/AMD64/Core_a4.fah/FahCore_a4 -dir 00 -suffix 01 -version 704 -lifeline 16822 -checkpoint 15 -np 3
15:03:33:WU00:FS00:Started FahCore on PID 16839
15:03:33:WU00:FS00:Core PID:16843
15:03:33:WU00:FS00:FahCore 0xa4 started
15:03:33:WU00:FS00:0xa4:
15:03:33:WU00:FS00:0xa4:*------------------------------*
15:03:33:WU00:FS00:0xa4:Folding@Home Gromacs GB Core
15:03:33:WU00:FS00:0xa4:Version 2.27 (Dec. 15, 2010)
15:03:33:WU00:FS00:0xa4:
15:03:33:WU00:FS00:0xa4:Preparing to commence simulation
15:03:33:WU00:FS00:0xa4:- Looking at optimizations...
15:03:33:WU00:FS00:0xa4:- Created dyn
15:03:33:WU00:FS00:0xa4:- Files status OK
15:03:33:WU00:FS00:0xa4:- Expanded 119271 -> 270148 (decompressed 226.4 percent)
15:03:33:WU00:FS00:0xa4:Called DecompressByteArray: compressed_data_size=119271 data_size=270148, decompressed_data_size=270148 diff=0
15:03:33:WU00:FS00:0xa4:- Digital signature verified
15:03:33:WU00:FS00:0xa4:
15:03:33:WU00:FS00:0xa4:Project: 6395 (Run 56, Clone 20, Gen 37)
15:03:33:WU00:FS00:0xa4:
15:03:33:WU00:FS00:0xa4:Assembly optimizations on if available.
15:03:33:WU00:FS00:0xa4:Entering M.D.
15:03:39:WU00:FS00:FahCore returned: INTERRUPTED (102 = 0x66)
15:03:40:WU00:FS00:Starting
15:03:40:WU00:FS00:Running FahCore: /opt/foldingathome/FAHCoreWrapper /home/thunderrd/FAH7/cores/web.stanford.edu/~pande/Linux/AMD64/Core_a4.fah/FahCore_a4 -dir 00 -suffix 01 -version 704 -lifeline 16822 -checkpoint 15 -np 3
15:03:40:WU00:FS00:Started FahCore on PID 16852
15:03:40:WU00:FS00:Core PID:16856
15:03:40:WU00:FS00:FahCore 0xa4 started
15:03:40:WU00:FS00:0xa4:
15:03:40:WU00:FS00:0xa4:*------------------------------*
15:03:40:WU00:FS00:0xa4:Folding@Home Gromacs GB Core
15:03:40:WU00:FS00:0xa4:Version 2.27 (Dec. 15, 2010)
15:03:40:WU00:FS00:0xa4:
15:03:40:WU00:FS00:0xa4:Preparing to commence simulation
15:03:40:WU00:FS00:0xa4:- Ensuring status. Please wait.
15:03:49:WU00:FS00:0xa4:- Looking at optimizations...
15:03:49:WU00:FS00:0xa4:- Working with standard loops on this execution.
15:03:49:WU00:FS00:0xa4:- Previous termination of core was improper.
15:03:49:WU00:FS00:0xa4:- Files status OK
15:03:49:WU00:FS00:0xa4:- Expanded 119271 -> 270148 (decompressed 226.4 percent)
15:03:49:WU00:FS00:0xa4:Called DecompressByteArray: compressed_data_size=119271 data_size=270148, decompressed_data_size=270148 diff=0
15:03:49:WU00:FS00:0xa4:- Digital signature verified
15:03:49:WU00:FS00:0xa4:
15:03:49:WU00:FS00:0xa4:Project: 6395 (Run 56, Clone 20, Gen 37)
15:03:49:WU00:FS00:0xa4:
15:03:49:WU00:FS00:0xa4:Entering M.D.
15:03:56:WU00:FS00:FahCore returned: INTERRUPTED (102 = 0x66)
^C15:04:04:Caught signal SIGINT(2) on PID 16822
15:04:04:Exiting, please wait. . .
15:04:05:Saving configuration to config.xml
15:04:05:<config>
15:04:05: <!-- Folding Slot Configuration -->
15:04:05: <gpu v='false'/>
15:04:05:
15:04:05: <!-- User Information -->
15:04:05: <passkey v='********************************'/>
15:04:05: <team v='45'/>
15:04:05: <user v='ThunderRd'/>
15:04:05:
15:04:05: <!-- Folding Slots -->
15:04:05: <slot id='0' type='CPU'/>
15:04:05:</config>
15:04:05:Clean exit
Re: (102 = 0x66) using sci-biology/foldingathome:Gentoo
I don't know if this matters or not, but I'm running Gentoo stable with a 3.14 series kernel and glibc-2.20, everything built with gcc-4.8.4 and linked with ld.bfd. I'm also using -march=corei7 (for my i7 processor) rather than -march=native, so my code (edit: i mean binaries, not code) might be a bit more generic than an -march=native user.
I noticed FahCore_a4 is a statically-linked 64bit binary built under a 2.6.15 kernel.. Although unlikely (since your 6.x series client worked fine), it's possible that there's some sort of incompatibility between FahCore_a4, FAHCoreWrapper, and the newness of your kernel/libc/toolchain. Debugging this, of course, will likely be rather difficult and potentially reverse-engineeringy which means you'd be breaking the terms of use.
If would really help if someone in the know could inform us what error 102 = 0x66 actually means. If this could be confirmed as a filesystem access error of some sort at least then we would know we're looking in the right direction.
I noticed FahCore_a4 is a statically-linked 64bit binary built under a 2.6.15 kernel.. Although unlikely (since your 6.x series client worked fine), it's possible that there's some sort of incompatibility between FahCore_a4, FAHCoreWrapper, and the newness of your kernel/libc/toolchain. Debugging this, of course, will likely be rather difficult and potentially reverse-engineeringy which means you'd be breaking the terms of use.
If would really help if someone in the know could inform us what error 102 = 0x66 actually means. If this could be confirmed as a filesystem access error of some sort at least then we would know we're looking in the right direction.
Last edited by axs on Fri Apr 24, 2015 4:12 pm, edited 1 time in total.
Re: (102 = 0x66) using sci-biology/foldingathome:Gentoo
The way it's set up in Gentoo is that the daemon is started and stopped via openrc, specifically /etc/init.d/foldingathome -- just add it to your default runlevel and it'll auto-start at boot.ThunderRd wrote:Any suggestions would be great, axs. If I can't run it as a normal user, how is it supposed to be run as a daemon? Should I be starting it from .xinitrc or something like that?
Everything (config.xml included) gets stored in /opt/foldingathome/ , which is also the working directory for FAHClient. The init script takes care of running FAHClient as the 'foldingathome' user and ensuring it's operating within the /opt/foldingathome/ directory. Also FYI (going back to your first post), the 'initfolding' scripts is a gentooism, which simply wraps FAHClient --configure to make sure that it gets run as the right user and within the /opt/foldingathome/ directory.
Re: (102 = 0x66) using sci-biology/foldingathome:Gentoo
I've seen no concrete meanings for the 0x66 error either in my searches. Bruce had responded in another old thread that INTERRUPTED was referring to the client being paused in some way, but that's not the case here. I'm guessing it is something like the code 66 listed on ths page in the wiki: http://fahwiki.net/index.php/CoreStatus_codes
I could build a 3.14 kernel with the existing toolchain to try it out, but am not *really* willing to downgrade gcc and rebuild the whole system for a test.
FWIW, my --info:
And yes, I caught the emerge message that says to start the client as a daemon by adding it to the rc default level, so I understand now. Currently, though, all the working files and directories are in ~/FAH7, which is the directory I created after reinstalling the package, and running it from there.
I could build a 3.14 kernel with the existing toolchain to try it out, but am not *really* willing to downgrade gcc and rebuild the whole system for a test.
FWIW, my --info:
Code: Select all
root@Q6600: ~# emerge --info
Portage 2.2.17 (python 3.4.3-final-0, default/linux/amd64/13.0/desktop, gcc-4.9.2, glibc-2.20-r2, 4.0.0-ck x86_64)
=================================================================
System uname: Linux-4.0.0-ck-x86_64-Intel-R-_Core-TM-2_Extreme_CPU_X9650_@_3.00GHz-with-gentoo-2.2
KiB Mem: 4046924 total, 1924712 free
KiB Swap: 1060860 total, 1060860 free
Timestamp of repository gentoo: Fri, 24 Apr 2015 14:45:01 +0000
sh bash 4.3_p33-r2
ld GNU ld (Gentoo 2.25 p1.0) 2.25
app-shells/bash: 4.3_p33-r2::gentoo
dev-java/java-config: 2.2.0::gentoo
dev-lang/perl: 5.20.2::gentoo
dev-lang/python: 2.7.9-r2::gentoo, 3.3.5-r1::gentoo, 3.4.3::gentoo
dev-util/cmake: 3.1.0::gentoo
dev-util/pkgconfig: 0.28-r2::gentoo
sys-apps/baselayout: 2.2::gentoo
sys-apps/openrc: 0.13.11::gentoo
sys-apps/sandbox: 2.6-r1::gentoo
sys-devel/autoconf: 2.13::gentoo, 2.69-r1::gentoo
sys-devel/automake: 1.11.6-r1::gentoo, 1.13.4::gentoo, 1.15::gentoo
sys-devel/binutils: 2.25::gentoo
sys-devel/gcc: 4.9.2::gentoo
sys-devel/gcc-config: 1.8::gentoo
sys-devel/libtool: 2.4.6-r1::gentoo
sys-devel/make: 4.1-r1::gentoo
sys-kernel/linux-headers: 4.0::gentoo (virtual/os-headers)
sys-libs/glibc: 2.20-r2::gentoo
Repositories:
gentoo
location: /mnt/ext4_STORAGE/usr/portage
sync-type: rsync
sync-uri: rsync://mirrors.kernel.org/gentoo-portage
priority: -1000
BZ-overlay
location: /mnt/ext4_STORAGE/usr/local/portage
masters: gentoo
priority: 0
ACCEPT_KEYWORDS="amd64 ~amd64"
ACCEPT_LICENSE="* -@EULA"
CBUILD="x86_64-pc-linux-gnu"
CFLAGS="-march=native -O2 -pipe"
CHOST="x86_64-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/share/gnupg/qualified.txt"
CONFIG_PROTECT_MASK="/etc/ca-certificates.conf /etc/dconf /etc/env.d /etc/fonts/fonts.conf /etc/gconf /etc/gentoo-release /etc/revdep-rebuild /etc/sandbox.d /etc/terminfo"
CXXFLAGS="-march=native -O2 -pipe"
DISTDIR="/mnt/ext4_STORAGE/usr/portage/distfiles"
EMERGE_DEFAULT_OPTS="--quiet-build=n"
FCFLAGS="-O2 -pipe"
FEATURES="assume-digests binpkg-logs collision-protect config-protect-if-modified distlocks ebuild-locks fixlafiles merge-sync news parallel-fetch preserve-libs protect-owned sandbox sfperms strict unknown-features-warn unmerge-logs unmerge-orphans userfetch userpriv usersandbox usersync"
FFLAGS="-O2 -pipe"
GENTOO_MIRRORS="http://mirrors.xmu.edu.cn/gentoo http://gentoo.aditsu.net:8000/ http://mirrors.stuhome.net/gentoo/"
LANG="en_US.UTF-8"
LDFLAGS="-Wl,-O1 -Wl,--as-needed"
MAKEOPTS="-j5"
PKGDIR="/mnt/ext4_STORAGE/usr/portage/packages"
PORTAGE_CONFIGROOT="/"
PORTAGE_RSYNC_EXTRA_OPTS="--verbose --progress --exclude-from=/etc/portage/rsync_excludes"
PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --omit-dir-times --compress --force --whole-file --delete --stats --human-readable --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages"
PORTAGE_TMPDIR="/var/tmp"
USE="X a52 aac acl acpi alsa amd64 branding bzip2 cairo cdda cdr cli consolekit cracklib crypt cups cxx dbus device-mapper directfb dri dts dvd dvdr emboss encode exif fam ffmpeg firefox flac fortran gdbm gif glamor gnutls gpm gtk iconv ipv6 jack jpeg lcms ldap libnotify mad mmx mmxext mng modules mp3 mp4 mpeg multilib ncurses nls nptl offensive ogg opengl openmp pam pango pcre pdf png policykit ppds python qt3support qt4 readline samba sdl session spell sse sse2 ssh ssl startup-notification svg tcpd threads tiff truetype udev udisks unicode usb uuid vdpau vorbis wxwidgets x264 xcb xcomposite xfce xml xv xvid zlib" ABI_X86="32 64" ALSA_CARDS="ca0106" CALLIGRA_FEATURES="kexi words flow plan sheets stage tables krita karbon braindump author" CAMERAS="ptp2" COLLECTD_PLUGINS="df interface irq load memory rrdtool swap syslog" CPU_FLAGS_X86="mmx mmxext sse sse2 sse3 sse4_1 ssse3" ELIBC="glibc" GPSD_PROTOCOLS="ashtech aivdm earthmate evermore fv18 garmin garmintxt gpsclock itrax mtk3301 nmea ntrip navcom oceanserver oldstyle oncore rtcm104v2 rtcm104v3 sirf superstar2 timing tsip tripmate tnt ublox ubx" INPUT_DEVICES="evdev" KERNEL="linux" LCD_DEVICES="bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses text" LIBREOFFICE_EXTENSIONS="presenter-console presenter-minimizer" OFFICE_IMPLEMENTATION="libreoffice" PHP_TARGETS="php5-5" PYTHON_SINGLE_TARGET="python2_7" PYTHON_TARGETS="python2_7 python3_3 python3_4" RUBY_TARGETS="ruby21" USERLAND="GNU" VIDEO_CARDS="nvidia" XFCE_PLUGINS="trash" XTABLES_ADDONS="quota2 psd pknock lscan length2 ipv4options ipset ipp2p iface geoip fuzzy condition tee tarpit sysrq steal rawnat logmark ipmark dhcpmac delude chaos account"
USE_PYTHON="2.7 3.3"
Unset: CPPFLAGS, CTARGET, INSTALL_MASK, LC_ALL, PORTAGE_BUNZIP2_COMMAND, PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS
-
- Site Admin
- Posts: 7939
- Joined: Tue Apr 21, 2009 4:41 pm
- Hardware configuration: Mac Pro 2.8 quad 12 GB smp4
MacBook Pro 2.9 i7 8 GB smp2 - Location: W. MA
Re: (102 = 0x66) using sci-biology/foldingathome:Gentoo
FahCore returned: INTERRUPTED (102 = 0x66) is a normal termination message from a folding core, it just indicates the core received a signal to terminate. As an example, here is an extract from one of my logs from where I paused the folding slot:
What is abnormal is for the core to be stopped immediately after starting. That could be from an error detected by the FAHCoreWrapper process or somewhere else in the client. The logged error does not indicate the source of the termination signal, just that the core received one. You might find something in the core log file kept in the work directory for the WU, but I am not sure what all gets logged there.
Code: Select all
18:28:09:FS00:Shutting core down
18:28:13:WU00:FS00:0xa4:Client no longer detected. Shutting down core.
18:28:13:WU00:FS00:0xa4:
18:28:13:WU00:FS00:0xa4:Folding@home Core Shutdown: CLIENT_DIED
18:28:13:WU00:FS00:FahCore returned: INTERRUPTED (102 = 0x66)
iMac 2.8 i7 12 GB smp8, Mac Pro 2.8 quad 12 GB smp6
MacBook Pro 2.9 i7 8 GB smp3
Re: (102 = 0x66) using sci-biology/foldingathome:Gentoo
I looked at the log you mentioned and there's nothing of interest there. It terminates after 'Entering M.D.' and says nothing else after that.
Re: (102 = 0x66) using sci-biology/foldingathome:Gentoo
FYI - I found a volunteer running a system-wide ~amd64 Gentoo with 4.0 kernel and all that jazz. They had no issues running foldingathome with the reproduction settings I used a few posts back. Whatever the issue is, it seems to be specific to your system somehow. :/
Re: (102 = 0x66) using sci-biology/foldingathome:Gentoo
OK, thanks for that. I'll have to keep digging.axs wrote:FYI - I found a volunteer running a system-wide ~amd64 Gentoo with 4.0 kernel and all that jazz.
Re: (102 = 0x66) using sci-biology/foldingathome:Gentoo
Interestingly enough, I revisited this problem after a month and discovered that some kernel .config setting seemed to be the issue. I don't know which setting it is, and I plan to eliminate them one-by one if necessary, but if someone is knowledgeable about which kernel option might be the problem related to the folding client, it would give me a starting point.
Here is a diff of the old, non-working .config and the new, working one:
Here is a diff of the old, non-working .config and the new, working one:
Code: Select all
thunderrd@Q6600:~/FAH7$ diff --suppress-common-lines .config-bad .config-works
87,88c87,88
< CONFIG_FHANDLE=y
< # CONFIG_USELIB is not set
---
> # CONFIG_FHANDLE is not set
> CONFIG_USELIB=y
124c124
< CONFIG_NO_HZ=y
---
> # CONFIG_NO_HZ is not set
358,359c358
< CONFIG_IOSF_MBI=m
< # CONFIG_IOSF_MBI_DEBUG is not set
---
> # CONFIG_IOSF_MBI is not set
425c424
< # CONFIG_X86_VSYSCALL_EMULATION is not set
---
> CONFIG_X86_VSYSCALL_EMULATION=y
683a683
> CONFIG_NF_LOG_COMMON=m
693,695c693,695
< # CONFIG_NF_LOG_ARP is not set
< # CONFIG_NF_LOG_IPV4 is not set
< # CONFIG_NF_REJECT_IPV4 is not set
---
> CONFIG_NF_LOG_ARP=m
> CONFIG_NF_LOG_IPV4=m
> CONFIG_NF_REJECT_IPV4=m
746a747
> # CONFIG_RFKILL_REGULATOR is not set
801,803c802
< CONFIG_BLK_DEV_LOOP=m
< CONFIG_BLK_DEV_LOOP_MIN_COUNT=8
< # CONFIG_BLK_DEV_CRYPTOLOOP is not set
---
> # CONFIG_BLK_DEV_LOOP is not set
809,811c808
< CONFIG_BLK_DEV_RAM=m
< CONFIG_BLK_DEV_RAM_COUNT=16
< CONFIG_BLK_DEV_RAM_SIZE=4096
---
> # CONFIG_BLK_DEV_RAM is not set
1019c1016
< CONFIG_BLK_DEV_DM=m
---
> CONFIG_BLK_DEV_DM=y
1138c1135,1142
< # CONFIG_USB_NET_DRIVERS is not set
---
> CONFIG_USB_NET_DRIVERS=y
> # CONFIG_USB_CATC is not set
> # CONFIG_USB_KAWETH is not set
> # CONFIG_USB_PEGASUS is not set
> # CONFIG_USB_RTL8150 is not set
> # CONFIG_USB_RTL8152 is not set
> # CONFIG_USB_USBNET is not set
> # CONFIG_USB_IPHETH is not set
1203c1207
< # CONFIG_MOUSE_PS2_FOCALTECH is not set
---
> CONFIG_MOUSE_PS2_FOCALTECH=y
1291c1295
< # CONFIG_ACPI_I2C_OPREGION is not set
---
> CONFIG_ACPI_I2C_OPREGION=y
1579,1580c1583
< CONFIG_X86_PKG_TEMP_THERMAL=m
< # CONFIG_INTEL_SOC_DTS_THERMAL is not set
---
> CONFIG_X86_PKG_TEMP_THERMAL=y
1677c1680,1707
< # CONFIG_REGULATOR is not set
---
> CONFIG_REGULATOR=y
> # CONFIG_REGULATOR_DEBUG is not set
> # CONFIG_REGULATOR_FIXED_VOLTAGE is not set
> # CONFIG_REGULATOR_VIRTUAL_CONSUMER is not set
> # CONFIG_REGULATOR_USERSPACE_CONSUMER is not set
> # CONFIG_REGULATOR_ACT8865 is not set
> # CONFIG_REGULATOR_AD5398 is not set
> # CONFIG_REGULATOR_DA9210 is not set
> # CONFIG_REGULATOR_DA9211 is not set
> # CONFIG_REGULATOR_FAN53555 is not set
> # CONFIG_REGULATOR_GPIO is not set
> # CONFIG_REGULATOR_ISL9305 is not set
> # CONFIG_REGULATOR_ISL6271A is not set
> # CONFIG_REGULATOR_LP3971 is not set
> # CONFIG_REGULATOR_LP3972 is not set
> # CONFIG_REGULATOR_LP872X is not set
> # CONFIG_REGULATOR_LP8755 is not set
> # CONFIG_REGULATOR_LTC3589 is not set
> # CONFIG_REGULATOR_MAX1586 is not set
> # CONFIG_REGULATOR_MAX8649 is not set
> # CONFIG_REGULATOR_MAX8660 is not set
> # CONFIG_REGULATOR_MAX8952 is not set
> # CONFIG_REGULATOR_MAX8973 is not set
> # CONFIG_REGULATOR_PFUZE100 is not set
> # CONFIG_REGULATOR_TPS51632 is not set
> # CONFIG_REGULATOR_TPS62360 is not set
> # CONFIG_REGULATOR_TPS65023 is not set
> # CONFIG_REGULATOR_TPS6507X is not set
2285d2314
< CONFIG_EXPORTFS=y
2381,2404c2410,2411
< CONFIG_NFS_FS=y
< # CONFIG_NFS_V2 is not set
< CONFIG_NFS_V3=y
< # CONFIG_NFS_V3_ACL is not set
< CONFIG_NFS_V4=y
< # CONFIG_NFS_SWAP is not set
< # CONFIG_NFS_V4_1 is not set
< # CONFIG_NFS_FSCACHE is not set
< # CONFIG_NFS_USE_LEGACY_DNS is not set
< CONFIG_NFS_USE_KERNEL_DNS=y
< CONFIG_NFSD=y
< CONFIG_NFSD_V3=y
< # CONFIG_NFSD_V3_ACL is not set
< CONFIG_NFSD_V4=y
< # CONFIG_NFSD_PNFS is not set
< # CONFIG_NFSD_FAULT_INJECTION is not set
< CONFIG_GRACE_PERIOD=y
< CONFIG_LOCKD=y
< CONFIG_LOCKD_V4=y
< CONFIG_NFS_COMMON=y
< CONFIG_SUNRPC=y
< CONFIG_SUNRPC_GSS=y
< CONFIG_RPCSEC_GSS_KRB5=y
< # CONFIG_SUNRPC_DEBUG is not set
---
> # CONFIG_NFS_FS is not set
> # CONFIG_NFSD is not set
2440c2447
< CONFIG_NLS_CODEPAGE_932=m
---
> CONFIG_NLS_CODEPAGE_932=y
2442c2449
< CONFIG_NLS_CODEPAGE_874=m
---
> CONFIG_NLS_CODEPAGE_874=y
2459c2466
< # CONFIG_NLS_KOI8_U is not set
---
> CONFIG_NLS_KOI8_U=m
2861d2867
< CONFIG_OID_REGISTRY=y