> El Thu, Jun 30, 2005 at 08:44:40PM -0400, Jason Castonguay me dec?a: > > Hello list members. Greetings! Family keeps growing :)
On 2005-06-30 23:03:15 -0300 (Thu, Jun), Fernando Canizo wrote:
> To make it short: test your RAM.
OR/AND you may want to ensure that your machine has proper cooling: fan
is working, the radioator is properly fixed and is big enough (however with
500MHz cpu it need not be very big IMHO)
Compilation is said to be very intensive excercise for machine
internals, and in my case most hardware problems emerge while emerging :-)
Usually the result of cpu being too hot is hangup; anyway in your case
it may be compilation failure.
If that's the case and nothing helps you may try to interrupt the
compilation process with ctrl-z every few minutes
(I know - it's only for desperate ones) and wait until your cpu
calms down.
How to know the temperature? I am not sure, but you may test whether your
machine has something similiar to /proc/acpi/thermal_zone/ (in my case it's
/proc/acpi/thermal_zone/THM0/temperature file)
You may start a background process that logs temp, and check how much it
was when compilation failed:
$ while : ; do (date ; cat /proc/acpi/thermal_zone/THM0/temperature ) >>
/tmp/temperlog ; sleep 1; done &
I hope this helps a little... however I believe that your problems are
caused rather by bad RAM. (memtest/memtest86+ is your friend)
--
No virus found in this outgoing message.
Checked by 'grep -i virus $MESSAGE'
Trust me.
pgp2QzrB24vZr.pgp
Description: PGP signature
