Message boards :
Number crunching :
CPU Work Units Did Not Validate
Message board moderation
Author | Message |
---|---|
Send message Joined: 22 Jan 09 Posts: 35 Credit: 46,731,190 RAC: 0 |
Just tried running a couple of test WUs using a new Linux machine. I have never run Milkyway before on this machine. I'm using the Linux 64 Bit optimized app from zslip.com. Both seemed to run to completion normally and gave no indication of errors in the BOINC Manager Message Logs but are both reported as Invalid with no credits received. Any help would be MUCH appreciated. Here is an example ... http://milkyway.cs.rpi.edu/milkyway/result.php?resultid=57525725 You will notice that the Outcome=Success but the Validate State=Invalid ??? |
Send message Joined: 29 Aug 07 Posts: 327 Credit: 116,463,193 RAC: 0 |
Not all P4's can do SSE3. You may have to use the SSE2 version. Calm Chaos Forum...Join Calm Chaos Now |
Send message Joined: 22 Jan 09 Posts: 35 Credit: 46,731,190 RAC: 0 |
I'll double check that, but I was using the SSE3 optimized app for Win 32 bit on this same hardware successfully. The only difference is I recently setup the machine for dual boot with Ubuntu 9.04 64 bit and ran these 2 WU's under that OS. I may have to revert to the stock app and run some tests that way because when I first ran Linux I immediately installed the opti app without first running the stock one. |
Send message Joined: 12 Nov 07 Posts: 2425 Credit: 524,164 RAC: 0 |
I'll double check that, but I was using the SSE3 optimized app for Win 32 bit on this same hardware successfully. The only difference is I recently setup the machine for dual boot with Ubuntu 9.04 64 bit and ran these 2 WU's under that OS. Are you using the win opti app or the correct linux app? Doesn't expecting the unexpected make the unexpected the expected? If it makes sense, DON'T do it. |
Send message Joined: 22 Jan 09 Posts: 35 Credit: 46,731,190 RAC: 0 |
I'll double check that, but I was using the SSE3 optimized app for Win 32 bit on this same hardware successfully. The only difference is I recently setup the machine for dual boot with Ubuntu 9.04 64 bit and ran these 2 WU's under that OS. Good question! Here's a result from the same machine running under the WinXP OS ... http://milkyway.cs.rpi.edu/milkyway/result.php?resultid=57396519 I'm preety sure that I'm using the Win opti-app for SSE3. On the Linux side I'm not so sure if I'm running the correct app or not, but I thought I picked Linux 64 bit SSE3 there as well. As I said I will have to double check that. |
Send message Joined: 14 Feb 09 Posts: 999 Credit: 74,932,619 RAC: 0 |
|
Send message Joined: 22 Jan 09 Posts: 35 Credit: 46,731,190 RAC: 0 |
I'll double check that, but I was using the SSE3 optimized app for Win 32 bit on this same hardware successfully. The only difference is I recently setup the machine for dual boot with Ubuntu 9.04 64 bit and ran these 2 WU's under that OS. OK, so even though I can run SSE3 apps on this chip running under WinXP, when I fired up the client running on Ubuntu 9.04 indeed it did not list SSE3 as a feature of my CPU, only SSE2. So now the question is, which app do I want? The 0.18 mkII marked for Linux 32 bit or the 0.18d (older) marked for Linux 32/64 bit. I'm running the 64 bit OS so as far as I can see it's a choice between one of these two but I'm not sure which one. |
Send message Joined: 22 Feb 08 Posts: 260 Credit: 57,387,048 RAC: 0 |
OK, so even though I can run SSE3 apps on this chip running under WinXP, when I fired up the client running on Ubuntu 9.04 indeed it did not list SSE3 as a feature of my CPU, only SSE2. So now the question is, which app do I want? open a root treminal, type cat /proc/cpuinfoand look if SSE3 will show up for the cpu. The 0.18 mkII marked for Linux 32 bit or the 0.18d (older) marked for Linux 32/64 bit. I'm running the 64 bit OS so as far as I can see it's a choice between one of these two but I'm not sure which one. I didn't make any 64bit SSE2 - assuming that any 64bit capable cpu is SSE3 capable. BTW, mkII or not doesn't really matter. mic. |
Send message Joined: 28 Apr 08 Posts: 1415 Credit: 2,716,428 RAC: 0 |
I had a problem running sse3 on my P4, although cpuid said it was sse3 capable, i put in sse2 & now it runs no problem. |
Send message Joined: 12 Oct 07 Posts: 77 Credit: 404,471,187 RAC: 0 |
open a root treminal, typecat /proc/cpuinfoand look if SSE3 will show up for the cpu. All is not lost if it doesn't show SSE3. In Linux some CPUs will list SSE3 as pni, so look for that too |
Send message Joined: 27 Aug 07 Posts: 647 Credit: 27,592,547 RAC: 0 |
|
Send message Joined: 17 Feb 08 Posts: 363 Credit: 258,227,990 RAC: 0 |
I have troubles with my Milkyway WUs on Linux, too. There's only one to blame for that, UBUNTU 9.04. Same happens on S@H when using optimized linux apps. Your only chance to get it working again is to get rid of 9.04 asap, it's simply broken crap. Join Support science! Joinc Team BOINC United now! |
Send message Joined: 27 Aug 07 Posts: 647 Credit: 27,592,547 RAC: 0 |
I have troubles with my Milkyway WUs on Linux, too. Arrgrgh.... that's no good news. :-( I don't want to install all again. *grumbles* PS. Which part of the "crap"@9.04 is exactly causing the troubles? *grin* Maybe there's a workaround so I don't have to re-install the whole OS... PS2: I have no troubles with Yoyo, DrugDiscovery, FreeHAL und ABC WUs. *scratches head* Lovely greetings, Cori |
Send message Joined: 14 Feb 09 Posts: 999 Credit: 74,932,619 RAC: 0 |
They are figuring it is in the Kernel. |
©2024 Astroinformatics Group