Error after 14sec / Gamma-ray pulsar binary search #1 on GPUs v1.18

Forums › Problems and Bug Reports

Peter Baetz
Peter Baetz
Joined: 25 Feb 05
Posts: 12
Credit: 39980380
RAC: 0
30 Dec 2017 16:45:23 UTC
Topic 212287
(moderation:
    )

    Hallo,

    After ~ 14sec the app finish with a error:

    Gamma-ray pulsar binary search #1 on GPUs v1.18 (FGRPopencl1K-ati) x86_64-pc-linux-gnu

    LATeah0049L_1100.0_0_0.0_13090905_1

    Job ID: 330291313
    Erstellt: 30 Dez 2017 15:42:17 GMT
    Gesendet: 30 Dez 2017 16:09:01 GMT
    Ablaufdatum: 13 Jan 2018 16:09:01 GMT
    Empfangen: 30 Dez 2017 16:13:56 GMT
    Serverstatus: Over
    Resultat: Computation error
    Clientstatus: Compute error
    Endstatus: 69 (0x00000045) Unknown error code
    Computer: 4867904
    Run time (sec): 14.14
    CPU time (sec): 0.78
    Peak working set size (MB): 70.81
    Peak swap size (MB): 166.58
    Peak disk usage (MB): 0.02
    Prüfungsstatus: Invalid
    Gewährte Punkte: 0
    Anwendung: Gamma-ray pulsar binary search #1 on GPUs v1.18 (FGRPopencl1K-ati) x86_64-pc-linux-gnu
     

    Stderr output

    <core_client_version>7.4.22</core_client_version>
