Core 7 Issue

Moderators: Site Moderators, FAHC Science Team

Core 7 Issue

Postby Juggy » Sun Sep 06, 2020 6:53 am

Woke up to a couple of these errors in my client, any ideas? Nothing has changed on my computer.

Code: Select all
05:50:17:WU02:FS01:Started FahCore on PID 9820
05:50:17:WU02:FS01:Core PID:5256
05:50:17:WU02:FS01:FahCore 0xa7 started
05:50:18:WU02:FS01:0xa7:*********************** Log Started 2020-09-06T05:50:17Z ***********************
05:50:18:WU02:FS01:0xa7:************************** Gromacs Folding@home Core ***************************
05:50:18:WU02:FS01:0xa7:       Type: 0xa7
05:50:18:WU02:FS01:0xa7:       Core: Gromacs
05:50:18:WU02:FS01:0xa7:       Args: -dir 02 -suffix 01 -version 706 -lifeline 9820 -checkpoint 15 -np
05:50:18:WU02:FS01:0xa7:             28
05:50:18:WU02:FS01:0xa7:************************************ CBang *************************************
05:50:18:WU02:FS01:0xa7:       Date: Nov 27 2019
05:50:18:WU02:FS01:0xa7:       Time: 03:40:09
05:50:18:WU02:FS01:0xa7:   Revision: d25803215b59272441049dfa05a0a9bf7a6e3c48
05:50:18:WU02:FS01:0xa7:     Branch: master
05:50:18:WU02:FS01:0xa7:   Compiler: Visual C++ 2008
05:50:18:WU02:FS01:0xa7:    Options: /TP /nologo /EHa /wd4297 /wd4103 /Ox /MT
05:50:18:WU02:FS01:0xa7:   Platform: win32 10
05:50:18:WU02:FS01:0xa7:       Bits: 64
05:50:18:WU02:FS01:0xa7:       Mode: Release
05:50:18:WU02:FS01:0xa7:************************************ System ************************************
05:50:18:WU02:FS01:0xa7:        CPU: AMD Ryzen 9 3950X 16-Core Processor
05:50:18:WU02:FS01:0xa7:     CPU ID: AuthenticAMD Family 23 Model 113 Stepping 0
05:50:18:WU02:FS01:0xa7:       CPUs: 32
05:50:18:WU02:FS01:0xa7:     Memory: 31.92GiB
05:50:18:WU02:FS01:0xa7:Free Memory: 18.10GiB
05:50:18:WU02:FS01:0xa7:    Threads: WINDOWS_THREADS
05:50:18:WU02:FS01:0xa7: OS Version: 6.2
05:50:18:WU02:FS01:0xa7:Has Battery: false
05:50:18:WU02:FS01:0xa7: On Battery: false
05:50:18:WU02:FS01:0xa7: UTC Offset: 3
05:50:18:WU02:FS01:0xa7:        PID: 5256
05:50:18:WU02:FS01:0xa7:        CWD: C:\Users\Mark Spencer\AppData\Roaming\FAHClient\work
05:50:18:WU02:FS01:0xa7:******************************** Build - libFAH ********************************
05:50:18:WU02:FS01:0xa7:    Version: 0.0.19
05:50:18:WU02:FS01:0xa7:     Author: Joseph Coffland <joseph@cauldrondevelopment.com>
05:50:18:WU02:FS01:0xa7:  Copyright: 2019 foldingathome.org
05:50:18:WU02:FS01:0xa7:   Homepage: https://foldingathome.org/
05:50:18:WU02:FS01:0xa7:       Date: Nov 25 2019
05:50:18:WU02:FS01:0xa7:       Time: 17:12:41
05:50:18:WU02:FS01:0xa7:   Revision: d5b5c747532224f986b7cd02c968ed9a20c16d6e
05:50:18:WU02:FS01:0xa7:     Branch: master
05:50:18:WU02:FS01:0xa7:   Compiler: Visual C++ 2008
05:50:18:WU02:FS01:0xa7:    Options: /TP /nologo /EHa /wd4297 /wd4103 /Ox /MT
05:50:18:WU02:FS01:0xa7:   Platform: win32 10
05:50:18:WU02:FS01:0xa7:       Bits: 64
05:50:18:WU02:FS01:0xa7:       Mode: Release
05:50:18:WU02:FS01:0xa7:************************************ Build *************************************
05:50:18:WU02:FS01:0xa7:       SIMD: avx_256
05:50:18:WU02:FS01:0xa7:********************************************************************************
05:50:18:WU02:FS01:0xa7:Project: 16417 (Run 951, Clone 1, Gen 92)
05:50:18:WU02:FS01:0xa7:Unit: 0x0000006596880e6e5e8a617cae5e151e
05:50:18:WU02:FS01:0xa7:Reading tar file core.xml
05:50:18:WU02:FS01:0xa7:Reading tar file frame92.tpr
05:50:18:WU02:FS01:0xa7:Digital signatures verified
05:50:18:WU02:FS01:0xa7:Calling: mdrun -s frame92.tpr -o frame92.trr -x frame92.xtc -cpt 15 -nt 28
05:50:18:WU02:FS01:0xa7:Steps: first=23000000 total=250000
05:50:18:WU02:FS01:0xa7:ERROR:
05:50:18:WU02:FS01:0xa7:ERROR:-------------------------------------------------------
05:50:18:WU02:FS01:0xa7:ERROR:Program GROMACS, VERSION 5.0.4-20191026-456f0d636-unknown
05:50:18:WU02:FS01:0xa7:ERROR:Source code file: C:\build\fah\core-a7-avx-release\windows-10-64bit-core-a7-avx-release\gromacs-core\build\gromacs\src\gromacs\mdlib\domdec.c, line: 6902
05:50:18:WU02:FS01:0xa7:ERROR:
05:50:18:WU02:FS01:0xa7:ERROR:Fatal error:
05:50:18:WU02:FS01:0xa7:ERROR:There is no domain decomposition for 20 ranks that is compatible with the given box and a minimum cell size of 1.4227 nm
05:50:18:WU02:FS01:0xa7:ERROR:Change the number of ranks or mdrun option -rcon or -dds or your LINCS settings
05:50:18:WU02:FS01:0xa7:ERROR:Look in the log file for details on the domain decomposition
05:50:18:WU02:FS01:0xa7:ERROR:For more information and tips for troubleshooting, please check the GROMACS
05:50:18:WU02:FS01:0xa7:ERROR:website at http://www.gromacs.org/Documentation/Errors
05:50:18:WU02:FS01:0xa7:ERROR:-------------------------------------------------------
05:50:22:WU00:FS01:Upload complete
05:50:22:WU00:FS01:Server responded WORK_ACK (400)
05:50:22:WU00:FS01:Final credit estimate, 5012.00 points
05:50:22:WU00:FS01:Cleaning up
05:50:22:WU02:FS01:0xa7:WARNING:Unexpected exit
05:50:23:WARNING:WU02:FS01:FahCore returned: EARLY_UNIT_END (123 = 0x7b)

