Trial Factoring
log in

Advanced search

Message boards : Number crunching : Trial Factoring

Previous · 1 · 2 · 3 · 4 · 5 · 6 · 7 · 8 . . . 23 · Next
Author Message
Stef42
Send message
Joined: 22 Dec 14
Posts: 15
Credit: 63,969,137
RAC: 254,189
Message 5873 - Posted: 27 Mar 2020, 22:09:24 UTC - in response to Message 5868.

Nvidia on Linux

<message>
process exited with code 195 (0xc3, -61)</message>
<stderr_txt>
22:54:06 (28652): wrapper (7.2.26012): starting
22:54:06 (28652): wrapper: running ./mfaktc.exe ( --device 0)
./mfaktc.exe: error while loading shared libraries: libcudart.so.10.1: cannot open shared object file: No such file or directory
22:54:07 (28652): ./mfaktc.exe exited; CPU time 0.001267
22:54:07 (28652): app exit status: 0x7f00
22:54:07 (28652): called boinc_finish
</stderr_txt>

This code tries running an .exe on Linux! Can be done under WINE (emulator), but not native.


Please see the FAQ, you're missing the CUDA 10.1 toolkit and you need this specific version in order for it to work.

Dirk Broer
Send message
Joined: 2 Jan 15
Posts: 71
Credit: 127,635,042
RAC: 36,872
Message 5874 - Posted: 27 Mar 2020, 22:59:49 UTC - in response to Message 5873.

Nvidia on Linux

<message>
process exited with code 195 (0xc3, -61)</message>
<stderr_txt>
22:54:06 (28652): wrapper (7.2.26012): starting
22:54:06 (28652): wrapper: running ./mfaktc.exe ( --device 0)
./mfaktc.exe: error while loading shared libraries: libcudart.so.10.1: cannot open shared object file: No such file or directory
22:54:07 (28652): ./mfaktc.exe exited; CPU time 0.001267
22:54:07 (28652): app exit status: 0x7f00
22:54:07 (28652): called boinc_finish
</stderr_txt>

This code tries running an .exe on Linux! Can be done under WINE (emulator), but not native.


Please see the FAQ, you're missing the CUDA 10.1 toolkit and you need this specific version in order for it to work.


I'll upgrade the system to Ubuntu 19.10 and install the latest Nvidia, OpenCL and CUDA files

zombie67 [MM]
Avatar
Send message
Joined: 4 Dec 14
Posts: 30
Credit: 1,005,778,104
RAC: 12,912
Message 5875 - Posted: 27 Mar 2020, 23:23:39 UTC

I thought the linux apps were updated so that installation of the toolkit was no longer required. I could swear I read that somewhere. Or am I going crazy?
____________
Reno, NV
Team: SETI.USA

Dirk Broer
Send message
Joined: 2 Jan 15
Posts: 71
Credit: 127,635,042
RAC: 36,872
Message 5876 - Posted: 27 Mar 2020, 23:39:44 UTC - in response to Message 5872.

That's not something I can choose, it is an error that the code comes up with


What card do you have?


Error comes up using various AMD APUs (Athlon 5350 Radeon R3, Athlon A12-9800E Radeon R7)


Can you pls post also the opencl line from the BOINC event manager so we could forward this to the developer of the app.


For the Athlon 5350:
14-8-2019 11:23:24 OpenCL: AMD/ATI GPU 0: AMD Radeon Graphics (driver version 2671.3, device version OpenCL 1.2 AMD-APP (2671.3), 2553MB, 2553MB available, 154 GFLOPS peak)
14-8-2019 11:23:24 OpenCL: AMD/ATI GPU 1: AMD KABINI (DRM 3.27.0, 5.0.0-25-generic, LLVM 8.0.0) (driver version 19.0.8, device version OpenCL 1.1 Mesa 19.0.8, 3072MB, 3072MB available, 96 GFLOPS peak)

Dirk Broer
Send message
Joined: 2 Jan 15
Posts: 71
Credit: 127,635,042
RAC: 36,872
Message 5877 - Posted: 28 Mar 2020, 0:18:58 UTC - in response to Message 5872.
Last modified: 28 Mar 2020, 0:20:21 UTC

That's not something I can choose, it is an error that the code comes up with


What card do you have?


Error comes up using various AMD APUs (Athlon 5350 Radeon R3, Athlon A12-9800E Radeon R7)


