BOINC 7.8.3 is not picking up the avx, avx2 flags in Ubuntu 16.04.3

Message boards : Questions and problems : BOINC 7.8.3 is not picking up the avx, avx2 flags in Ubuntu 16.04.3
Message board moderation

To post messages, you must log in.

Previous · 1 · 2

AuthorMessage
Jim1348

Send message
Joined: 8 Nov 10
Posts: 310
United States
Message 86758 - Posted: 29 Jun 2018, 17:44:45 UTC - in response to Message 86757.  

Can you please post the log the message log output from BOINC itself (either via BOINC Manager, or from stdoutdae.txt), to eliminate the possibility of artefacts being introduced by BOINC Tasks?

I don't see stdoutdae.txt at all. As I recall, that is Windows only. And the location of the BOINC logs may have changed in 7.10.2, as I don't see /var/log/boinc.log at all.

But here is the first portion of the "client_state.xml" file in /var/lib/boinc:
<client_state>
<host_info>
    <timezone>-14400</timezone>
    <domain_name>i7-3770-PC1</domain_name>
    <ip_addr>127.0.1.1</ip_addr>
    <host_cpid>b026f7dd6b5136cd61bfad6010a9f7ef</host_cpid>
    <p_ncpus>8</p_ncpus>
    <p_vendor>GenuineIntel</p_vendor>
    <p_model>Intel(R) Core(TM) i7-3770 CPU @ 3.40GHz [Family 6 Model 58 Stepping 9]</p_model>
    <p_features>fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm cpuid_fault epb pti retpoline spec_ctrl tpr_shadow vnmi flexpriority ept vpid fsgsbase smep erms xsaveopt dtherm ida arat pln pts</p_features>


Also, here is the relevant portion of the "sched_request_www.gpugrid.net.xml" file in the same folder, which seems to give the same features list:
<host_info>
    <timezone>-14400</timezone>
    <domain_name>i7-3770-PC1</domain_name>
    <ip_addr>127.0.1.1</ip_addr>
    <host_cpid>b026f7dd6b5136cd61bfad6010a9f7ef</host_cpid>
    <p_ncpus>8</p_ncpus>
    <p_vendor>GenuineIntel</p_vendor>
    <p_model>Intel(R) Core(TM) i7-3770 CPU @ 3.40GHz [Family 6 Model 58 Stepping 9]</p_model>
    <p_features>fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm cpuid_fault epb pti retpoline spec_ctrl tpr_shadow vnmi flexpriority ept vpid fsgsbase smep erms xsaveopt dtherm ida arat pln pts</p_features>


If I need to look anywhere else, please let me know. Thanks again.
ID: 86758 · Report as offensive
Richard Haselgrove
Volunteer tester
Help desk expert

Send message
Joined: 5 Oct 06
Posts: 5081
United Kingdom
Message 86759 - Posted: 29 Jun 2018, 18:08:04 UTC - in response to Message 86758.  

And that, of course, contains the ones you said were missing:

ssse3
sse4_1
sse4_2
avx

(but no avx2). We really have to work out whether the problem is the BOINC client not sending the messages, or BOINCtasks screwing up when receiving them: different fixers needed ;-)

We need that intermediate display from BOINC - does boinccmd --get_messages help? Or could you use your Windows machine manager to attach remotely to the Linux client?
ID: 86759 · Report as offensive
Juha
Volunteer developer
Volunteer tester
Help desk expert

Send message
Joined: 20 Nov 12
Posts: 801
Finland
Message 86760 - Posted: 29 Jun 2018, 18:10:51 UTC

Debian 9 in a VM.

/proc/cpuinfo
flags		: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx rdtscp lm constant_tsc rep_good nopl xtopology nonstop_tsc eagerfpu pni pclmulqdq ssse3 cx16 sse4_1 sse4_2 x2apic movbe popcnt aes xsave avx rdrand hypervisor lahf_lm abm 3dnowprefetch kaiser avx2 rdseed clflushopt


