Message boards :
Number crunching :
process exited with code 22
Message board moderation
Author | Message |
---|---|
Send message Joined: 8 Feb 10 Posts: 23 Credit: 513,143,911 RAC: 0 |
All my AMD GPU WUs now immediately error out with error code 22. Does anybody have an idea what is causing that? I ran MW successfully before and as far as I know nothing changed on my machines. I am running openSUSE 12.2 and BOINC 7.0.65. |
Send message Joined: 8 Feb 10 Posts: 23 Credit: 513,143,911 RAC: 0 |
Never mind, I already figured it out. This is an old bug in the milkyway_separation_0.82_x86_64-pc-linux-gnu__ati14 binary. It is 64-bit, but erroneously expects ld-linux-x86-64.so.2 to be in /lib/ld-linux-x86-64.so.2. This should be /lib64/ld-linux-x86-64.so.2. Creating a symlink /lib/ld-linux-x86-64.so.2 -> /lib64/ld-linux-x86-64.so.2 will fix this, but it would be better if you fixed the binary... |
Send message Joined: 8 Feb 08 Posts: 261 Credit: 104,050,322 RAC: 0 |
Both of your gpus are able to run the newer openCL version 1.02 instead of the old CAL version 0.82. |
Send message Joined: 8 Feb 10 Posts: 23 Credit: 513,143,911 RAC: 0 |
Well, there is something weird going on here. If you look on the website (the overview of tasks), it claims that the WUs are done with client v1.02, but if you look in the output it identifies itself as client v0.82. If I look at the running processes on my machines, I see the v0.82 client running. This is certainly not necessary as I ran v1.02 successfully in the past... I am now also getting invalid WUs. I never had those in the past. It says: "Validate state: Workunit error - check skipped". I don't see anything in the output that suggests an error though... |
Send message Joined: 27 Feb 13 Posts: 2 Credit: 1,092,978 RAC: 0 |
I was having the same problem and I can confirm the symlink trick works! :) The exact command is: sudo ln -s /lib64/ld-linux-x86-64.so.2 /lib/ld-linux-x86-64.so.2 It helped me with both v0.82 and this new v1.02 (ati14). Previously (until last week) all my GPU tasks were v1.02 (opencl_amd_ati). Not sure why server started sending me (ati14) instead of (opencl_amd_ati) tho... my card is OpenCL compatible and worked fine for months. The OpenCL version is also much more responsive than the ati14 (is it CAL?), I could run the GPU jobs while using the desktop just fine, now I can only run whenn PC is idle. |
©2024 Astroinformatics Group