Linux x64 AP v5.05

[sunu]

I see you're using kernel 2.6.28-15-generic, this is the ubuntu 9.04 kernel right? For some reason, this kernel isn't good for running lunatics's optimised apps. Revert back to 8.10's kernel (2.6.27-14) or build your own.

[lordvader]

Yeah, it's ubuntu.

Don't have any issues with other apps (the CUDA apps crunch fine ...).

Surely a kernel I build myself will be pretty much identical though ?

[sunu]

Surely a kernel I build myself will be pretty much identical though ?

Not necessarily.

I don't know if this bug exists in ubuntu's compiled kernel or 2.6.28 in general. Other people with the same problem, compiling their own newer kernel (2.6.29, 2.6.30) had this problem go away. I haven't bothered with compiling my own kernel, I'm running 9.04 with 8.10's 2.6.27-14 kernel.

[Urs Echternacht]

I don't think you can run it on the main board yet, it is only for the Beta at the moment.

Yes, build and packaged (app_info.xml) for Beta.

[Urs Echternacht]

So I've been running AP overnight. 4 units completed, none validated, but 1 did fail with a computation error :

http://setiathome.berkeley.edu/result.php?resultid=1339606984
http://setiathome.berkeley.edu/result.php?resultid=1339613053

Hopefully there's some info in there for debug. My CPU isn't overclocked, and isn't overheating, so it's probably not that. It may be a completely random error though ...

*EDIT*
2 computarion errors.

Is this the best place to report these errors ?

Many thanks for beta testing this application version.

The best and preferred place for reports is the forum thread where you find the AP apps.

These error looks pretty similar to that one which was seen with previous (v5.03) versions and exactly this 2.6.28 kernel. Hopefully the trace contains enough hints to find out why it fails.

If you don't mind, could you try the other application version as well ?

[lordvader]

I'll try that tomorrow.

At the moment I'm trying the SSE3 version on a 2.6.30 kernel, just wanna make sure that works.

... by other version, you mean the SSE2 only version, correct ? Which kernel ? The 2.6.28 one ?

[Urs Echternacht]

I'll try that tomorrow.

At the moment I'm trying the SSE3 version on a 2.6.30 kernel, just wanna make sure that works.

... by other version, you mean the SSE2 only version, correct ? Which kernel ? The 2.6.28 one ?

If 2.6.30 works for you without errors, that would at least proove that 2.6.28 has to be excluded from support, similar to kernel versions before 2.6.22.

Yes, the AMD64 SSE2 version. If possible, run a few wus on each kernel, to see if there will occur other problems. Thanks in advance.

ps: your first wu has validated. ++

[lordvader]

I'll keep posting here, as this seems the more active thread

The vanilla 2.6.28 kernel also resulted in errors, so I don't think its an ubuntu thing.
The SSE2 client seemed to work fine, but when I switched back to SSE3, the executable wasn't in the folder, and I lost my cache of AP units !!! Bugger !

I'm going to try the 2.6.31rc6 kernel, with the new nvidia drivers, see if I can hit the middle ground of stable AP, and fast CUDA.

[Urs Echternacht]

I'll keep posting here, as this seems the more active thread

The vanilla 2.6.28 kernel also resulted in errors, so I don't think its an ubuntu thing.
The SSE2 client seemed to work fine, but when I switched back to SSE3, the executable wasn't in the folder, and I lost my cache of AP units !!! Bugger !

I'm going to try the 2.6.31rc6 kernel, with the new nvidia drivers, see if I can hit the middle ground of stable AP, and fast CUDA.

The only reported errors after one week into beta testing are yours (Ubuntu 9.04, kernel version 2.6.28+), lordvader. A big thank you for your efforts.

Anyone else has results to report ?

ps: stock astropulse seems not to play well on that os/kernel, too.

[Tye]

On the AMD client, I get mostly good runs, one error.  But, they all had very low claimed credit:

