Hi,
I'm not familiar with BSD's either since I never worked with
them, but I also suspected that maybe it is a CPU over-heat.
In my case, I was over-clocking a little bit but it was a
CYRIX 233 ( what'd you expect ;) ) and it mysteriously
kept going down.
Of course, I cant interpret oops logs so I left the situation
alone until I found a s*it load of dust clogging up the CPU
fan and heat sink, bringing it almost to a halt.
Man was that baby burnin' ;)
Cleaned it up, set jumpers back to default and all is
well now.
Since I'm on a maintenance-talk spree :) ---
Sometimes cheap RAM is known to be buggy.
Also, pluging/unpluging of cards/cables/ram etc helps since
corrosion builds up between the contacts over a period of
time and loses some conductivity (living here in Japan with
all this moist is a real killer).
cheers,
jamie
ps
maybe its an unknown virus that eats the cpu waffers
(just kidding...)
> > BSD is not my choice of OSes but a sig 11 in linux is commonly
> > a memory error, almost always a hardware error.
>
> It's also quite frequently a symptom of an overheated CPU, par-
> ticularly if it occurs randomly and is difficult to reproduce.
> If overclocking, you're that's the first place that I'd look.
#---------#---------#---------#---------#---------#---------#---------#
-- If somebody can help create a search engine for my room,
I will call them a Saint...
GUI == Graphical User Interference
