Questions and Answers :
Unix/Linux :
Get SIGSEGV on Astropule Tasks
Message board moderation
Author | Message |
---|---|
Harry Send message Joined: 11 Dec 00 Posts: 2 Credit: 25,008 RAC: 0 |
Every Astropulse task results in a SIGSEGV (SETI@home tasks work fine). Here's the output on stderr: <core_client_version>6.10.17</core_client_version> <![CDATA[ <message> process exited with code 193 (0xc1, -63) </message> <stderr_txt> In ap_gfx_main.cpp: in ap_graphics_init(): Starting client. SIGSEGV: segmentation violation Stack trace (6 frames): [0x440158] [0x2b78a687d8f0] [0x58a272] [0x43cd72] [0x2b78a68749ca] [0x2b78a6b7270d] Exiting... </stderr_txt> ]]> Thanks for your help! Harald. |
SylvainD Send message Joined: 11 Oct 00 Posts: 2 Credit: 135,568 RAC: 0 |
Hello, i have the same problem on Linux/Gentoo 3.0.6 with nvidia-drivers : <core_client_version>6.12.33</core_client_version> <![CDATA[ <message> process exited with code 193 (0xc1, -63) </message> <stderr_txt> In ap_gfx_main.cpp: in ap_graphics_init(): Starting client. SIGSEGV: segmentation violation Stack trace (64 frames): [0x440158] [0x7f315e4da430] [0x58a28b] [0x43cd72] ... Note: boinc is boinc_client launched at boot an attached to init. May be boinc must be compiled without CUDA? Some body confirm? Best Regards |
BilBg Send message Joined: 27 May 07 Posts: 3720 Credit: 9,385,827 RAC: 0 |
CUDA?? - Despite I'm not a Linux expert I will safely say that CUDA here is "double" irrelevant ;) 1. BOINC do not use CUDA, it only detects the GPU (BOINC do not compute any project tasks) 2. Talk here is about Astropulse which is CPU only If you are talking about this line: In ap_gfx_main.cpp: in ap_graphics_init(): Starting client. a. This line is not output from BOINC - it is message from Astropulse app b. ap_graphics have nothing to do with CUDA - it is just the graphics/screensaver part of the Astropulse app  - ALF - "Find out what you don't do well ..... then don't do it!" :)  |
skildude Send message Joined: 4 Oct 00 Posts: 9541 Credit: 50,759,529 RAC: 60 |
I thought SIGSEGV was a hardware issue In a rich man's house there is no place to spit but his face. Diogenes Of Sinope |
SylvainD Send message Joined: 11 Oct 00 Posts: 2 Credit: 135,568 RAC: 0 |
Hello, SIGSEGV is not harware issue. It is is a software defect. The pogram try to access a wrong memory segment. If i have understand, Astropulse can be launch only in an interactiv session boinc, to authozied it to access the screensaver. I have change my profile to excecute only standard SETI, while this bug is not corrected for Linux daemon. Thank's all Best Regards Sylvain Depuille |
skildude Send message Joined: 4 Oct 00 Posts: 9541 Credit: 50,759,529 RAC: 60 |
I run optimized apps from the Lunatics folks. I've not had a problem with SIGSEGV. However the optimized apps also don't run the screensaver. So a simpler solution would seem to be not to use the screensaver since as we do know the screensaver does tend to slow processing down a bit In a rich man's house there is no place to spit but his face. Diogenes Of Sinope |
BilBg Send message Joined: 27 May 07 Posts: 3720 Credit: 9,385,827 RAC: 0 |
You may want to see this (problems with Linux stock Astropulse app): http://setiathome.berkeley.edu/forum_thread.php?id=65917 Â - ALF - "Find out what you don't do well ..... then don't do it!" :) Â |
Harry Send message Joined: 11 Dec 00 Posts: 2 Credit: 25,008 RAC: 0 |
Thank you for your replies. It sounds reasonable that this issue is somehow related to the screensaver: I'm running the tasks on a headless linux virtual root server. Is it possible to look into this by someone of the development team? Meanwhile I've deactivated Astropule tasks. Thanks and best regards, Harald. |
©2024 University of California
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.