Trial Factoring tests
log in

Advanced search

Message boards : Number crunching : Trial Factoring tests

Previous · 1 · 2 · 3 · 4 · 5 · 6 · 7 · Next
Author Message
dannyridel
Avatar
Send message
Joined: 21 Jul 19
Posts: 63
Credit: 15,355,619
RAC: 74,346
Message 6149 - Posted: 13 Apr 2020, 3:05:02 UTC - in response to Message 6148.

Even though your APU is not recognized, I think selecting APU will be slower than "AUTO" - kernels used on the APU settings were tested on much older, different APU's (if i recall correctly, that was tuned for A8-3850... released 2011.)

I'm hoping I can test the IGP of the Ryzen 2400g that I get occasional access to...


Ah ok, I tried GCN now and it seems to be okay too.

Profile rebirther
Volunteer moderator
Project administrator
Project developer
Project tester
Project scientist
Avatar
Send message
Joined: 2 Jan 13
Posts: 7479
Credit: 43,687,101
RAC: 41,962
Message 6151 - Posted: 13 Apr 2020, 7:03:12 UTC - in response to Message 6144.

I have extended the parameter list for mfakto. (and compiled)

You can download it frome here:
https://p-numbers.net/mfakto_linux_x86_64_device.zip

HTH

the new code snippet:
else if(!strcmp((char*)"--device", argv[i]))
{
if(i+1 >= argc)
{
printf("ERROR: no device number specified for option \"--device\"\n");
return ERR_PARAM;
}
else if (argv[i+1][0] == '0') // parse to 00
{
devicenumber = strtol("00",&ptr,10);
if(*ptr || errno || devicenumber != strtol("00",&ptr,10) )
{
printf("ERROR: can't parse for option \"--device\"\n");
return ERR_PARAM;
}
}
i++;
}[/url]


This app is now up.

DeleteNull
Volunteer developer
Volunteer tester
Send message
Joined: 29 Nov 14
Posts: 83
Credit: 374,914,522
RAC: 4,661
Message 6152 - Posted: 13 Apr 2020, 7:33:20 UTC - in response to Message 6151.

Thanks, now I get a new error:

process exited with code 195

This is an error from BOINC (wrapper)
195 is CHILD_FAILED,
Which means the wrapper failed to start the worker app.

Profile rebirther
Volunteer moderator
Project administrator
Project developer
Project tester
Project scientist
Avatar
Send message
Joined: 2 Jan 13
Posts: 7479
Credit: 43,687,101
RAC: 41,962
Message 6153 - Posted: 13 Apr 2020, 7:41:28 UTC - in response to Message 6152.
Last modified: 13 Apr 2020, 7:41:41 UTC

Thanks, now I get a new error:

process exited with code 195

This is an error from BOINC (wrapper)
195 is CHILD_FAILED,
Which means the wrapper failed to start the worker app.


I have tried it on the server (ubuntu) and the wrapper is starting the app (CPU), selftest was ok.

Did you use the same wrapper?

DeleteNull
Volunteer developer
Volunteer tester
Send message
Joined: 29 Nov 14
Posts: 83
Credit: 374,914,522
RAC: 4,661
Message 6154 - Posted: 13 Apr 2020, 7:56:33 UTC - in response to Message 6153.

All my "standalone tests" are okay too. I think the problem ist that mfakto-x86_64 starts a child process to compile the mfakto_Kernels.elf file.

I seems that this forces the CHILD_FAILED error.

Can you include this file:
https://p-numbers.net/mfakto_Kernels.elf
in the ZIP?

(Just for a test)

Profile rebirther
Volunteer moderator
Project administrator
Project developer
Project tester
Project scientist
Avatar
Send message
Joined: 2 Jan 13
Posts: 7479
Credit: 43,687,101
RAC: 41,962
Message 6155 - Posted: 13 Apr 2020, 8:02:00 UTC - in response to Message 6154.
Last modified: 13 Apr 2020, 8:27:31 UTC

All my "standalone tests" are okay too. I think the problem ist that mfakto-x86_64 starts a child process to compile the mfakto_Kernels.elf file.

I seems that this forces the CHILD_FAILED error.

Can you include this file:
https://p-numbers.net/mfakto_Kernels.elf
in the ZIP?

(Just for a test)


I hope you will not get an error, I put this in v5 zip.

Update
I have seen the error which I have expected, v7 is available.

