Welcome to MilkyWay@home

Posts by POPSIE

1) Message boards : News : Nobdy Release 1.02 (Message 56684)
Posted 1 Jan 2013 by POPSIE
Post:
Yes, Debian/Linux x86_64 exist.
But what for you need that!?
Nbody doesn't work since february 2012!
Nbody WU's will not produced since month.
Looks like Nbody is dead or no qualified developer is available for to produce a working system of Nbody.
2) Message boards : News : Nobdy Release 1.02 (Message 56277)
Posted 23 Nov 2012 by POPSIE
Post:
On Windows 8


Name ps_nbody_plus_slice_emd_2_1352203202_12105_3
Arbeitspaket 269547725
Erstellt 22 Nov 2012 | 1:26:29 UTC
Gesendet 22 Nov 2012 | 1:26:35 UTC
Empfangen 22 Nov 2012 | 1:28:38 UTC
Serverstatus Abgeschlossen
Resultat Berechnungsfehler
Clientstatus Berechnungsfehler
Endstatus -1073741515 (0xffffffffc0000135) Unknown error number
Computer ID 472499
Ablaufdatum 4 Dec 2012 | 1:26:35 UTC
Laufzeit 0.00
CPU Zeit 0.00
Prüfungsstatus Ungültig
Punkte 0.00
Anwendungsversion MilkyWay@Home N-Body Simulation v1.02
Stderr Ausgabe

<core_client_version>7.0.28</core_client_version>
<![CDATA[
<message>
- exit code -1073741515 (0xc0000135)
</message>
]]>


On Windows 7


Name ps_nbody_plus_slice_emd_2_1352203202_13392_4
Arbeitspaket 269559500
Erstellt 23 Nov 2012 | 0:38:00 UTC
Gesendet 23 Nov 2012 | 0:38:05 UTC
Empfangen 23 Nov 2012 | 0:39:23 UTC
Serverstatus Abgeschlossen
Resultat Berechnungsfehler
Clientstatus Berechnungsfehler
Endstatus -1073741515 (0xffffffffc0000135) Unknown error number
Computer ID 435673
Ablaufdatum 5 Dec 2012 | 0:38:05 UTC
Laufzeit 0.00
CPU Zeit 0.00
Prüfungsstatus Ungültig
Punkte 0.00
Anwendungsversion MilkyWay@Home N-Body Simulation v1.02
Stderr Ausgabe

<core_client_version>7.0.25</core_client_version>
<![CDATA[
<message>
- exit code -1073741515 (0xc0000135)
</message>
]]>


On Linux OpenSuse


Name ps_nbody_plus_slice_emd_2_1352203202_10142_3
Arbeitspaket 269531818
Erstellt 22 Nov 2012 | 4:06:17 UTC
Gesendet 22 Nov 2012 | 4:06:29 UTC
Empfangen 22 Nov 2012 | 5:01:45 UTC
Serverstatus Abgeschlossen
Resultat Erfolgreich
Clientstatus Fertig
Endstatus 0 (0x0)
Computer ID 400549
Ablaufdatum 4 Dec 2012 | 4:06:29 UTC
Laufzeit 3,316.00
CPU Zeit 5,399.97
Prüfungsstatus Arbeitspaket fehlerhaft - Prüfung übersprungen
Punkte 0.00
Anwendungsversion MilkyWay@Home N-Body Simulation v0.94
Stderr Ausgabe

<core_client_version>6.12.34</core_client_version>
<![CDATA[
<stderr_txt>
<search_application> milkyway_nbody 0.94 Linux x86_64 double OpenMP, Crlibm </search_application>
Warning: not applying timestep correction for workunit with min version 0.80
Number of particles in bins is very small compared to total. (42 << 100000). Skipping distance calculation
<search_likelihood>-194.117647058823536</search_likelihood>
06:02:55 (19824): called boinc_finish

</stderr_txt>
]]>

[/u]
3) Message boards : News : N_body (Message 56177)
Posted 13 Nov 2012 by POPSIE
Post:
On Linux OpenSuse with MilkyWay@Home N-Body Simulation v0.94

Endstatus -1073741515 (0xffffffffc0000135) Unknown error number

<core_client_version>7.0.28</core_client_version>
<![CDATA[
<message>
- exit code -1073741515 (0xc0000135)
</message>
]]>


