Exactly the point - the most common causes of seg faults
are hardware (bad memory, mb, etc.) so that's where I look
first. I had one system that seg faulted like crazy and I
couldn't figure it out. Later it started working with no
problem. I finally but things together. When I first
started the system up it took forever (72+ hours to
compile what should have been done in 8 hours) and would
start making beeping noises. I found that neither of the
case fans had been hooked up so the dual Intels were
temperature limiting (at least that worked!). I connected
the fans and the system ran at normal speed - and I
haven't seen a segfault since even with heavy usage.
n Mon, 9 Jun 2003 21:15:04 +0100
Tom Wesley <[EMAIL PROTECTED]> wrote:
On Monday 09 June 2003 21:07, Josh Helmer wrote:
On Monday 09 June 2003 09:22 am, brett holcomb wrote:
> Just because Windows doesn't seg fault doesn't mean
Oddly enough I had some fun with a slightly dodgy
compiled kernel module that
was the result of some over warm RAM on a hot day.
Caused all manner of
problems, I had to let the system cool and recompile the
kernel again and all
has been fine since.
--
Tom Wesley
Please encrypt personal replies if possible.
--
[EMAIL PROTECTED] mailing list
