ME OS AMD Duron did this 6.09 task, all went well. Time 27:21:47
Had a look at the stderr output on your task and noticed this:
AllocateAndInitializeSid Error 120
failed to create shared mem segment
2008-12-08 03:10:37.1900 [normal]: WARNING: Couldn't set up communication with graphics process
Looks a bit odd.
Is it a problem with that machine or the app?
ME OS AMD Duron did this 6.09 task, all went well. Time 27:21:47
Had a look at the stderr output on your task and noticed this:
AllocateAndInitializeSid Error 120
failed to create shared mem segment
2008-12-08 03:10:37.1900 [normal]: WARNING: Couldn't set up communication with graphics process
Looks a bit odd.
Is it a problem with that machine or the app?
I'm assuming it's not a problem with the app or the pc, since it did that with 6.04 stock app. Never thoght of it as a problem since I don't use the graphics, but I always thought it had to do with the OS. I will admit though the graphics drivers for this pc are just what came on the cd for the MB.
I haven't seen this behavior before: beginning at skypoint 234 it goes all the way to skypoint 268 before it takes another checkpoint. After that, it goes from 269 to 288 before the next checkpoint. The rest seem more or less normal.
This was on a switch-over WU. The first 16 skypoints processed by 6.07, then switched to 6.09.
I haven't seen this behavior before: beginning at skypoint 234 it goes all the way to skypoint 268 before it takes another checkpoint. After that, it goes from 269 to 288 before the next checkpoint. The rest seem more or less normal.
This was on a switch-over WU. The first 16 skypoints processed by 6.07, then switched to 6.09.
Hmm...could this be related to Windows correcting the real-time clock setting from a time server at that tmoment during the computation?
ME OS AMD Duron did this 6.09
)
ME OS AMD Duron did this 6.09 task, all went well. Time 27:21:47
RE: ME OS AMD Duron did
)
Had a look at the stderr output on your task and noticed this:
Looks a bit odd.
Is it a problem with that machine or the app?
RE: RE: ME OS AMD Duron
)
I'm assuming it's not a problem with the app or the pc, since it did that with 6.04 stock app. Never thoght of it as a problem since I don't use the graphics, but I always thought it had to do with the OS. I will admit though the graphics drivers for this pc are just what came on the cd for the MB.
Finished another 6.09 task
)
Finished another 6.09 task AMD64 3800+ Time 12:59:24
Everything is working fine
)
Everything is working fine running Vista 64 bit Ultimate..............
Intel Q9300 Quadcore, 2500 Mhz, 4096 MB RAM, GeForce 9800 GT, Vista Ultimate 64-bit, Ubuntu 10.10 64 bit
One more ME 6.09 task
)
One more ME 6.09 task
I haven't seen this behavior
)
I haven't seen this behavior before: beginning at skypoint 234 it goes all the way to skypoint 268 before it takes another checkpoint. After that, it goes from 269 to 288 before the next checkpoint. The rest seem more or less normal.
This was on a switch-over WU. The first 16 skypoints processed by 6.07, then switched to 6.09.
Seti Classic Final Total: 11446 WU.
RE: I haven't seen this
)
Hmm...could this be related to Windows correcting the real-time clock setting from a time server at that tmoment during the computation?
CU
Bikeman
Just ran through 8 of these
)
Just ran through 8 of these with nary a glitch
http://einsteinathome.org/host/1618644
Go Celeron! Here is task
)
Go Celeron! Here is task 110603248 - the MMX/W98 testbed.
Started with v6.04, switched to v6.07 to test the 'rename checkpoint' bug, completed with v6.08 to confirm the bugfix. And validated!