<![CDATA[
<message>
process exited with code 69 (0x45, -187)
</message>
<stderr_txt>
17:10:35 (9106): [normal]: This Einstein@home App was built at: Jan 16 2017 08:09:16

    17:10:35 (9106): [normal]: Start of BOINC application '../../projects/einstein.phys.uwm.edu/hsgamma_FGRPB1G_1.18_x86_64-pc-linux-gnu__FGRPopencl1K-ati'.
    17:10:35 (9106): [debug]: 1e+16 fp, 2e+09 fp/s, 5124443 s, 1423h27m23s00
    command line: ../../projects/einstein.phys.uwm.edu/hsgamma_FGRPB1G_1.18_x86_64-pc-linux-gnu__FGRPopencl1K-ati --inputfile ../../projects/einstein.phys.uwm.edu/LATeah0049L.dat --alpha 4.42281478648 --delta -0.0345027837249 --skyRadius 2.152570e-06 --ldiBins 15 --f0start 1092.0 --f0Band 8.0 --firstSkyPoint 0 --numSkyPoints 1 --f1dot -1e-13 --f1dotBand 1e-13 --df1dot 3.344368011e-15 --ephemdir ../../projects/einstein.phys.uwm.edu/JPLEPH --Tcoh 2097152.0 --toplist 10 --cohFollow 10 --numCells 1 --useWeights 1 --Srefinement 1 --CohSkyRef 1 --cohfullskybox 1 --mmfu 0.1 --reftime 56100 --model 0 --f0orbit 0.005 --mismatch 0.1 --demodbinary 1 --BinaryPointFile ../../projects/einstein.phys.uwm.edu/templates_LATeah0049L_1100_13090905.dat --debug 1 --device 0 -o LATeah0049L_1100.0_0_0.0_13090905_1_0.out
    output files: 'LATeah0049L_1100.0_0_0.0_13090905_1_0.out' '../../projects/einstein.phys.uwm.edu/LATeah0049L_1100.0_0_0.0_13090905_1_0' 'LATeah0049L_1100.0_0_0.0_13090905_1_0.out.cohfu' '../../projects/einstein.phys.uwm.edu/LATeah0049L_1100.0_0_0.0_13090905_1_1'
    17:10:35 (9106): [debug]: Flags: X64 SSE SSE2 GNUC X86 GNUX86
    17:10:35 (9106): [debug]: glibc version/release: 2.22/stable
    17:10:35 (9106): [debug]: Set up communication with graphics process.
    boinc_get_opencl_ids returned [0x19cb668 , 0x7f289d0ef800]
    Using OpenCL platform provided by: Mesa
    Using OpenCL device "AMD TURKS (DRM 2.43.0 / 4.4.103-18.41-default, LLVM 6.0.0)" by: AMD
    Max allocation limit: 751619276
    Global mem size: 1073741824
    OpenCL compiling FAILED! : -11 . Error message: input.cl:7:26: error: unsupported OpenCL extension 'cl_khr_fp64' - ignoring
    input.cl:10:30: error: unknown type name 'double2'; did you mean 'double'?
    input.cl:10:30: error: use of type 'double' requires cl_khr_fp64 extension to be enabled

    OpenCL device has no FP64 support
    OpenCL compiling FAILED! : -11 . Error message: <unknown>:0:0: in function kernel_ts_2_phase_diff_sorted void (float addrspace(1)*, i32, %struct.PhotonPair addrspace(1)*, i32, i32, float, i32, %struct.Bloc_info addrspace(1)*, i32): unsupported call to function llvm.AMDGPU.barrier.local

    Couldn't compile OpenCL kernels (error: 1)
    initialize_ocl returned error [2006]
    OCL context null
    OCL queue null
    Error generating generic FFT context object [5]
    17:10:36 (9106): [CRITICAL]: ERROR: MAIN() returned with error '5'
    FPU status flags:
    mv: der Aufruf von stat f&#195;&#188;r 'LATeah0049L_1100.0_0_0.0_13090905_1_0.out' ist nicht m&#195;&#182;glich: Datei oder Verzeichnis nicht gefunden
    mv: der Aufruf von stat f&#195;&#188;r 'LATeah0049L_1100.0_0_0.0_13090905_1_0.out' ist nicht m&#195;&#182;glich: Datei oder Verzeichnis nicht gefunden
    mv: der Aufruf von stat f&#195;&#188;r 'LATeah0049L_1100.0_0_0.0_13090905_1_0.out' ist nicht m&#195;&#182;glich: Datei oder Verzeichnis nicht gefunden
    mv: der Aufruf von stat f&#195;&#188;r 'LATeah0049L_1100.0_0_0.0_13090905_1_0.out' ist nicht m&#195;&#182;glich: Datei oder Verzeichnis nicht gefunden
    mv: der Aufruf von stat f&#195;&#188;r 'LATeah0049L_1100.0_0_0.0_13090905_1_0.out' ist nicht m&#195;&#182;glich: Datei oder Verzeichnis nicht gefunden
    mv: der Aufruf von stat f&#195;&#188;r 'LATeah0049L_1100.0_0_0.0_13090905_1_0.out.cohfu' ist nicht m&#195;&#182;glich: Datei oder Verzeichnis nicht gefunden
    mv: der Aufruf von stat f&#195;&#188;r 'LATeah0049L_1100.0_0_0.0_13090905_1_0.out.cohfu' ist nicht m&#195;&#182;glich: Datei oder Verzeichnis nicht gefunden
    mv: der Aufruf von stat f&#195;&#188;r 'LATeah0049L_1100.0_0_0.0_13090905_1_0.out.cohfu' ist nicht m&#195;&#182;glich: Datei oder Verzeichnis nicht gefunden
    mv: der Aufruf von stat f&#195;&#188;r 'LATeah0049L_1100.0_0_0.0_13090905_1_0.out.cohfu' ist nicht m&#195;&#182;glich: Datei oder Verzeichnis nicht gefunden
    mv: der Aufruf von stat f&#195;&#188;r 'LATeah0049L_1100.0_0_0.0_13090905_1_0.out.cohfu' ist nicht m&#195;&#182;glich: Datei oder Verzeichnis nicht gefunden
    mv: der Aufruf von stat f&#195;&#188;r 'LATeah0049L_1100.0_0_0.0_13090905_1_0.out.cohfu' ist nicht m&#195;&#182;glich: Datei oder Verzeichnis nicht gefunden
    mv: der Aufruf von stat f&#195;&#188;r 'LATeah0049L_1100.0_0_0.0_13090905_1_0.out.cohfu' ist nicht m&#195;&#182;glich: Datei oder Verzeichnis nicht gefunden
    17:10:48 (9106): [normal]: done. calling boinc_finish(69).
    17:10:48 (9106): called boinc_finish

    </stderr_txt>
    ]]>

     

    Could anybody help me?

     

    Peter

    Gary Roberts
    Gary Roberts
    Moderator
    Joined: 9 Feb 05
    Posts: 5872
    Credit: 117718805673
    RAC: 35006027

    Peter Baetz

    30 Dec 2017 22:25:29 UTC
    Message 163610
    (moderation:
      )

      Peter Baetz wrote:

      ....
