LHC@home

Have you checked the messages when Boinc starts up that it actually recoqnizes the avx extension on the processor?

good point - unfortunately, the BOINC event log shows the messages only one day back. So, to make the check, I would have to shut down BOINC and restart it. Which I cannot do right now as I have also several VM tasks running (CMS), and experience has shown that VM tasks tend to fail when they get interrupted by a BOINC shutdown. So I cannot do this until later today.

Meanwhile, I detected another case where on the same task the processing by my PC is ss2, the processing by the wingman is avx:
https://lhcathome.cern.ch/lhcathome/workunit.php?wuid=83956370

what also catches my eye is that the application name is shown as "SixTrack v46.30 (sse2) windows_intelx86" - which obviously means that it is 32-bit, not 64-bit; right?
in contrast to this, for the wingman's PC with AVX, the application name is shown as "SixTrack v46.30 (avx) windows_x86_64" - which means 64-bit

Edit: I now checked several other finished tasks waiting for validation, and in ALL cases the wingman's application is avx, mine is sse2.
So, something seems strange.

This is what i see on my computer:

20/01/2018 09:01:45 | LHC@home | Started upload of w-c2_job.B1inj_c2.2158__23__s__64.28_59.31__11.1_12.1__6__24_1_sixvf_boinc13712_0_r471927011_0
20/01/2018 09:01:45 | LHC@home | Started upload of w-c2_job.B1inj_c2.2158__28__s__64.28_59.31__7.1_8.1__6__57_1_sixvf_boinc18808_1_r1137666119_0
20/01/2018 09:01:48 | LHC@home | [error] Error reported by file upload server: [w-c2_job.B1inj_c2.2158__23__s__64.28_59.31__11.1_12.1__6__24_1_sixvf_boinc13712_0_r471927011_0] locked by file_upload_handler PID=-1
20/01/2018 09:01:48 | LHC@home | [error] Error reported by file upload server: [w-c2_job.B1inj_c2.2158__28__s__64.28_59.31__7.1_8.1__6__57_1_sixvf_boinc18808_1_r1137666119_0] locked by file_upload_handler PID=-1
20/01/2018 09:01:48 | LHC@home | Temporarily failed upload of w-c2_job.B1inj_c2.2158__23__s__64.28_59.31__11.1_12.1__6__24_1_sixvf_boinc13712_0_r471927011_0: transient upload error
20/01/2018 09:01:48 | LHC@home | Backing off 04:10:47 on upload of w-c2_job.B1inj_c2.2158__23__s__64.28_59.31__11.1_12.1__6__24_1_sixvf_boinc13712_0_r471927011_0
20/01/2018 09:01:48 | LHC@home | Temporarily failed upload of w-c2_job.B1inj_c2.2158__28__s__64.28_59.31__7.1_8.1__6__57_1_sixvf_boinc18808_1_r1137666119_0: transient upload error
20/01/2018 09:01:48 | LHC@home | Backing off 04:24:47 on upload of w-c2_job.B1inj_c2.2158__28__s__64.28_59.31__7.1_8.1__6__57_1_sixvf_boinc18808_1_r1137666119_0



https://boincstats.com/signature/-1/user/3640163/sig.png

In Boinc data folder (default place in windows is c:\ProgramData\BOINC, may be a hidden folder) there are two files which contain the Boinc messages: stdoutdae.txt and stdoutdae.old. You can copy them to another folder and view their content there (doing it like this you don't accidentally lock the files and disable boinc writing in them).

---

Dear all,
can we continue the discussion on avx in its original thread:
https://lhcathome.cern.ch/lhcathome/forum_thread.php?id=4581
Thanks!
Cheers,
A.