On Linux OpenSuse with MilkyWay@Home N-Body Simulation v1.00

Endstatus 193 (0xc1) EXIT_SIGNAL

<core_client_version>7.0.28</core_client_version>
<![CDATA[
<message>
process exited with code 193 (0xc1, -63)
</message>
<stderr_txt>
<search_application> milkyway_nbody 0.94 Linux x86 double , Crlibm </search_application>
Warning: not applying timestep correction for workunit with min version 0.80
<search_likelihood>-78.873167893643412</search_likelihood>
*** glibc detected *** ../../projects/milkyway.cs.rpi.edu_milkyway/milkyway_nbody_1.00_i686-pc-linux-gnu__mt: free(): invalid next size (normal): 0x094e0140 ***
======= Backtrace: =========
/lib/i386-linux-gnu/libc.so.6(+0x73e42)[0x575e42]
../../projects/milkyway.cs.rpi.edu_milkyway/milkyway_nbody_1.00_i686-pc-linux-gnu__mt(destroyNBodyState+0x72)[0x806c0d2]
../../projects/milkyway.cs.rpi.edu_milkyway/milkyway_nbody_1.00_i686-pc-linux-gnu__mt(nbMain+0x2ae)[0x80649fe]
../../projects/milkyway.cs.rpi.edu_milkyway/milkyway_nbody_1.00_i686-pc-linux-gnu__mt(main+0x28d)[0x806258d]
/lib/i386-linux-gnu/libc.so.6(__libc_start_main+0xf3)[0x51b4d3]
../../projects/milkyway.cs.rpi.edu_milkyway/milkyway_nbody_1.00_i686-pc-linux-gnu__mt[0x8062745]
======= Memory map: ========
0016d000-00184000 r-xp 00000000 2b:00 12003 /rofs/lib/i386-linux-gnu/libpthread-2.15.so
00184000-00185000 r--p 00016000 2b:00 12003 /rofs/lib/i386-linux-gnu/libpthread-2.15.so
00185000-00186000 rw-p 00017000 2b:00 12003 /rofs/lib/i386-linux-gnu/libpthread-2.15.so
00186000-00188000 rw-p 00000000 00:00 0
00502000-006a1000 r-xp 00000000 2b:00 12054 /rofs/lib/i386-linux-gnu/libc-2.15.so
006a1000-006a3000 r--p 0019f000 2b:00 12054 /rofs/lib/i386-linux-gnu/libc-2.15.so
006a3000-006a4000 rw-p 001a1000 2b:00 12054 /rofs/lib/i386-linux-gnu/libc-2.15.so
006a4000-006a7000 rw-p 00000000 00:00 0
007ac000-007ad000 r-xp 00000000 00:00 0 [vdso]
007b2000-007b9000 r-xp 00000000 2b:00 11978 /rofs/lib/i386-linux-gnu/librt-2.15.so
007b9000-007ba000 r--p 00006000 2b:00 11978 /rofs/lib/i386-linux-gnu/librt-2.15.so
007ba000-007bb000 rw-p 00007000 2b:00 11978 /rofs/lib/i386-linux-gnu/librt-2.15.so
00d9c000-00dc6000 r-xp 00000000 2b:00 12060 /rofs/lib/i386-linux-gnu/libm-2.15.so
00dc6000-00dc7000 r--p 00029000 2b:00 12060 /rofs/lib/i386-linux-gnu/libm-2.15.so
00dc7000-00dc8000 rw-p 0002a000 2b:00 12060 /rofs/lib/i386-linux-gnu/libm-2.15.so
00dcf000-00deb000 r-xp 00000000 2b:00 12056 /rofs/lib/i386-linux-gnu/libgcc_s.so.1
00deb000-00dec000 r--p 0001b000 2b:00 12056 /rofs/lib/i386-linux-gnu/libgcc_s.so.1
00dec000-00ded000 rw-p 0001c000 2b:00 12056 /rofs/lib/i386-linux-gnu/libgcc_s.so.1
00e00000-00e20000 r-xp 00000000 2b:00 12062 /rofs/lib/i386-linux-gnu/ld-2.15.so
00e20000-00e21000 r--p 0001f000 2b:00 12062 /rofs/lib/i386-linux-gnu/ld-2.15.so
00e21000-00e22000 rw-p 00020000 2b:00 12062 /rofs/lib/i386-linux-gnu/ld-2.15.so
08048000-08120000 r-xp 00000000 00:19 47848874 /opt/x86/boinc/work/pc23/projects/milkyway.cs.rpi.edu_milkyway/milkyway_nbody_1.00_i686-pc-linux-gnu__mt
08120000-08121000 r--p 000d8000 00:19 47848874 /opt/x86/boinc/work/pc23/projects/milkyway.cs.rpi.edu_milkyway/milkyway_nbody_1.00_i686-pc-linux-gnu__mt
08121000-08122000 rw-p 000d9000 00:19 47848874 /opt/x86/boinc/work/pc23/projects/milkyway.cs.rpi.edu_milkyway/milkyway_nbody_1.00_i686-pc-linux-gnu__mt
08122000-08143000 rw-p 00000000 00:00 0
09254000-09504000 rw-p 00000000 00:00 0 [heap]
b76be000-b7736000 rw-s 00000000 00:19 47972438 /opt/x86/boinc/work/pc23/slots/2/boinc_milkyway_nbody_0.94_i686-pc-linux-gnu__sse2_2
b7785000-b7788000 rw-p 00000000 00:00 0
b7788000-b7789000 rw-p 00000000 00:00 0
b7789000-b778a000 ---p 00000000 00:00 0
b778a000-b778d000 rw-p 00000000 00:00 0
b778d000-b778f000 rw-s 00000000 00:19 47972632 /opt/x86/boinc/work/pc23/slots/2/boinc_mmap_file
b778f000-b7791000 rw-p 00000000 00:00 0
bfeb9000-bfeda000 rw-p 00000000 00:00 0 [stack]
SIGABRT: abort called
Stack trace (12 frames):
../../projects/milkyway.cs.rpi.edu_milkyway/milkyway_nbody_1.00_i686-pc-linux-gnu__mt(boinc_catch_signal+0x1ad)[0x80c7ca7]
[0x7ac400]
[0x7ac416]
/lib/i386-linux-gnu/libc.so.6(gsignal+0x4f)[0x5301ef]
/lib/i386-linux-gnu/libc.so.6(abort+0x175)[0x533835]
/lib/i386-linux-gnu/libc.so.6(+0x692fa)[0x56b2fa]
/lib/i386-linux-gnu/libc.so.6(+0x73e42)[0x575e42]
../../projects/milkyway.cs.rpi.edu_milkyway/milkyway_nbody_1.00_i686-pc-linux-gnu__mt(destroyNBodyState+0x72)[0x806c0d2]
../../projects/milkyway.cs.rpi.edu_milkyway/milkyway_nbody_1.00_i686-pc-linux-gnu__mt(nbMain+0x2ae)[0x80649fe]
../../projects/milkyway.cs.rpi.edu_milkyway/milkyway_nbody_1.00_i686-pc-linux-gnu__mt(main+0x28d)[0x806258d]
/lib/i386-linux-gnu/libc.so.6(__libc_start_main+0xf3)[0x51b4d3]
../../projects/milkyway.cs.rpi.edu_milkyway/milkyway_nbody_1.00_i686-pc-linux-gnu__mt[0x8062745]

Exiting...

</stderr_txt>
]]>


