Re: [Flightgear-devel] FlightGear freezes (float point interrupt)

2005-08-20 Thread Ampere K. Hardraade
I believe I have fixed my freezing problem by removing Xorg and moving back to 
XFree.

Ampere

___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d


Re: [Flightgear-devel] FlightGear freezes (float point interrupt)

2005-08-17 Thread David Luff
Ampere K. Hardraade writes:

 Lately, my computer has been freezing on me unpredictably while I am using 
 FlightGear.  (Note: I'm not saying FlightGear is to blame.)  Normally, I just 
 cold boot the machine.  Today however, after multiple freezes, I was too 
 angry to try again.  I went away to do other things, and when I came back, 
 FlightGear seems to got killed by the kernel.  When I relaunch FlightGear 
 later, I got a lot of this:
 
 Floating point interrupt (SIGFPE)
 
 Unfortunately, this was the only message I've got.  
 
 I start FlightGear using the following command:
 /usr/local/FlightGear/bin/fgfs 
 --fg-scenery=/usr/local/FlightGear/data/FlightGear/Scenery-0.9.8 
 --aircraft=b1900d --airport=KSAC --bpp=24 --geometry=1280x600 --fov=69.9 
 --multiplay=out,10,81.169.158.37,5002 --multiplay=in,10,192.168.0.194,5002 
 --callsign=AMPERE --enable-real-weather-fetch --enable-clouds3d
 

A real stab in the dark this, but I solved a lot of random freezes in opengl 
apps and internal compiler errors from gcc by clearing a layer of compacted 
dust from the cpu cooler (Athlon).

Alternatively, does FG freeze when you start it without all the options above?

Cheers - Dave

___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d


Re: [Flightgear-devel] FlightGear freezes (float point interrupt)

2005-08-17 Thread Andy Ross
Ampere K. Hardraade wrote:
 Lately, my computer has been freezing on me unpredictably while I am using
 FlightGear.  (Note: I'm not saying FlightGear is to blame.)  Normally, I just
 cold boot the machine.  Today however, after multiple freezes, I was too
 angry to try again.  I went away to do other things, and when I came back,
 FlightGear seems to got killed by the kernel.  When I relaunch FlightGear
 later, I got a lot of this:

 Floating point interrupt (SIGFPE)

This sounds to me a lot like a hardware problem.  Can you make it
happen when running other 3D applications?  Have you tried
memtest86?

Andy

___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d


Re: [Flightgear-devel] FlightGear freezes (float point interrupt)

2005-08-17 Thread Ampere K. Hardraade
On August 17, 2005 04:55 am, David Luff wrote:
 Alternatively, does FG freeze when you start it without all the options
 above?

 Cheers - Dave

It seems to.

Ampere

___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d


Re: [Flightgear-devel] FlightGear freezes (float point interrupt)

2005-08-17 Thread Ampere K. Hardraade
On August 17, 2005 10:02 am, Andy Ross wrote:
 This sounds to me a lot like a hardware problem.  Can you make it
 happen when running other 3D applications?  Have you tried
 memtest86?

 Andy

I think I reproduced it by increasing CPU load (ie. loading other 
applications).  As for memtest86, I do not know how to use the program.

Ampere

___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d


Re: [Flightgear-devel] FlightGear freezes (float point interrupt)

2005-08-17 Thread Ivo
On Thursday 18 August 2005 05:19, Ampere K. Hardraade wrote:
 On August 17, 2005 10:02 am, Andy Ross wrote:
  This sounds to me a lot like a hardware problem.  Can you make it
  happen when running other 3D applications?  Have you tried
  memtest86?
 
  Andy

 I think I reproduced it by increasing CPU load (ie. loading other
 applications).

This sounds like a heat problem. Check your CPU temperature right after the 
crash. How hot is it?

AMD (that's what I'm using) specs say they can go up to 85 or 90 degrees C 
(depends on the model), but I ran into trouble at about 70-75 degrees.

(Don't laugh, I had mounted my heatsink the wrong way around by mistake, 
there was almost no thermal paste between the cpu core and the heatsink. 
That had never happened to me before, and I have built quite a lot of 
systems in the past ten years.)

  As for memtest86, I do not know how to use the program.

Download the iso image, burn it to a cd, boot from it and let it run all 
tests (may take a while).

--Ivo


___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d


[Flightgear-devel] FlightGear freezes (float point interrupt)

2005-08-16 Thread Ampere K. Hardraade
Lately, my computer has been freezing on me unpredictably while I am using 
FlightGear.  (Note: I'm not saying FlightGear is to blame.)  Normally, I just 
cold boot the machine.  Today however, after multiple freezes, I was too 
angry to try again.  I went away to do other things, and when I came back, 
FlightGear seems to got killed by the kernel.  When I relaunch FlightGear 
later, I got a lot of this:

Floating point interrupt (SIGFPE)

Unfortunately, this was the only message I've got.  

I start FlightGear using the following command:
/usr/local/FlightGear/bin/fgfs 
--fg-scenery=/usr/local/FlightGear/data/FlightGear/Scenery-0.9.8 
--aircraft=b1900d --airport=KSAC --bpp=24 --geometry=1280x600 --fov=69.9 
--multiplay=out,10,81.169.158.37,5002 --multiplay=in,10,192.168.0.194,5002 
--callsign=AMPERE --enable-real-weather-fetch --enable-clouds3d


Ampere

___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d