Re: [info-performer] semaphore errors again ..

New Message Reply Date view Thread view Subject view Author view

From: Tom Flynn (flynnt++at++engr.sgi.com)
Date: 09/12/2002 22:06:23


hmmm, this shouldn't happen in 2.5.2....what kernel are you running
against? (i'll run the same kernel here and double check it)
-tom

On Thu, 12 Sep 2002, Michael Logan wrote:

> Hmmm.. I'm now getting this error in Performer 2.5.2 demo version:
>
> PF Fatal/Internal: : Numerical result out of range
> PF Warning/SysErr(34): Error posting semaphore 4f8011 [9] in pid 2399
> PF Fatal/Internal: PF_USPSEMA() errno = 0
> PF Fatal/Internal: : Numerical result out of range
> PF Warning/SysErr(34): Error posting semaphore 4f8011 [10] in pid 2400
> PF Fatal/Internal: PF_USPSEMA() errno = 0
>
>
> I just installed everything today.
>
> I have a dual 866Mhz P-III RH7.3 box, with an
> NVIDIA Quadro2-Pro. The Performer libs are for gcc 2.96
>
> Its a fresh install, so no extras really.
>
> Was there something else that needs done? Patches? Upgrades?
>
> I was spinning a large terrain around in perfly for "burn in"
> purposes.. 8-)
>
> ml
>
> > From: Tom Flynn (flynnt++at++engr.sgi.com)
> > Date: 05/28/2002 17:45:0
> >
> > ------------------------------------------------------------------------
> >
> > greetings,
> >
> > sorry for the delay in reply...this is fixed in performer 2.5.1.
> > -tom
> >
> > On Tue, 28 May 2002, Nigel Jenkins wrote:
> >
> > >
> > > Hi All
> > >
> > > I'm having exactly the same problem as S?bastien was having (13th May)
> > > and have delved a little deeper.
> > > I've used ddd and it appears the program is seg-faulting in a file
> > > called:
> > >
> > > sysdeps/unix/sysv/linux/semop.c
> > >
> > > I didn't see any reply's to S?bastien, is this a known error? Is there a
> > > fix in PF2.5.1?
> > > I get the same error on a number of machines Dell Latitude 1.6GHz
> > laptop
> > > and SGI 330's (dual 833MHz). I'm using 2.4.18 kernels on all machines
> > > and a pre-emptive kernel patch on the laptop, but disabling it has no
> > > effect on the error...
> > >
> > > cheers
> > >
> > > Nigel
> > >
> > >
> > >
> > > S?bastien Kuntz wrote:
> > > >
> > > > Hello!
> > > > I'm having a strange crash : after 15 or 20 minutes,
> > > > my applications crashes,
> > > > and performer tells me this :
> > > >
> > > > PF Fatal/Internal : : Numerical Result out of range
> > > > PF Fatal/Internal(29): PF_USPSEMA() errno = 29
> > > > PF Fatal/Internal : : Numerical Result out of range
> > > > PF Fatal/Internal(29): PF_USPSEMA() errno = 29
> > > > PF Fatal/Internal : : Numerical Result out of range
> > > >
> > > > I'm using a sid debian, a 2.4.18 kernel, a bi-athlon
> > > > 1.2ghz, and performer 2.5.
> > > >
> > > > does this have anything to do with the semaphore leaks
> > > > you've been talking about?
> > > > how should I deal with that ?
> > > >
> > > > the crash is not happening on another computer
> > > > (mandrake 8.2, bi-p3 800mhz and performer 2.5)
> > > > I'm not dealing with any semaphore in the code,
> > > > (althoug performer sure is)
> > > > Is there a pfPleaseDontCrash function? ;)
> > > >
> > > > thanx in advance, have a nice day
> > > > S?bastien Kuntz
> > > > S.N.C.F research dept.
> > > > --//
> >
>
>
> --
> Michael Logan Task Manager/Chief Programmer, Visual Cueing & Simulation
> Raytheon ITSS NASA Ames Research Center,MS 262-6,Moffett Field,CA, 94035
> (650)-604-4494 private: vonlogan++at++rcn.com
> http://users.rcn.com/vonlogan/index.htm
>
>
> -----------------------------------------------------------------------
> List Archives, Info, FAQ: http://www.sgi.com/software/performer/
> Open Development Project: http://oss.sgi.com/projects/performer/
> Submissions: info-performer++at++sgi.com
> Admin. requests: info-performer-request++at++sgi.com
> -----------------------------------------------------------------------
>

--
"Mongooses are famous for their snake-fighting ability, and are
 almost always victorious because of their speed, agility, and timing
 and also because of their thick coat."


New Message Reply Date view Thread view Subject view Author view

This archive was generated by hypermail 2b29 : Thu Sep 12 2002 - 22:06:34 PDT

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