Task ID
click for details
Show names   Work unit ID
click for details   Sent   Time reported
or deadline
explain   Status   Run time (sec)   claimed credit   granted credit
6627643   2282517   19 Aug 2009 23:36:57 UTC   20 Aug 2009 0:08:22 UTC   Completed, validation inconclusive   1,286.88   3.13   pending
6627635   2282513   19 Aug 2009 23:28:59 UTC   20 Aug 2009 0:02:44 UTC   Completed, waiting for validation   396.70   0.97   pending
6627619   2282505   19 Aug 2009 23:13:26 UTC   19 Aug 2009 23:28:59 UTC   Completed, validation inconclusive   161.91   0.38   pending
6627609   2282500   20 Aug 2009 0:08:22 UTC   14 Sep 2009 0:08:22 UTC   In progress   ---   ---   ---
6627595   2282493   20 Aug 2009 0:02:44 UTC   20 Aug 2009 9:14:29 UTC   Completed, waiting for validation   291.70   0.68   pending
6627490   2282443   19 Aug 2009 23:16:42 UTC   19 Aug 2009 23:36:57 UTC   Completed, validation inconclusive   636.87   1.55   pending
6624580   2281948   17 Aug 2009 21:22:49 UTC   18 Aug 2009 15:26:25 UTC   Error while computing   2,295.81   8.93   8.93

[Urs Echternacht]

On the AMD client, I get mostly good runs, one error.  But, they all had very low claimed credit:

Task ID
click for details
Show names   Work unit ID
click for details   Sent   Time reported
or deadline
explain   Status   Run time (sec)   claimed credit   granted credit
6627643   2282517   19 Aug 2009 23:36:57 UTC   20 Aug 2009 0:08:22 UTC   Completed, validation inconclusive   1,286.88   3.13   pending
6627635   2282513   19 Aug 2009 23:28:59 UTC   20 Aug 2009 0:02:44 UTC   Completed, waiting for validation   396.70   0.97   pending
6627619   2282505   19 Aug 2009 23:13:26 UTC   19 Aug 2009 23:28:59 UTC   Completed, validation inconclusive   161.91   0.38   pending
6627609   2282500   20 Aug 2009 0:08:22 UTC   14 Sep 2009 0:08:22 UTC   In progress   ---   ---   ---
6627595   2282493   20 Aug 2009 0:02:44 UTC   20 Aug 2009 9:14:29 UTC   Completed, waiting for validation   291.70   0.68   pending
6627490   2282443   19 Aug 2009 23:16:42 UTC   19 Aug 2009 23:36:57 UTC   Completed, validation inconclusive   636.87   1.55   pending
6624580   2281948   17 Aug 2009 21:22:49 UTC   18 Aug 2009 15:26:25 UTC   Error while computing   2,295.81   8.93   8.93

[/size]
Are you sure you had the optimized version running on that error. I have checked the task id :

Code: [Select]

<core_client_version>6.6.11</core_client_version>
<![CDATA[
<message>
process got signal 11
</message>
<stderr_txt>
In ap_gfx_main.cpp: in ap_graphics_init(): Starting client.
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 896
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 1024
SIGSEGV: segmentation violation

</stderr_txt>
]]>This is the stock astropulse 5.06 application having an error not the optimized one. All of your results, Tye, look like that.

If you have problems with the installation instructions that were included in the optimized package, please ask for help in this forum. There are a few people here that can assist you through the installation process.

The low claimed credts are due to very low runtimes because of early finishing with "Found 30 single pulses and 30 repeating pulses, exiting."

[Tye]

You're right - that was 2 days before I switched.  The others should be with the new client, or at least the ones 20 Aug and later.  It shows up in top and ps with the correct client and has since I installed it.  Hmmm.  I'll check more after work tonight.

[Tye]

Aha, it turned out I hadn't completed any yet.  Just submitted one right now manually and it looks good:

http://setiweb.ssl.berkeley.edu/beta/result.php?resultid=6627609

[Urs Echternacht]

Aha, it turned out I hadn't completed any yet.  Just submitted one right now manually and it looks good:

http://setiweb.ssl.berkeley.edu/beta/result.php?resultid=6627609

Thanks Tye, that one looks indeed like the right thing. 

[lordvader]

I was wondering if the AP issues exist under kernel 2.6.27 ?

Moving to kernel 2.6.30 won't cut it, as CUDA performance in abysmal, and the AP failure rate in 2.6.28 is just horrible.
I haven't tried 2.6.29 though ...