Mkay, this issue almost got somebody killed: I was strolling happily down to the basement to even more happily play with my computer when I to my horror realised that someone had moved the box!! It diddnt look like it had recieved any battering or anything but when I booted... ARGHH!!! HEADS will ROLL!:

"bla bla ok
blablb ok
configuring kernel parameters: ok
divide error: 0000
ext3 jbd
CPU 0
EIP: 0010:[<c0106e03>] Not tainted
EFLAGS: 00000246
EIP is at default_idle [kernel] 0x23 (2.4.18-3)

(a lot of other things that didnt make any sense (mostly numbers)

and finally:
<0> Kernel panic: attempted to kill the idle task!
In idle task-not syncing"

Now, I have NO idea whatsoever what happened or what the kernel panic means, i did however suspect either the motherboard or cpu to be toast... this wasnt the case (puhh...!) I booted with the red hat rescue cd, mounted my system and looked around, didnt tell me anything so I rebooted and BOOM! here I am writing this post on the very system that I yesterday centenced to eternal doom. (that made me drown my sorrows in beer (mmm.... beer ;D))! I didnt have time to fiddle with this untill today, told you bout the beer!!!
I suspected harware fault since the system behavied very strange pre bios and post bios (hangin, warning for improper cpu settings, in bios-setup everything was really running sluggish!)

Any thoughts comments or anything? I opened the box to try see if anything had been forced loose... nothing!

Cheers, Klod

I noticed now that the clock (not the system clock, or maybe... ) have been reset...

Anyone?? I still havent found out what has happened, although my time settings was changed back to: first of january 2000, at 00:00!!!

The 2000 bug is finally arriving... seriously, anyone?

Cheers, Klod

Just a wild guess. Are your batteries dead, missing, or disconnected?

well... since its working now I dont think so... ;D.
Maybe a glitch between the mobo and the battery or something?!!
Dont now if youre suspecting this box for being a laptop, it isnt!

Thanks for the reply!

Cheers, Klod

If I were you, I would check all the hard drive cables. I had
something like this happen to me . After a week of head scratching, I tried cleaning the connectors on the back of
the drives where the IDE cable plugs in. Miraculous recovery
for me too after that. Not a big pain to do but less then an
insane computer babbling at me. Season to taste if you are
running SATA drives. They can get cruddy too. One thing I have
learned, things rarely heal themselves for long and HAL9000 aint
in stores yet .