stdoutdae.txt
29-Jun-2018 20:27:28 [---] Starting BOINC client version 7.11.0 for x86_64-pc-linux-gnu
29-Jun-2018 20:27:28 [---] This a development version of BOINC and may not function properly
29-Jun-2018 20:27:28 [---] log flags: file_xfer, sched_ops, task
29-Jun-2018 20:27:28 [---] Libraries: libcurl/7.52.1 OpenSSL/1.0.2l zlib/1.2.8 libidn2/0.16 libpsl/0.17.0 (+libidn2/0.16) libssh2/1.7.0 nghttp2/1.18.1 librtmp/2.3
29-Jun-2018 20:27:28 [---] Data directory: /home/juha/boinc
29-Jun-2018 20:27:28 [---] No usable GPUs found
29-Jun-2018 20:27:28 [---] [libc detection] gathered: 2.24, Debian GLIBC 2.24-11+deb9u1
29-Jun-2018 20:27:28 [---] Host name: debian9
29-Jun-2018 20:27:28 [---] Processor: 2 GenuineIntel Intel(R) Core(TM) i5-6200U CPU @ 2.30GHz [Family 6 Model 78 Stepping 3]
29-Jun-2018 20:27:28 [---] Processor features: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx rdtscp lm constant_tsc rep_good nopl xtopology nonstop_tsc eagerfpu pni pclmulqdq ssse3 cx16 sse4_1 sse4_2 x2apic movbe popcnt aes xsave avx rdrand hypervisor lahf_lm abm 3dnowprefetch kaiser avx2 rdseed clflushopt
29-Jun-2018 20:27:28 [---] OS: Linux Debian: Debian GNU/Linux 9.3 (stretch) [4.9.0-6-amd64|libc 2.24 (Debian GLIBC 2.24-11+deb9u1)]


boinccmd --get_messages
1: 29-Jun-2018 20:27:28 (low) [] Starting BOINC client version 7.11.0 for x86_64-pc-linux-gnu
2: 29-Jun-2018 20:27:28 (low) [] This a development version of BOINC and may not function properly
3: 29-Jun-2018 20:27:28 (low) [] log flags: file_xfer, sched_ops, task
4: 29-Jun-2018 20:27:28 (low) [] Libraries: libcurl/7.52.1 OpenSSL/1.0.2l zlib/1.2.8 libidn2/0.16 libpsl/0.17.0 (+libidn2/0.16) libssh2/1.7.0 nghttp2/1.18.1 librtmp/2.3
5: 29-Jun-2018 20:27:28 (low) [] Data directory: /home/juha/boinc
6: 29-Jun-2018 20:27:28 (low) [] No usable GPUs found
7: 29-Jun-2018 20:27:28 (low) [] [libc detection] gathered: 2.24, Debian GLIBC 2.24-11+deb9u1
8: 29-Jun-2018 20:27:28 (low) [] Host name: debian9
9: 29-Jun-2018 20:27:28 (low) [] Processor: 2 GenuineIntel Intel(R) Core(TM) i5-6200U CPU @ 2.30GHz [Family 6 Model 78 Stepping 3]
10: 29-Jun-2018 20:27:28 (low) [] Processor features: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx rdtscp lm constant_tsc rep_good nopl xtopology nonstop_tsc eagerfpu pni pclmulqdq ssse3 cx16 sse4_1 sse4_2 x2apic movbe popcnt aes xsave avx rdrand hypervisor lahf_lm abm 3dnowprefetch kaiser avx2 rdseed clflushopt
11: 29-Jun-2018 20:27:28 (low) [] OS: Linux Debian: Debian GNU/Linux 9.3 (stretch) [4.9.0-6-amd64|libc 2.24 (Debian GLIBC 2.24-11+deb9u1)]


Manager
https://drive.google.com/open?id=18-8m_MrDhuhfsa1M3a3WyoDfJzcvrvis

That's 300 or so characters. At this point I'd say if Fred thinks client truncates the text he needs to tell where or tell how he accesses the log messages or show network capture with the truncated message.
ID: 86760 · Report as offensive
Juha
Volunteer developer
Volunteer tester
Help desk expert

Send message
Joined: 20 Nov 12
Posts: 801
Finland
Message 86761 - Posted: 29 Jun 2018, 18:18:22 UTC - in response to Message 86760.  

Oh right. Windows Manager does truncate the text but I think it's a wxWidgets on Windows or just Windows issue. In my case the last visible feature in the window is popcount but if copied to clipboard all the features get copied.
ID: 86761 · Report as offensive
Richard Haselgrove
Volunteer tester
Help desk expert

Send message
Joined: 5 Oct 06
Posts: 5081
United Kingdom
Message 86762 - Posted: 29 Jun 2018, 18:33:45 UTC

Thanks Juha - everything is there, including avx2. I suspect that the difference between your i5-6200U and Jim's i7-3770 may be genuine - I have an i7-3770K running Windows, and that reports avx but not avx2 as well.

Would you be able to guide Jim to the new location for stdoutdae - it *might* be /var/lib/boinc following the systemd changes in v7.10.2
ID: 86762 · Report as offensive
Jim1348

Send message
Joined: 8 Nov 10
Posts: 310
United States
Message 86763 - Posted: 29 Jun 2018, 18:37:39 UTC - in response to Message 86759.  