Can you pls post also the opencl line from the BOINC event manager so we could forward this to the developer of the app.


For the Athlon A12-9800E:
28-3-2020 01:15:45 OpenCL: AMD/ATI GPU 0: AMD CARRIZO (DRM 3.33.0, 5.3.0-42-generic, LLVM 9.0.1) (driver version 20.1.0-devel, device version OpenCL 1.1 Mesa 20.1.0-devel (git-aad0e6f 2020-03-27 bionic-oibaf-ppa), 3072MB, 3072MB available, 576 GFLOPS peak)
28-3-2020 01:15:45 OpenCL CPU: pthread-AMD A12-9800E RADEON R7, 12 COMPUTE CORES 4C+8G (OpenCL driver vendor: The pocl project, driver version 1.1, device version OpenCL 1.2 pocl HSTR: pthread-x86_64-pc-linux-gnu-bdver4)

zombie67 [MM]
Avatar
Send message
Joined: 4 Dec 14
Posts: 30
Credit: 1,005,778,104
RAC: 12,912
Message 5878 - Posted: 28 Mar 2020, 3:04:45 UTC - in response to Message 5820.
Last modified: 28 Mar 2020, 3:13:26 UTC

linux v2 and Mac doesnt have an entry yet

I just tried running it on a Mac. It failed.

Here is the task:

http://srbase.my-firewall.org/sr5/result.php?resultid=387750937

Stderr output

<core_client_version>7.14.2</core_client_version>
<![CDATA[
<message>
process exited with code 195 (0xc3, -61)</message>
<stderr_txt>
20:02:04 (52956): wrapper (7.2.26012): starting
20:02:04 (52956): wrapper: running ./mfakto ( --device 0)
ERROR: unknown option '--device'
20:02:05 (52956): ./mfakto exited; CPU time 0.013171
20:02:05 (52956): app exit status: 0x100
20:02:05 (52956): called boinc_finish

</stderr_txt>
]]>


Here are the system and GPU details if you need them:

1 3/23/2020 3:49:43 PM Starting BOINC client version 7.14.2 for x86_64-apple-darwin
3 3/23/2020 3:49:43 PM Libraries: libcurl/7.58.0 OpenSSL/1.1.0g zlib/1.2.11 c-ares/1.13.0
5 3/23/2020 3:49:43 PM OpenCL: AMD/ATI GPU 0: AMD Radeon Pro 580 Compute Engine (driver version 1.2 (Jan 13 2020 20:12:40), device version OpenCL 1.2, 8192MB, 8192MB available, 3456 GFLOPS peak)
6 3/23/2020 3:49:43 PM OpenCL CPU: Intel(R) Core(TM) i7-7700K CPU @ 4.20GHz (OpenCL driver vendor: Apple, driver version 1.1, device version OpenCL 1.2)
8 3/23/2020 3:49:43 PM Processor: 8 GenuineIntel Intel(R) Core(TM) i7-7700K CPU @ 4.20GHz [x86 Family 6 Model 158 Stepping 9]
9 3/23/2020 3:49:43 PM Processor features: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clfsh ds acpi mmx fxsr sse sse2 ss htt tm pbe pni pclmulqdq dtes64 mon dscpl vmx est tm2 ssse3 fma cx16 tpr pdcm sse4_1 sse4_2 x2apic movbe popcnt aes pcid xsave o
10 3/23/2020 3:49:43 PM OS: Mac OS X 10.15.3 (Darwin 19.3.0)


Edit: I tried a second Mac, with a different GPU. Same error. Here is the line for the GPU form the event log:

5 3/27/2020 8:12:25 PM OpenCL: AMD/ATI GPU 0: AMD Radeon R9 M295X Compute Engine (driver version 1.2 (Jan 13 2020 20:12:40), device version OpenCL 1.2, 4096MB, 4096MB available, 2176 GFLOPS peak)
____________
Reno, NV
Team: SETI.USA

davidBAM
Send message
Joined: 5 Apr 19
Posts: 3
Credit: 1,162,470,925
RAC: 0
Message 5879 - Posted: 28 Mar 2020, 3:18:58 UTC
Last modified: 28 Mar 2020, 3:19:16 UTC

On a twin GPU system (Linux), both WU are going onto one GPU while the other one is ignored