Using OpenCL platform provided by: Mesa
Using OpenCL device "AMD TURKS (DRM 2.43.0 / 4.4.103-18.41-default, LLVM 6.0.0)" by: AMD
Max allocation limit: 751619276
Global mem size: 1073741824
OpenCL compiling FAILED! : -11 . Error message: input.cl:7:26: error: unsupported OpenCL extension 'cl_khr_fp64' - ignoring
input.cl:10:30: error: unknown type name 'double2'; did you mean 'double'?
input.cl:10:30: error: use of type 'double' requires cl_khr_fp64 extension to be enabled

      OpenCL device has no FP64 support
OpenCL compiling FAILED! : -11 . Error message: <unknown>:0:0: in function kernel_ts_2_phase_diff_sorted void (float addrspace(1)*, i32, %struct.PhotonPair addrspace(1)*, i32, i32, float, i32, %struct.Bloc_info addrspace(1)*, i32): unsupported call to function llvm.AMDGPU.barrier.local

      Couldn't compile OpenCL kernels (error: 1)
initialize_ocl returned error [2006]
OCL context null
OCL queue null
Error generating generic FFT context object [5]
17:10:36 (9106): [CRITICAL]: ERROR: MAIN() returned with error '5'
....

       

      Could anybody help me?

      I really know very little about Mesa/LLVM as I've never tried to use it. The comments that follow are just guesses.  If I'm not stating things correctly, I'd appreciate being corrected by someone who knows more about this than I do.

      Firstly, your device is seen as 'TURKS' which is relatively old - Wikipedia tells me it's something like a HD6570 or HD6670, etc.  It has just enough VRAM (1GB) to allow the scheduler to send tasks for it but in the snip above you can see that the card itself doesn't have FP64 support which means that part of the calculations requiring double precision would be performed on the CPU rather than the GPU.  In itself that doesn't stop tasks being crunched - just slows them down.

      As I understand it, Mesa/LLVM is a work in progress to provide (amongst other things) support for hardware not directly supported by AMD's latest amdgpu/amdgpu-pro drivers.  The above snip makes it fairly clear that for the versions of Mesa/LLVM you are using, your card is not properly supported.

      Previously, cards that did have OpenCL capability were supported by the proprietary fglrx driver which has been deprecated.  fglrx would probably allow your card to crunch (just a guess) but is incompatible with recent versions of xorg.  To use fglrx, you would need to install an old enough version of your OS to have the 1.17.x version of xorg.  Later versions won't allow fglrx to be used.

      I have essentially the same problem.  I use lots of cards that work fine with fglrx so (for those cards - mainly Pitcairn series, a few Cape Verde and Tahiti) I've controllled my OS upgrades to allow fglrx to continue working.  I do this on the assumption that there will eventually be support developed for them.  Maybe they'll all die of old age before that happens :-).

      For your particular situation, since your machine has a nice new Ryzen 7 CPU, shout yourself a late Christmas present and upgrade your GPU to a basic Polaris series card :-).  Something like an RX 460 (if you can find one cheaply) or an RX 560 (just a little faster - not much) would do nicely without breaking the bank :-).  I'm running versions of both that don't need PCIe power connectors so don't consume much power - probably little more than your old card.  The output is good for the power used.

      Otherwise, I suspect you'll be waiting a long time for your card to be properly supported, if ever.

       

      Cheers,
      Gary.

      Peter Baetz
      Peter Baetz
      Joined: 25 Feb 05
      Posts: 12
      Credit: 39980380
      RAC: 0

      Thanks for your very good

      31 Dec 2017 9:03:51 UTC
      Message 163621 in response to message 163610
      (moderation:
        )

        Thanks for your very good comment. Yes, for some months I had updated my OS without thinking to the fglrx-problem (I did not know about it).

        Your are right, and I will bought a RX560. (next year) ;-)

        Cheers,

        Peter

         

         

         

        Comment viewing options

        Select your preferred way to display the comments and click "Save settings" to activate your changes.

        Forums › Problems and Bug Reports