And that, of course, contains the ones you said were missing:

ssse3
sse4_1
sse4_2
avx

(but no avx2). We really have to work out whether the problem is the BOINC client not sending the messages, or BOINCtasks screwing up when receiving them: different fixers needed ;-)

We need that intermediate display from BOINC - does boinccmd --get_messages help? Or could you use your Windows machine manager to attach remotely to the Linux client?

The absence of avx2 is no problem; this is only an Ivy Bridge CPU. That did not come until Haswell, and it would be present in those comparable files I am sure.

I see that Juha has beat me to it, but on my machine, boinccmd --get_messages:
1: 29-Jun-2018 10:21:49 (low) [] Starting BOINC client version 7.10.2 for x86_64-pc-linux-gnu
2: 29-Jun-2018 10:21:49 (low) [] log flags: file_xfer, sched_ops, task
3: 29-Jun-2018 10:21:49 (low) [] Libraries: libcurl/7.47.0 OpenSSL/1.0.2g zlib/1.2.8 libidn/1.32 librtmp/2.3
4: 29-Jun-2018 10:21:49 (low) [] Data directory: /var/lib/boinc-client
5: 29-Jun-2018 10:21:49 (low) [] CUDA: NVIDIA GPU 0: GeForce GTX 750 Ti (driver version 384.13, CUDA version 9.0, compute 

capability 5.0, 1999MB, 1862MB available, 1472 GFLOPS peak)
6: 29-Jun-2018 10:21:49 (low) [] OpenCL: NVIDIA GPU 0: GeForce GTX 750 Ti (driver version 384.130, device version OpenCL 1.2 

CUDA, 1999MB, 1862MB available, 1472 GFLOPS peak)
7: 29-Jun-2018 10:21:50 (low) [] [libc detection] gathered: 2.23, Ubuntu GLIBC 2.23-0ubuntu10
8: 29-Jun-2018 10:21:50 (low) [] Host name: i7-3770-PC1
9: 29-Jun-2018 10:21:50 (low) [] Processor: 8 GenuineIntel Intel(R) Core(TM) i7-3770 CPU @ 3.40GHz [Family 6 Model 58 Stepping 9]
10: 29-Jun-2018 10:21:50 (low) [] Processor features: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 
clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology 
nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic 
popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm cpuid_fault epb pti retpoline spec_ctrl tpr_shadow vnmi flexpriority 
ept vpid fsgsbase smep erms xsaveopt dtherm ida arat pln pts
11: 29-Jun-2018 10:21:50 (low) [] OS: Linux Ubuntu: Ubuntu 16.04.4 LTS [4.13.0-45-generic|libc 2.23 (Ubuntu GLIBC 2.23-0ubuntu10)]

Yes, I can do a Windows into the Ubuntu machine if we need it.
ID: 86763 · Report as offensive
Richard Haselgrove
Volunteer tester
Help desk expert

Send message
Joined: 5 Oct 06
Posts: 5081
United Kingdom
Message 86764 - Posted: 29 Jun 2018, 18:43:21 UTC - in response to Message 86763.  

Thanks - I think the boinccmd is sufficient to say "no fault found" within the BOINC ecosystem. Time to toss it back into Fred's lap, I'm afraid, with the results from what we've found here.
ID: 86764 · Report as offensive
Juha
Volunteer developer
Volunteer tester
Help desk expert

Send message
Joined: 20 Nov 12
Posts: 801
Finland
Message 86765 - Posted: 29 Jun 2018, 18:56:20 UTC - in response to Message 86762.  

Would you be able to guide Jim to the new location for stdoutdae - it *might* be /var/lib/boinc following the systemd changes in v7.10.2


Not that it matters any more but for completeness sake:

Debian's 7.6.33 logs to /var/lib/boinc.log and /var/lib/boincerr.log.
Upstream 7.9.1 logs to systemd's journal. Read with journalctl -u boinc-client or your favourite GUI log reader.
Debian moved to systemd's journal earlier than that but I'm not sure when.
ID: 86765 · Report as offensive
Jim1348

Send message
Joined: 8 Nov 10
Posts: 310
United States
Message 86766 - Posted: 29 Jun 2018, 19:45:44 UTC - in response to Message 86764.  

OK, thanks. I will just look at the BOINC logs. It is more reliable than anything else.
ID: 86766 · Report as offensive
Previous · 1 · 2

Message boards : Questions and problems : BOINC 7.8.3 is not picking up the avx, avx2 flags in Ubuntu 16.04.3

Copyright © 2024 University of California.
Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation.