Setiathome

[Taylor]

Ok this is really buring me up! I use to use the older 2.4(?) client. I am now using the 3.0 client with a test kernel (2.4.0-11).

I had no problems at all with this machine and the old client, but ever since I have upgraded to the new client my machine will randomly lockup or dump the kernel. This is really annoying. I can not keep the machine up more then 1-2 days it seems. This same machine use to run the old client and had uptimes w/ heavy usage of months. It never use to give me problems.

I did not participate in seti over the summer and would like to now that I can again but I am about to pull the plug on this crap and see if it makes a difference. I noticed that there are problems with the windows version of the 3.0 client. I wonder if there is not problems with the linux version as well!

Anyone else having problems?



------------------
-Taylor

[Taylor]

<begin rant>

OK I HAVE HAD IT!!!! F#@King SETI!!

I know it is seti now. The stuff spewed on the console proves it.

here is some of it, the more inportant info AFAIK!

"Unable to handle kernel NULL pointer dereference<1>Unable to handle kernel NULL pointer dereference at virtual address 00000018";

"Kernel panic: Attempted to kill the idle task!"

"Process setiathome (pid 111, stackpage=c9323000)
Stack...... lots of stacks"

So I say Fsck Seti!!!

Ok now that I got that out... I will try the older 2.4 client and if it works on my machine I will continue to use that. If not I will have to end my seti participation.

<end rant>

------------------
-Taylor