Profile rebirther
Volunteer moderator
Project administrator
Project developer
Project tester
Project scientist
Avatar
Send message
Joined: 2 Jan 13
Posts: 7142
Credit: 42,729,227
RAC: 404
Message 5880 - Posted: 28 Mar 2020, 6:08:30 UTC - in response to Message 5879.

On a twin GPU system (Linux), both WU are going onto one GPU while the other one is ignored


multi GPU is not supported

Profile rebirther
Volunteer moderator
Project administrator
Project developer
Project tester
Project scientist
Avatar
Send message
Joined: 2 Jan 13
Posts: 7142
Credit: 42,729,227
RAC: 404
Message 5881 - Posted: 28 Mar 2020, 6:20:11 UTC - in response to Message 5875.

I thought the linux apps were updated so that installation of the toolkit was no longer required. I could swear I read that somewhere. Or am I going crazy?


you still need the toolkit

Trotador
Send message
Joined: 22 Oct 15
Posts: 2
Credit: 301,017,654
RAC: 638
Message 5882 - Posted: 28 Mar 2020, 8:44:05 UTC

Radeon VII, Ubuntu 18.04

Exit status 195 (0xc3) EXIT_CHILD_FAILED
Computer ID 198359

<core_client_version>7.14.2</core_client_version>
<![CDATA[
<message>
process exited with code 195 (0xc3, -61)</message>
<stderr_txt>
09:37:39 (28615): wrapper (7.2.26012): starting
09:37:39 (28615): wrapper: running mfakto-x64 ( --device 0)
ERROR: unknown option '--device'
09:37:40 (28615): mfakto-x64 exited; CPU time 0.003226
09:37:40 (28615): app exit status: 0x100
09:37:40 (28615): called boinc_finish

</stderr_txt>
]]>

Trotador
Send message
Joined: 22 Oct 15
Posts: 2
Credit: 301,017,654
RAC: 638
Message 5883 - Posted: 28 Mar 2020, 8:53:43 UTC

RX570, ubuntu 18.04
Exit status 195 (0xc3) EXIT_CHILD_FAILED
Computer ID 41183

<core_client_version>7.6.31</core_client_version>
<![CDATA[
<message>
process exited with code 195 (0xc3, -61)
</message>
<stderr_txt>
09:50:48 (48047): wrapper (7.2.26012): starting
09:50:48 (48047): wrapper: running mfakto-x64 ( --device 0)
ERROR: unknown option '--device'
09:50:49 (48047): mfakto-x64 exited; CPU time 0.006712
09:50:49 (48047): app exit status: 0x100
09:50:49 (48047): called boinc_finish

</stderr_txt>
]]>

dannyridel
Avatar
Send message
Joined: 21 Jul 19
Posts: 63
Credit: 7,102,619
RAC: 0
Message 5884 - Posted: 28 Mar 2020, 9:28:23 UTC - in response to Message 5883.
Last modified: 28 Mar 2020, 9:30:14 UTC

Exactly the same problem on Radeon Vega 8, Windows 10:

<core_client_version>7.14.2</core_client_version> <![CDATA[ <message> (unknown error) - exit code 195 (0xc3)</message> <stderr_txt> 11:49:20 (57492): wrapper (7.5.26012): starting 11:49:20 (57492): wrapper: running mfakto-x64.exe () 11:49:23 (57492): mfakto-x64.exe exited; CPU time 0.046875 11:49:23 (57492): app exit status: 0xc0000135 11:49:23 (57492): called boinc_finish(195) </stderr_txt>

Installed the perquisites reb said last time.

Dirk Broer
Send message
Joined: 2 Jan 15
Posts: 71
Credit: 127,635,042
RAC: 36,872
Message 5885 - Posted: 28 Mar 2020, 10:19:53 UTC

GPU72 tasks for Ati on Windows keeps running forever for HD 6670, Radeon HD 7660D 'Devastator' IGP of AMD A10-5700 and HD 8400/R3 IGP of Athlon 5350.

Profile rebirther
Volunteer moderator
Project administrator
Project developer
Project tester
Project scientist
Avatar
Send message
Joined: 2 Jan 13
Posts: 7142
Credit: 42,729,227
RAC: 404
Message 5886 - Posted: 28 Mar 2020, 10:51:47 UTC - in response to Message 5885.

GPU72 tasks for Ati on Windows keeps running forever for HD 6670, Radeon HD 7660D 'Devastator' IGP of AMD A10-5700 and HD 8400/R3 IGP of Athlon 5350.


check your stderr.txt in slot folder. The cards could be very slow.

Dirk Broer
Send message
Joined: 2 Jan 15
Posts: 71
Credit: 127,635,042
RAC: 36,872
Message 5887 - Posted: 28 Mar 2020, 10:56:13 UTC - in response to Message 5886.
Last modified: 28 Mar 2020, 11:08:59 UTC

GPU72 tasks for Ati on Windows keeps running forever for HD 6670, Radeon HD 7660D 'Devastator' IGP of AMD A10-5700 and HD 8400/R3 IGP of Athlon 5350.


check your stderr.txt in slot folder. The cards could be very slow.


I've aborted the lot when they weren't finished after 10 hours, 9 hours of which they were at 100% completed.
http://srbase.my-firewall.org/sr5/results.php?hostid=996
http://srbase.my-firewall.org/sr5/results.php?hostid=2148

Profile rebirther
Volunteer moderator
Project administrator
Project developer
Project tester
Project scientist
Avatar
Send message
Joined: 2 Jan 13
Posts: 7142
Credit: 42,729,227
RAC: 404
Message 5888 - Posted: 28 Mar 2020, 11:23:16 UTC - in response to Message 5887.

GPU72 tasks for Ati on Windows keeps running forever for HD 6670, Radeon HD 7660D 'Devastator' IGP of AMD A10-5700 and HD 8400/R3 IGP of Athlon 5350.


check your stderr.txt in slot folder. The cards could be very slow.


I've aborted the lot when they weren't finished after 10 hours, 9 hours of which they were at 100% completed.
http://srbase.my-firewall.org/sr5/results.php?hostid=996
http://srbase.my-firewall.org/sr5/results.php?hostid=2148


let them run, you can see at the end of the file a progress but its very slow.

Dirk Broer
Send message
Joined: 2 Jan 15
Posts: 71
Credit: 127,635,042
RAC: 36,872
Message 5889 - Posted: 28 Mar 2020, 11:43:21 UTC - in response to Message 5888.
Last modified: 28 Mar 2020, 11:53:04 UTC

Funny thing is that the system with the A10-5700 has three HD6670 cards, and it own IGP, and crunches four of the GPU72 WUs at the same time.

I get the idea that in Radeon-coding the option '--device 0' just doesn't work, not for Linux and not for Windows.

Profile PDW
Send message
Joined: 15 Oct 15
Posts: 41
Credit: 1,077,181,594
RAC: 35,132
Message 5892 - Posted: 28 Mar 2020, 12:26:58 UTC - in response to Message 5889.

Funny thing is that the system with the A10-5700 has three HD6670 cards, and it own IGP, and crunches four of the GPU72 WUs at the same time.

Those four WUs will have been running on just 1 of the GPUs.

Dirk Broer
Send message
Joined: 2 Jan 15
Posts: 71
Credit: 127,635,042
RAC: 36,872
Message 5893 - Posted: 28 Mar 2020, 12:55:54 UTC - in response to Message 5892.
Last modified: 28 Mar 2020, 13:27:11 UTC

Funny thing is that the system with the A10-5700 has three HD6670 cards, and it own IGP, and crunches four of the GPU72 WUs at the same time.

Those four WUs will have been running on just 1 of the GPUs.


No they didn't, all four AMD GPUs were busy at the same time. Normally they run four Moo!, Seti, Seti Beta or Collatz WUs, or any combination of these.
The view in BOINC Tasks was just the same when running SRBase GPU72, all GPUs running.

Profile rebirther
Volunteer moderator
Project administrator
Project developer
Project tester
Project scientist
Avatar
Send message
Joined: 2 Jan 13
Posts: 7142
Credit: 42,729,227
RAC: 404
Message 5894 - Posted: 28 Mar 2020, 13:05:50 UTC - in response to Message 5889.

Funny thing is that the system with the A10-5700 has three HD6670 cards, and it own IGP, and crunches four of the GPU72 WUs at the same time.

I get the idea that in Radeon-coding the option '--device 0' just doesn't work, not for Linux and not for Windows.


-d 0

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

Message boards : Number crunching : Trial Factoring


Main page · Your account · Message boards


Copyright © 2014-2024 BOINC Confederation / rebirther