E@H on linux kernel 2.6.9 and AMD64 3000
Anonymous
28 Dec 2004 3:33:59 UTC
Topic 10647
(moderation:
> I just re-attached my AMD64 3000. When I do a top command, it does not show
> that E@H is running. The cpu utilization is at 99% however. And when I do a ps
> -Al it showes E@H as one of the processes but it is sleeping. If I kill E@H
> then the cpu goes to 100% idle so it is running. This is what happened before.
> I am using the new E@H client, 4.68. This is what happened before on the older
> E@H client, then after a while E@H quits running and the cpu goes to idle and
> does not start S@H.
> I'll let it run over night to see what happens.
>
> E@H does run correctly on the older linux kernel, 2.4.x
James, can you please use 'strace -p PID' to poke at the
'sleeping' process and see what it's up to.
Bruce
E@H on linux kernel 2.6.9 and AMD64 3000
)
Got some similar behaviour. Machine is running kernel 2.6.8.
After starting the boinc core client (4.13) and the usual benchmarks,
there will be two (dual-CPU machine!) einstein apps in Z state.
It is impossible to attach a strace to any of them.
Restarting from scratch will not help.
The last message I can see is "Restarting result..." using version 4.68.
Any ideas?
It looks like BOINC is trying
)
It looks like BOINC is trying to determine if your machine is running on batteries or not! Do you have 'battery/laptop' preferences set? If so, could you try changing them, please, and tell me if it does anything?
Cheers,
Bruce
Hi, running kernel 2.6.8
)
Hi,
running kernel 2.6.8 here on a rackmount machine. The boinc client will go into
the same loop (but it would do so on any machine I suppose), and there are two
"zombie" processes (it's a dual Xeon machine) which would disappear if the boinc
client was killed. The zombies of course can't be straced...
The strange thing is that although no process seems to do real work, there's
still progress being made : the numbers in client_state.xml *do*
change.
This is strange, and I only see it with a 2.6 machine (I'm running another one
with basically the same Debian installation but kernel 2.4.xy so don't blame
Debian).
Unfortunately it took some time to find out (I wrote a watcher script to keep
track of the machines), so I dropped a lot of workunits that would have been
useful otherwise.
Since the WU is a pt* one at the moment, it will take some time to reach 99%,
I'm a bit curious what would happen next...
Cheers,
Steffen