Re: Draw Lockup (was Performer Woes)

New Message Reply Date view Thread view Subject view Author view

Jean-Luc Dery (dery++at++Discreet.COM)
Tue, 28 Oct 1997 15:35:13 -0500


On Oct 28, 8:59am, Jan Barglowski wrote:
> Subject: Draw Lockup (was Performer Woes)
>
Rémi Arnaud wrote:
> > > Background:
> > > We upgraded from 1 to 3 Pipes on our iR. 2Gb RAM, Iris 6.2, and
> > > Performer 2.1. Processor locking and non-degrading priorities via
> > > the pfu calls worked well under 1 pipe, but now we cannot lock down
> > > the draw process without locking up (hard) the entire machine!
> >
> > Which means you are going from 1 draw process to 3 draw process (and
> > also from 1 cull to 3 culls if you run APP_CULL_DRAW).
> >
> > So the question is: do you have enough CPUs to handle 3 pipes with 3 draw
> > processes locked ?
>
> We have 16 processors, and I am currently locking them individually
> by number. However, perfly (which doesn't lock by number, but by
> next available?) crashes as well. It's only when the -D option in
> perfly is used that causes the lockup.
>
> jan

We are having the same problem on a 2 CPU Octane (IRIX 6.4), with a Performer
2.1 multiprocess application set to either APPCULL_DRAW or APP_CULL_DRAW. The
call that seems to be causing this is pfuPrioritizeProcs( true ). When the
application doesn't run as root, we get a notification: "must be root to set
non-degrading priorities" and every thing runs OK; but when running as root,
the same thing happens, a total freeze and we have use the h/w reset button.

Any idea on what's causing this ??!

Jean-Luc

-- 
_____________________________________________________________________________

Jean-Luc Dery Discreet Logic System Engineer 10 Duke Street 3-D Graphics Technology Montreal (Quebec), Canada, H3C 2L7 Tel: (514) 954-7239 Email: dery++at++discreet.com Fax: (514) 393-0110 _____________________________________________________________________________

===================================List Archives, FAQ, FTP: http://www.sgi.com/Technology/Performer/ Submissions: info-performer++at++sgi.com Admin. requests: info-performer-request++at++sgi.com


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:56:08 PDT

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