1)
Message boards :
Number crunching :
Always immediate segfault on MilkyWay@Home N-Body Simulation v1.62 (mt)
(Message 65044)
Posted 18 Aug 2016 by Carsten Milkau Post: I successfully ran MilkyWay@Home N-Body Simulation v1.62 (mt) on the following setup:
enabled heap randomization (breaks libc5) disabled uselib syscall (breaks libc5)
|
2)
Message boards :
Number crunching :
Always immediate segfault on MilkyWay@Home N-Body Simulation v1.62 (mt)
(Message 65043)
Posted 18 Aug 2016 by Carsten Milkau Post: I identfied three possibly related settings:
Enabled heap randomization (breaks libc5) Disable uselib syscall (breaks libc5)
|
3)
Message boards :
Number crunching :
Always immediate segfault on MilkyWay@Home N-Body Simulation v1.62 (mt)
(Message 65040)
Posted 17 Aug 2016 by Carsten Milkau Post: Erm, as I mentioned, this happens with *every* WU (of this app) for me. I have more than 100 failed tasks. It's always immediate segfault. I checked many of them, most belong to WU with both failed and successful runs (for other user). But I didnt see many other crashes, mostly the disk usage problem. So it looks a bit specific to me. Unfortunately I dont know how zo obtain more information. P.S. I noticed the app is statically linked. Do you use different libraries or a different compiler for nbody? The segfaults are so early they are likely still during initialization. I recently disabled kernel support for some very old compilers / c libraries. |
4)
Message boards :
Number crunching :
Always immediate segfault on MilkyWay@Home N-Body Simulation v1.62 (mt)
(Message 65038)
Posted 17 Aug 2016 by Carsten Milkau Post: N-Body sim always crashes immediately (0 secs CPU) with segmentation fault.
- Other Milkyway@home apps run fine. - Ran a memtest on all cpus in parallel just to make sure it's not hardware. All fine. For instance, see: |
5)
Message boards :
Number crunching :
All WU crash with permission error
(Message 61833)
Posted 3 Jun 2014 by Carsten Milkau Post: See e.g. http://milkyway.cs.rpi.edu/milkyway/result.php?resultid=758337201 Boinc runs on niceness 19 on my system. I think this is reasonable. However, it seems the milkyway tasks attempt to set priority to 0, which fails. I guess that attempt to an priority upgrade is an error in the first place? If there is a reason to run at higher process priority than "background" please tell me, maybe I can find a way to make that work. |
6)
Message boards :
Number crunching :
Computation errors
(Message 57465)
Posted 9 Mar 2013 by Carsten Milkau Post: Got a different kind of error, which fails all WU immediately: <core_client_version>7.0.29</core_client_version> I completely removed and re-initialized the project several times without any luck. Apparantly GPU tasks need this file but don't download it. http://milkyway.cs.rpi.edu/milkyway/result.php?resultid=415923043 http://milkyway.cs.rpi.edu/milkyway/results.php?userid=765878&state=5 |
©2024 Astroinformatics Group