Page 1 of 1
INTERRUPTED (102 = 0x66) when using ON IDLE
Posted: Fri Apr 03, 2020 5:26 am
by jgolinuc
Hi, I'm new to the FAH project and I've installed the FAH client on my home and work computers.
Both with the setting to work on idle. And both of them get interrupted shortly after finishing an assignment in the middle of the night when I wasn't accessing any of them
Log from my home computer:
Code: Select all
04:52:39:WU00:FS01:0x22:Completed 1940000 out of 2000000 steps (97%)
04:53:52:WU00:FS01:0x22:Completed 1960000 out of 2000000 steps (98%)
04:54:57:FS01:Shutting core down
04:54:57:WU00:FS01:0x22:WARNING:Console control signal 1 on PID 9584
04:54:57:WU00:FS01:0x22:Exiting, please wait. . .
04:54:57:WU00:FS01:0x22:Folding@home Core Shutdown: INTERRUPTED
04:54:57:WU00:FS01:FahCore returned: INTERRUPTED (102 = 0x66)
Log from my work computer:
Code: Select all
04:50:45:WU01:FS00:0xa7:Completed 155000 out of 500000 steps (31%)
04:52:23:WU01:FS00:0xa7:Completed 160000 out of 500000 steps (32%)
04:54:02:WU01:FS00:0xa7:Completed 165000 out of 500000 steps (33%)
04:55:08:FS00:Shutting core down
04:55:08:FS01:Shutting core down
04:55:08:WU02:FS01:0x22:WARNING:Console control signal 1 on PID 4528
04:55:08:WU02:FS01:0x22:Exiting, please wait. . .
04:55:08:WU01:FS00:0xa7:WARNING:Console control signal 1 on PID 3756
04:55:09:WU01:FS00:0xa7:Exiting, please wait. . .
04:55:09:WU02:FS01:0x22:Folding@home Core Shutdown: INTERRUPTED
04:55:09:WU02:FS01:FahCore returned: INTERRUPTED (102 = 0x66)
04:55:10:WU01:FS00:0xa7:Folding@home Core Shutdown: INTERRUPTED
04:55:10:WU01:FS00:FahCore returned: INTERRUPTED (102 = 0x66)
For info, the computer are located in different places (one at my office and one at home in a different city, with different internet provider, etc...)
Mod Edit: Added Code Tags - PantherX
Re: INTERRUPTED (102 = 0x66) when using ON IDLE
Posted: Fri Apr 03, 2020 5:47 am
by bruce
I don't have enough information to give you a good answer. IINTERRUPTED is the normal message which something tells FAH it needs to suspend processing but it doesn't say who sent the signal.
1) Did something like WindowsUpdate decide it was time to restart your computer?
2) Is your system configured to go into hibernation or sleep when certain things happen?
============================================================================
The following is a personal recommendation which has nothing to do with your question and you're free to ignore.
If you are folding with a low-performance GPU, the "idle" setting is a useful way to manage the issue of the potentially slow screen updates while your using the computer. It also maximizes FAH performance while your sleeping.
There's no reason to use idle when you fold with your CPU. The Operating System does a better job of managing CPU performance than using idle.
These options can be configured using FAHControl.
Re: INTERRUPTED (102 = 0x66) when using ON IDLE
Posted: Fri Apr 03, 2020 6:00 am
by jgolinuc
I've checked, no Windows Update and no reboot happend. Both computer are not going in hibernation nor sleep mode, they've been up all night but stopped folding at around 04:55 this night.
For info, I'm using two different identities on the same team.
Regarding your personal recommendation, my work computer has not much performance (CPU: i7-3770, GPU: Nvidia GeForce GTX 460) and my home computer is better (CPU: i7-8700K, GPU: Nvidia GeForce GTX 1080) but I rather have them working FAH when I'm not using them: because my home computer is usually for gaming which is incompatible with running FAH (I need my CPU and GPU power
) and my work computer is to slow to be doing both (me working and folding at the same time).
I found the "On idle" setting quite usefull so I don't forget to unpause the FAH client when leaving work or stop using my home computer.
Re: INTERRUPTED (102 = 0x66) when using ON IDLE
Posted: Fri Apr 03, 2020 6:04 am
by jgolinuc
Ooohhh I've just figured out something: the log is in UTC time !
So when it says INTERRUPTED at 04:55 it means in UTC, so for me it was 06:55, the time when I check on both of them.
Re: INTERRUPTED (102 = 0x66) when using ON IDLE
Posted: Fri Apr 03, 2020 5:41 pm
by Joe_H
We really need a lightbulb emoji! Yes, log time is UTC , also called Zulu time for that "Z" at the end of the time string.