Experimental Physics and Industrial Control System
|
I believe this was solved with entry 334 in Mantis. R3.14.11 was the
first release with the fix. The problem occurred when I connected to PVs
from 2 or more IOCs and it happened when I was exiting the program. It
only happened rarely, but enough to be a big problem for us.
P.S. How can we search launchpad for Mantis bug numbers?
[email protected] wrote:
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
- Replies:
- Re: epicsThreadOnceOsd epicsMutexLock failed Ralph Lange
- References:
- epicsThreadOnceOsd epicsMutexLock failed Wang Xiaoqiang
- Re: epicsThreadOnceOsd epicsMutexLock failed Ralph Lange
- RE: epicsThreadOnceOsd epicsMutexLock failed nick.rees
- Navigate by Date:
- Prev:
RE: epicsThreadOnceOsd epicsMutexLock failed nick.rees
- Next:
Re: epicsThreadOnceOsd epicsMutexLock failed Ralph Lange
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
<2010>
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
- Navigate by Thread:
- Prev:
RE: epicsThreadOnceOsd epicsMutexLock failed nick.rees
- Next:
Re: epicsThreadOnceOsd epicsMutexLock failed Ralph Lange
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
<2010>
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
|
ANJ, 02 Sep 2010 |
·
Home
·
News
·
About
·
Base
·
Modules
·
Extensions
·
Distributions
·
Download
·
·
Search
·
EPICS V4
·
IRMIS
·
Talk
·
Bugs
·
Documents
·
Links
·
Licensing
·
|