Gfx engine crash

New Message Reply Date view Thread view Subject view Author view

Jean-Francois Richard (jfr++at++cae.ca)
Thu, 18 Nov 93 23:24:01 EST


During the last week, I have run the same Performer-based program
which makes heavy use of texture mapping on two different
Reality Engine platforms (a 420 RE running Irix 4.0.5H and an Onyx/4 RE2
running Irix 5.0.1). Everything is fine most of the time but
occasionally (once every couple of hours), the graphics freeze up
and die and I am thrown back to the login prompt without warning or
even a core dump.

After looking around, I did find the following cryptic messages in
/usr/adm/SYSLOG:

Nov 18 18:37:18 mesef_visual unix: GE4: Bad CP command encountered
Nov 18 18:37:18 mesef_visual unix: GE5: Bad CP command encountered
Nov 18 18:37:18 mesef_visual unix: GE5: Bad CP command order
Nov 18 18:37:18 mesef_visual unix: GE5: Bad CP command encountered
Nov 18 18:37:18 mesef_visual unix: GE5: Bad CP command order
Nov 18 18:37:18 mesef_visual unix: GE6: Bad CP command encountered
Nov 18 18:37:18 mesef_visual unix: GE6: Bad CP command order
Nov 18 18:37:33 mesef_visual unix: WARNING: venice: lightweight deactivation timed out
Nov 18 18:37:33 mesef_visual unix: WARNING: venice: vcstage change timed out

I have seen Reality Engines do that before with pure GL programs
on Crimson RE and 420 RE platforms and have talked to people complaining
of similar problems. I was hoping that using Performer on a brand-new
Onyx running a brand-new OS (IRIX 5) would take care of the problem but
I was apparently mistaken.

Now, am I doing something wrong or is this a well-known problem with the
Reality Engine? Is this happening to anybody else?

---------------------------------------------------------------------------
   J.F. Richard
   CAE Electronics
---------------------------------------------------------------------------

   


New Message Reply Date view Thread view Subject view Author view

This archive was generated by hypermail 2.0b2 on Mon Aug 10 1998 - 17:50:06 PDT

This message has been cleansed for anti-spam protection. Replace '++at++' in any mail addresses with the '@' symbol.