Or On Linux OpenSuse with MilkyWay@Home N-Body Simulation v1.00


Serverstatus Abgeschlossen
Resultat Erfolgreich
Clientstatus Fertig
Prüfungsstatus Arbeitspaket fehlerhaft - Prüfung übersprungen

<core_client_version>7.0.31</core_client_version>
<![CDATA[
<stderr_txt>
<search_application> milkyway_nbody 0.94 Darwin x86_64 double OpenMP, Crlibm </search_application>
Using OpenMP 1 max threads on a system with 12 processors
Warning: not applying timestep correction for workunit with min version 0.80
<search_likelihood>-78.873167893643412</search_likelihood>
20:35:00 (39930): called boinc_finish

</stderr_txt>
]]>



Why is trying to use NVIDIA, this PC has got no GPU!?

<core_client_version>6.12.34</core_client_version>
<![CDATA[
<message>
process exited with code 7 (0x7, -249)
</message>
<stderr_txt>
<search_application> milkyway_nbody 0.94 Linux x86_64 double OpenCL, Crlibm </search_application>
FATAL: Module nvidia not found.
Error getting number of platform (-1001): CL_PLATFORM_NOT_FOUND_KHR
Failed to get information about device
02:40:48 (29064): called boinc_finish

</stderr_txt>
]]>