Mod Edit: Added Code Tags - PantherX
Image
Image
Juggy
 
Posts: 102
Joined: Fri Mar 20, 2020 1:07 pm
Location: Qatar

Re: Core 7 Issue

Postby PantherX » Sun Sep 06, 2020 7:41 am

Please note that error message means that the WU assigned to you was not able to be partitioned across your CPUs since the assigned WU was too small. Thus, it encountered the Domain Decomposition issue. Your client will simply pick up a new WU and carry on.

There are plans to ensure that errors like this are handled more gracefully by the client using FahCore_a8.
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
User avatar
PantherX
Site Moderator
 
Posts: 6765
Joined: Wed Dec 23, 2009 10:33 am
Location: Land Of The Long White Cloud

Re: Core 7 Issue

Postby Juggy » Sun Sep 06, 2020 8:00 am

PantherX wrote:Please note that error message means that the WU assigned to you was not able to be partitioned across your CPUs since the assigned WU was too small. Thus, it encountered the Domain Decomposition issue. Your client will simply pick up a new WU and carry on.

There are plans to ensure that errors like this are handled more gracefully by the client using FahCore_a8.


Excellent, thank you for the explanation. Terminology had me confused.
Juggy
 
Posts: 102
Joined: Fri Mar 20, 2020 1:07 pm
Location: Qatar


Return to Issues with a specific WU

Who is online

Users browsing this forum: No registered users and 2 guests

cron