DeleteNull
Volunteer developer
Volunteer tester
Send message
Joined: 29 Nov 14
Posts: 83
Credit: 374,914,522
RAC: 4,661
Message 6156 - Posted: 13 Apr 2020, 8:29:36 UTC - in response to Message 6155.
Last modified: 13 Apr 2020, 8:30:04 UTC

I get an error (two):
A new attached PC: Download error (checksum fail)
Previously attached: The old ZIP (without elf-file) remains, if you replace the file manually the file is deleted (zip error).

It seems you have to create a new version, sorry.

DeleteNull
Volunteer developer
Volunteer tester
Send message
Joined: 29 Nov 14
Posts: 83
Credit: 374,914,522
RAC: 4,661
Message 6157 - Posted: 13 Apr 2020, 8:42:42 UTC - in response to Message 6156.

On both of my PC with AMD GPU: error 195 from wrapper, with or without elf-file?!

Profile rebirther
Volunteer moderator
Project administrator
Project developer
Project tester
Project scientist
Avatar
Send message
Joined: 2 Jan 13
Posts: 7479
Credit: 43,687,101
RAC: 41,962
Message 6158 - Posted: 13 Apr 2020, 8:43:29 UTC - in response to Message 6157.

On both of my PC with AMD GPU: error 195 from wrapper, with or without elf-file?!


with the .elf file

DeleteNull
Volunteer developer
Volunteer tester
Send message
Joined: 29 Nov 14
Posts: 83
Credit: 374,914,522
RAC: 4,661
Message 6159 - Posted: 13 Apr 2020, 8:56:39 UTC - in response to Message 6158.
Last modified: 13 Apr 2020, 8:59:17 UTC

Yes with elf-file.
But in the tests before (zip without elf-file) was the same error.

Standalone test with wrapper and job.xml succeeded. So I don't know what the problem is. Sofware is o.k., but if the wrapper is started inside BOINC it fails.

Profile rebirther
Volunteer moderator
Project administrator
Project developer
Project tester
Project scientist
Avatar
Send message
Joined: 2 Jan 13
Posts: 7479
Credit: 43,687,101
RAC: 41,962
Message 6160 - Posted: 13 Apr 2020, 8:59:52 UTC - in response to Message 6159.
Last modified: 13 Apr 2020, 9:04:12 UTC

Yes with elf-file.
But in the tests before (zip without elf-file) was the same error.


If the old wrapper was currently working in standalone then it must also be running in BOINC, this is odd, do you have a chance to compile the linux wrapper from the latest BOINC code? So we could trying if the latest wrapper is running.

https://github.com/BOINC/boinc (in samples folder)

DeleteNull
Volunteer developer
Volunteer tester
Send message
Joined: 29 Nov 14
Posts: 83
Credit: 374,914,522
RAC: 4,661
Message 6161 - Posted: 13 Apr 2020, 9:25:29 UTC - in response to Message 6160.

You can download here:
https://p-numbers.net/wrapper

Version information:
wolfgang@i920:~/Downloads/boinc-client_release-7-7.16/samples/wrapper> ./wrapper --version
11:22:17 (26004): wrapper (7.16.26016): starting
7.16.6
11:22:17 (26004): called boinc_finish(0)

If you need a verion from trunk, I can compile it too. It shouldn't differ from this version here.

Profile rebirther
Volunteer moderator
Project administrator
Project developer
Project tester
Project scientist
Avatar
Send message
Joined: 2 Jan 13
Posts: 7479
Credit: 43,687,101
RAC: 41,962
Message 6162 - Posted: 13 Apr 2020, 9:36:44 UTC - in response to Message 6161.
Last modified: 13 Apr 2020, 9:53:00 UTC

You can download here:
https://p-numbers.net/wrapper

Version information:
wolfgang@i920:~/Downloads/boinc-client_release-7-7.16/samples/wrapper> ./wrapper --version
11:22:17 (26004): wrapper (7.16.26016): starting
7.16.6
11:22:17 (26004): called boinc_finish(0)

If you need a verion from trunk, I can compile it too. It shouldn't differ from this version here.


v8 app is up with new wrapper

Update:
damnit, the execute bit was not set for wrapper. v9 is up

Looks like its running? But there are no checkpoints, if you are able to put the checkpoint code into the new wrapper code that would be great, I think the Mac app should be running too with the new wrapper.