4) Message boards : News : N_body (Message 56176)
Posted 13 Nov 2012 by POPSIE
Post:
On Windows 8

Stderr Ausgabe

<core_client_version>7.0.28</core_client_version>
<![CDATA[
<message>
Incorrect function. (0x1) - exit code 1 (0x1)
</message>
<stderr_txt>
BOINC: parse gpu_opencl_dev_index 0
<search_application> milkyway_separation 1.02 Windows x86_64 double OpenCL </search_application>
Unrecognized XML in project preferences: max_gfx_cpu_pct
Skipping: 100
Skipping: /max_gfx_cpu_pct
BOINC GPU type suggests using OpenCL vendor 'Advanced Micro Devices, Inc.'
Error loading Lua script 'astronomy_parameters.txt': [string "number_parameters: 4..."]:1: '<name>' expected near '4'
Error reading astronomy parameters from file 'astronomy_parameters.txt'
Trying old parameters file
Using SSE3 path
Found 1 platform
Platform 0 information:
Name: AMD Accelerated Parallel Processing
Version: OpenCL 1.2 AMD-APP (923.1)
Vendor: Advanced Micro Devices, Inc.
Extensions: cl_khr_icd cl_amd_event_callback cl_amd_offline_devices cl_khr_d3d10_sharing
Profile: FULL_PROFILE
Using device 0 on platform 0
Found 2 CL devices
Device 'ATI RV770' (Advanced Micro Devices, Inc.:0x1002) (CL_DEVICE_TYPE_GPU)
Driver version: CAL 1.4.1720
Version: OpenCL 1.0 AMD-APP (923.1)
Compute capability: 0.0
Max compute units: 10
Clock frequency: 575 Mhz
Global mem size: 268435456
Local mem size: 16384
Max const buf size: 65536
Double extension: cl_khr_fp64
Build log:
--------------------------------------------------------------------------------
LOOP UNROLL: pragma unroll (line 288)
Unrolled as requested!
LOOP UNROLL: pragma unroll (line 280)
Unrolled as requested!
LOOP UNROLL: pragma unroll (line 273)
Unrolled as requested!
LOOP UNROLL: pragma unroll (line 244)
Unrolled as requested!
LOOP UNROLL: pragma unroll (line 202)
Unrolled as requested!

--------------------------------------------------------------------------------
Using AMD IL kernel
Binary status (0): CL_SUCCESS
Estimated AMD GPU GFLOP/s: 920 SP GFLOP/s, 184 DP FLOP/s
Using a target frequency of 60.0
Using a block size of 2560 with 145 blocks/chunk
Using clWaitForEvents() for polling (mode -1)
Range: { nu_steps = 640, mu_steps = 1600, r_steps = 1400 }
Iteration area: 2240000
Chunk estimate: 6
Num chunks: 7
Chunk size: 371200
Added area: 358400
Effective area: 2598400
Initial wait: 13 ms
Integration time: 91.939081 s. Average time per iteration = 143.654814 ms
Integral 0 time = 93.596521 s
Estimated AMD GPU GFLOP/s: 920 SP GFLOP/s, 184 DP FLOP/s
Using a target frequency of 60.0
Using a block size of 2560 with 145 blocks/chunk
Using clWaitForEvents() for polling (mode -1)
Range: { nu_steps = 640, mu_steps = 800, r_steps = 1400 }
Iteration area: 1120000
Chunk estimate: 3
Num chunks: 4
Chunk size: 371200
Added area: 364800
Effective area: 1484800
Initial wait: 13 ms
Integration time: 40.721433 s. Average time per iteration = 63.627240 ms
Integral 1 time = 41.992103 s
Estimated AMD GPU GFLOP/s: 920 SP GFLOP/s, 184 DP FLOP/s
Using a target frequency of 60.0
Using a block size of 2560 with 145 blocks/chunk
Using clWaitForEvents() for polling (mode -1)
Range: { nu_steps = 640, mu_steps = 800, r_steps = 1400 }
Iteration area: 1120000
Chunk estimate: 3
Num chunks: 4
Chunk size: 371200
Added area: 364800
Effective area: 1484800
Initial wait: 13 ms
Integration time: 42.888748 s. Average time per iteration = 67.013669 ms
Integral 2 time = 43.638151 s
Running likelihood with 66200 stars
Likelihood time = 0.342848 s
Non-finite result
Failed to calculate likelihood
<background_integral> 0.000170892611007 </background_integral>
<stream_integral> 0.000000000000000 0.084049238267364 79.889389034944514 </stream_integral>
<background_likelihood> -3.006227472513750 </background_likelihood>
<stream_only_likelihood> -1.#IND00000000000 -219.635048495225450 -3.920174169135421 </stream_only_likelihood>
<search_likelihood> -241.000000000000000 </search_likelihood>
14:19:26 (3632): called boinc_finish

</stderr_txt>
]]>

