| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Completed Research
Forum: FightAIDS@Home Phase 2
Thread: WU goes all in errors Seg violation exit code 11 |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 3
|
|
| Author |
|
|
[AF>Libristes]Maeda
Cruncher Joined: Sep 1, 2011 Post Count: 43 Status: Offline Project Badges: 
|
Hello !
I saw some projects had beta testing (related to new gcc version compilation) which fixes other projects WU errors. I think all my WU errors on FAAH2 could be the same root cause. Is there any beta testing scheduled for fixing this ? Example : FAH2_ 001605_ avx38781-2_ 000001_ 000054_ 071_ 0-- I'm on : 4.17.3-1-ARCH Intel CPU. Thanks. |
|||
|
||||
|
Pakal92
Cruncher Joined: Dec 6, 2015 Post Count: 2 Status: Offline Project Badges: 
|
I have the same issue on my machine AMD running Windows 10, the tasks run around 4 minutes and crashes with exit code 38. Only I finished successfully a pair of tasks in my laptop AMD with Lubuntu 14.04
----------------------------------------This is the full message: <core_client_version>7.12.1</core_client_version> <![CDATA[ <message> Se ha alcanzado el final del archivo. (0x26) - exit code 38 (0x26)</message> <stderr_txt> INFO: result number = 0 %IMPACT-I: Requested file to open for appending md.out Does not exist. Opening it as a new file. %IMPACT-I: Softcore binding energy with umax = 1000.00000 %IMPACT-I: Using AGBNP2: Analytical Generalized Born Model + Analytic Non-Polar Hydration Model %IMPACT-I: Hybrid potential for binding with lambda = 0.00000 agbnpf_assign_parameters(): info: attempting to load from SQL tables. forrtl: No hay ningún proceso en el otro extremo de la canalización. forrtl: severe (38): error during write, unit 6, file CONOUT$ Image PC Routine Line Source wcgrid_fahb_bedam 00D5ADAF Unknown Unknown Unknown wcgrid_fahb_bedam 00B7322A _cwrite_ 37 utilities.for wcgrid_fahb_bedam 00B1711F Unknown Unknown Unknown wcgrid_fahb_bedam 00B170E5 Unknown Unknown Unknown wcgrid_fahb_bedam 00B1711F Unknown Unknown Unknown wcgrid_fahb_bedam 00A5B406 Unknown Unknown Unknown wcgrid_fahb_bedam 00D2561C Unknown Unknown Unknown wcgrid_fahb_bedam 00B10CD0 Unknown Unknown Unknown wcgrid_fahb_bedam 00B10C20 Unknown Unknown Unknown wcgrid_fahb_bedam 00B10C50 Unknown Unknown Unknown wcgrid_fahb_bedam 00B10C80 Unknown Unknown Unknown wcgrid_fahb_bedam 00B10C90 Unknown Unknown Unknown wcgrid_fahb_bedam 00ADFDC0 Unknown Unknown Unknown wcgrid_fahb_bedam 00B10CC0 Unknown Unknown Unknown wcgrid_fahb_bedam 00B10BE0 Unknown Unknown Unknown wcgrid_fahb_bedam 00B10CD0 Unknown Unknown Unknown </stderr_txt> ]]>
AMD A10-7700K @ 3.8 GHz, Win10 Pro x64 (95 W)
Intel Core i3-4130 @ 3.4 GHz, Kubuntu 20.04 x64 (54 W) Intel Pentium E5300 @ 2.6 GHz, Lubuntu 18.04 x64 (65 W) |
||
|
|
Pakal92
Cruncher Joined: Dec 6, 2015 Post Count: 2 Status: Offline Project Badges:
|
Well, I think I have a clue about why my tasks was failing.
----------------------------------------You will see, I got some tasks and I chaged its priority (trough Tasks Manager) when its was running since Low to Normal or High, all these tasks failing. Later, I got more tasks and let with its default priority (Low) and they finished successfully. Then, I downloaded 4 more tasks and again changed priority Low to Normal and it failed too. Conclusion: don't touch default priority. Anyway I'll download more tasks and leave it processing without touch anything. Cheers!
AMD A10-7700K @ 3.8 GHz, Win10 Pro x64 (95 W)
Intel Core i3-4130 @ 3.4 GHz, Kubuntu 20.04 x64 (54 W) Intel Pentium E5300 @ 2.6 GHz, Lubuntu 18.04 x64 (65 W) |
||
|
|
|