DeleteNull
Volunteer developer
Volunteer tester
Send message
Joined: 29 Nov 14
Posts: 83
Credit: 374,914,522
RAC: 4,661
Message 6163 - Posted: 13 Apr 2020, 10:40:15 UTC - in response to Message 6162.

No doesn't work:
version `GLIBC_2.29' not found

The PC where I took the wrapper from has a very new linux and this dependency is awful.
I compiled BOINC on Ubuntu 18.04, and this wrapper should be o.k.:
https://p-numbers.net/wrapper_26016

For Linux it's a hard way to deploy software.....

Profile rebirther
Volunteer moderator
Project administrator
Project developer
Project tester
Project scientist
Avatar
Send message
Joined: 2 Jan 13
Posts: 7479
Credit: 43,687,101
RAC: 41,962
Message 6164 - Posted: 13 Apr 2020, 15:34:21 UTC - in response to Message 6163.
Last modified: 13 Apr 2020, 16:08:23 UTC

No doesn't work:
version `GLIBC_2.29' not found

The PC where I took the wrapper from has a very new linux and this dependency is awful.
I compiled BOINC on Ubuntu 18.04, and this wrapper should be o.k.:
https://p-numbers.net/wrapper_26016

For Linux it's a hard way to deploy software.....


Linux shows me as shared lib not as executable file. I need a corrected file, cannot change it in config.

DeleteNull
Volunteer developer
Volunteer tester
Send message
Joined: 29 Nov 14
Posts: 83
Credit: 374,914,522
RAC: 4,661
Message 6165 - Posted: 13 Apr 2020, 16:40:27 UTC - in response to Message 6164.

Oops,

can you try this one:
https://p-numbers.net/wrapper_26016_7.16

Profile rebirther
Volunteer moderator
Project administrator
Project developer
Project tester
Project scientist
Avatar
Send message
Joined: 2 Jan 13
Posts: 7479
Credit: 43,687,101
RAC: 41,962
Message 6166 - Posted: 13 Apr 2020, 17:02:14 UTC - in response to Message 6165.

Oops,

can you try this one:
https://p-numbers.net/wrapper_26016_7.16


is up, I have tried to compile it on the old ubuntu, no chance, I think the code isnt working anymore with older OS.

DeleteNull
Volunteer developer
Volunteer tester
Send message
Joined: 29 Nov 14
Posts: 83
Credit: 374,914,522
RAC: 4,661
Message 6167 - Posted: 13 Apr 2020, 17:13:52 UTC - in response to Message 6166.

And it's running!

stderr:
19:07:26 (16398): wrapper (7.16.26016): starting
19:07:26 (16398): wrapper (7.16.26016): starting
19:07:26 (16398): wrapper: running ./mfakto-x64 ()
DRM_IOCTL_I915_GEM_APERTURE failed: Invalid argument
Assuming 131072kB available aperture size.
May lead to reduced performance or incorrect rendering.
get chip id failed: -1 [2]
param: 4, val: 0

After one minute it jumped to 100% ?!
The first checkpoint was generated after 300 s.

Profile rebirther
Volunteer moderator
Project administrator
Project developer
Project tester
Project scientist
Avatar
Send message
Joined: 2 Jan 13
Posts: 7479
Credit: 43,687,101
RAC: 41,962
Message 6168 - Posted: 13 Apr 2020, 17:15:14 UTC - in response to Message 6167.

And it's running!

stderr:
19:07:26 (16398): wrapper (7.16.26016): starting
19:07:26 (16398): wrapper (7.16.26016): starting
19:07:26 (16398): wrapper: running ./mfakto-x64 ()
DRM_IOCTL_I915_GEM_APERTURE failed: Invalid argument
Assuming 131072kB available aperture size.
May lead to reduced performance or incorrect rendering.
get chip id failed: -1 [2]
param: 4, val: 0

After one minute it jumped to 100% ?!
The first checkpoint was generated after 300 s.


ok but there is no checkpointing in the wrapper code.

DeleteNull
Volunteer developer
Volunteer tester
Send message
Joined: 29 Nov 14
Posts: 83
Credit: 374,914,522
RAC: 4,661
Message 6169 - Posted: 13 Apr 2020, 17:17:16 UTC - in response to Message 6168.

The checkpoint is generated from mfakto with the name: M97983883.ckp

Previous · 1 · 2 · 3 · 4 · 5 · 6 · 7 · Next
Post to thread

Message boards : Number crunching : Trial Factoring tests


Main page · Your account · Message boards


Copyright © 2014-2024 BOINC Confederation / rebirther