5) Message boards : News : NBody Update and New Runs (Message 55382)
Posted 18 Aug 2012 by POPSIE
Post:
Most of the NBODY ends with error:
http://milkyway.cs.rpi.edu/milkyway/result.php?resultid=280006234

Overview of results:
http://milkyway.cs.rpi.edu/milkyway/results.php?userid=147231&offset=0&show_names=0&state=0&appid=


<core_client_version>6.12.34</core_client_version>
<![CDATA[
<message>
The data is invalid. (0xd) - exit code 13 (0xd)
</message>
<stderr_txt>
<search_application> milkyway_nbody 0.84 Windows x86_64 double OpenMP, Crlibm </search_application>
Using OpenMP 8 max threads on a system with 8 processors
Error loading Lua script 'nbody_parameters.lua': [string "#---~/Research/milkywayathome_client/bin/milkyway_nbody -f ./pl..."]:1: unexpected symbol near '#'
Failed to read input parameters file
23:18:09 (6788): called boinc_finish

</stderr_txt>
]]>
[/quote]
6) Message boards : News : New NBody test searches (Message 55085)
Posted 11 Jul 2012 by POPSIE
Post:
After Restarting NBody-Server after last stop on beginning of month 6, I get many WU's.
First 3 Day's all work well.
On Third day, all WU's ending with calculation errors, I think ERR-NR15
After 4. day NBody Server where stopped and nobody gets new WU's
Now no WU's and no running NBody-Server is the Staus of today.
Over 6 weeks and no proper working NBody WOW!?

<core_client_version>6.12.34</core_client_version>
<![CDATA[
<message>
process exited with code 15 (0xf, -241)
</message>
<stderr_txt>
<search_application> milkyway_nbody 0.88 Linux x86_64 double  OpenMP, Crlibm </search_application>
Using OpenMP 7 max threads on a system with 4 processors
Error reading histogram line 37: massPerParticle = 0.000100
18:53:54 (5221): called boinc_finish

</stderr_txt>
7) Message boards : News : nbody workunit credit (Message 54662)
Posted 4 Jun 2012 by POPSIE
Post:
All I get for nbody since 1. june is:
04.06.2012 21:15:24 update requested by user
04.06.2012 21:15:29 Sending scheduler request: Requested by user.
04.06.2012 21:15:29 Requesting new tasks for CPU
04.06.2012 21:15:30 Scheduler request completed: got 0 new tasks
04.06.2012 21:15:30 No work available
8) Message boards : Number crunching : N-Body and the Bunker (Message 53341)
Posted 20 Feb 2012 by POPSIE
Post:
Thank you for your help.
I thought I was too stupid to handle it properly.
Hopefully waiting good news comes up for N-Body

[Deutsch]
Vielen Dank für deine Untertützung und Mühe.
Ich dachte schon ich sei zu blöde es richtig zu handhaben.
Dann warte ich mal, bis es neue, gute Nachrichten für N-Body gibt.
9) Message boards : Number crunching : N-Body and the Bunker (Message 53273)
Posted 18 Feb 2012 by POPSIE
Post:
Where did you change them? Online Preferences or BOINC Manager?

Stop Client, change on local system(global_prefs.xml), Start Client

