Experimental Physics and
Industrial Control System

<[email protected]> · Fri, 16 Apr 2010 16:52:55 +0100

Hi Ralph, Xiaoqiang,

This isn't just HP-UX. If I do:

for (( i=0; i<100; i++ )) ; do caget CS-CS-MSTAT-01:MODE; echo $?; done

On RHEL5/R3.14.8.2 this generates the message "epicsThreadOnceOsd
epicsMutexLock failed." (usually, but not always, with exit status 255)
about every 20 caget's.

If I do the same thing on RHEL5/R3.14.11 it doesn't seem to happen (at
least not in 500 tries).

Whatever it is, it seems to have got better with R3.14.11 and so maybe
that's what Xiaoqiang should try. If someone still wants me to generate
a stack trace I can, but maybe we can close it with a message.

Cheers,

Nick Rees
Principal Software Engineer           Phone: +44 (0)1235-778430
Diamond Light Source                  Fax:   +44 (0)1235-446713 

> -----Original Message-----
> From: [email protected] 
> [mailto:[email protected]] On Behalf Of Ralph Lange
> Sent: 16 April 2010 16:22
> To: Wang Xiaoqiang
> Cc: EPICS Tech Talk
> Subject: Re: epicsThreadOnceOsd epicsMutexLock failed
> 
> Hello Xiaoqiang,
> 
> Please note that the EPICS Base bug tracker has been moved to the new 
> EPICS Base location on Lauchpad, this bug is now:
>    https://bugs.launchpad.net/epics-base/+bug/541249
> The old Mantis tracker is still on-line for reference, but it 
> is *not* 
> updated anymore.
> 
> The bug is suspended, because Jeff was asking for a stack trace which 
> was never provided.
> 
> The bug is about erroneous behavior experienced on the HP-UX 
> operating 
> system.
> Support for HP-UX has been dropped with EPICS release 3.14.9, so this 
> bug will most probably never be fixed.
> 
> If you experience the error on a different version of EPICS and a 
> different operating system, please check on Launchpad if it has been 
> reported. If not, you are encouraged to file a new bug report.
> 
> Thanks a lot,
> Ralph
> 
> 
> On Fri 16 Apr 2010 10:08:53 Wang Xiaoqiang wrote:
> > Hi,
> >
> > When CA client exit, sometimes it spills out "epicsThreadOnceOsd
> > epicsMutexLock failed" message. It has been reported since 
> 3.14.7 and
> > has an entry 207 in Mantis. The status is labeled as 
> "suspended". Does
> > it mean it is hopeless to be solved?
> > http://www.aps.anl.gov/epics/mantis/view_bug_page.php?f_id=207
> >
> > In normal cases it is harmless since the program is anyway exiting.
> > However it exits with code 255. If it is run as a 
> subprocess, this will
> > cause the caller think exit code other than 0 is wrong and stop
> > execution. In such case one cannot ignore the exit code, which would
> > ignore other possible exceptions.
> >
> > Thanks and nice weekend.
> > --
> > Dr. Xiaoqiang Wang
> > Paul Scherrer Institut, WBGB/010
> > 5232 Villigen PSI, Switzerland
> >
> >   
> 

-- 
This e-mail and any attachments may contain confidential, copyright and or privileged material, and are for the use of the intended addressee only. If you are not the intended addressee or an authorised recipient of the addressee please notify us of receipt by returning the e-mail and do not use, copy, retain, distribute or disclose the information in or attached to the e-mail.
Any opinions expressed within this e-mail are those of the individual and not necessarily of Diamond Light Source Ltd. 
Diamond Light Source Ltd. cannot guarantee that this e-mail or any attachments are free from viruses and we cannot accept liability for any damage which you may sustain as a result of software viruses which may be transmitted in or with the message.
Diamond Light Source Limited (company no. 4375679). Registered in England and Wales with its registered office at Diamond House, Harwell Science and Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United Kingdom

Experimental Physics and Industrial Control System

Experimental Physics and
Industrial Control System