If you add another project and would like to give all possible resources to Milkyway, you'd have to set cpu_scheduling_period_minutes to something very low, maybe even just 1 minute. And of course the resource share of that project would have to be very low... 0 could work good with v6.12.34.

With other projects and parts of Milkyway the bunker-problem doesn't exist, I've tested. It only affects the N-Body.

On moment I'm on 7.0.8 for test, should I go back to 6.12.34?
And I'd suggest also:

<suspend_cpu_usage>0</suspend_cpu_usage>

I've set to on local system prefs-file, restart client, but no other results.
10) Message boards : Number crunching : N-Body and the Bunker (Message 53266)
Posted 18 Feb 2012 by POPSIE
Post:
I checked with BOINC 6.10.60, 6.12.34, 6.13.1 and 7.0.8.
Played with parms of work_buf_min_days and work_buf_additinonal_days.
On all versions and different work_buf parameters he's starting first time with 8-12 WU's for a while, then he goes down to one WU and then every minute one new WU. I never get a filled bunker.
I also played with cpu using parameters, result of all, no bunker, only one WU per minute. Every WU needs 11 sec. CPU to finish.

And now my last settings on my openSUSE 12.1 Core 4 system with BOINC 7.0.8:
<venue name="school">
<run_on_batteries>1</run_on_batteries>
<run_if_user_active>1</run_if_user_active>
<run_gpu_if_user_active>1</run_gpu_if_user_active>
<idle_time_to_run>3</idle_time_to_run>
<suspend_if_no_recent_input>0</suspend_if_no_recent_input>
<suspend_cpu_usage>25</suspend_cpu_usage>
<leave_apps_in_memory>1</leave_apps_in_memory>
<cpu_scheduling_period_minutes>60</cpu_scheduling_period_minutes>
<max_cpus>4</max_cpus>
<max_ncpus_pct>100</max_ncpus_pct>
<cpu_usage_limit>100</cpu_usage_limit>
<disk_max_used_gb>100</disk_max_used_gb>
<disk_min_free_gb>0.001</disk_min_free_gb>
<disk_max_used_pct>50</disk_max_used_pct>
<disk_interval>20</disk_interval>
<vm_max_used_pct>75</vm_max_used_pct>
<ram_max_used_busy_pct>50</ram_max_used_busy_pct>
<ram_max_used_idle_pct>90</ram_max_used_idle_pct>
<work_buf_min_days>8</work_buf_min_days>
<work_buf_additional_days>2</work_buf_additional_days>
<confirm_before_connecting>0</confirm_before_connecting>
<hangup_if_dialed>0</hangup_if_dialed>
<max_bytes_sec_down>0</max_bytes_sec_down>
<max_bytes_sec_up>0</max_bytes_sec_up>
<daily_xfer_limit_mb>0</daily_xfer_limit_mb>
<daily_xfer_period_days>0</daily_xfer_period_days>
<dont_verify_images>0</dont_verify_images>
</venue>
11) Message boards : Number crunching : N-Body and the Bunker (Message 53143)
Posted 13 Feb 2012 by POPSIE
Post:
Now I understand the world is not at all.
Bad habit he moved to 12 WU's are very rare, and holds the bunker to 12
Then he builds from the bunker to 1 every 2 minutes and invites a new WU, and processes them.
It then goes on for hours and days Keep it up.
Why did he then sometimes it takes 12 WU's because I'm not yet come back.
But why only 12 place settings and allow much more!

Because maybe someone has an idea of what debug parameters to get behind the riddle?
Or someone has a special tip for settings?
My local recruitment attempts in the files or remotely via an account I did not learn much here.

There you can find messages and settings from my OpenSuse 11.4 based system core 4
12) Message boards : News : another change for the maximum time limit elapsed bug (Message 48845)
Posted 18 May 2011 by POPSIE
Post:
since Mai 7. n-body produces error.

<core_client_version>6.10.58</core_client_version>
<![CDATA[
<message>
Maximum elapsed time exceeded
</message>
<stderr_txt>
<search_application>milkywayathome nbody 0.40 Windows x86_64 double OpenMP Crlibm</search_application>
07:19:24: Using OpenMP 4 max threads on a system with 4 processors

</stderr_txt>
]]>


For more Info look at this




©2020 Astroinformatics Group