EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  <20062007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024  Index 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  <20062007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: Re: R 3.14.8.2 on FreeBSD 6.x amd64
From: "Ernest L. Williams Jr." <[email protected]>
To: [email protected]
Cc: EPICS tech-talk <[email protected]>
Date: Thu, 26 Oct 2006 00:56:18 -0400
On Thu, 2006-10-26 at 11:12 +0900, Artem Kazakov wrote:
> > Are you running EPICS in pure 64-bit mode?
> > That is did you build EPICS as a 64-bit package or are you in 32-bit
> > mode?
> Yes I'm running EPICS in pure 64-bit mode.
Excellent.


> 
> > If you are truly running pure 64-bit, you should run all of the
> > regression tests in EPICS BASE.  Also, you should check the EPICS
> > extensions.
> > 
> Regression test log is in attachment. 
> Looks fine, except this (I don't whether that is bad) 
> 
> #### epicsThreadPriorityTestHost
> epicsEventTryWait did not return epicsEventWaitTimeout
> Does not appear to support strict priority scheduling
You can build EPICS BASE to support strict priority scheduling.

======================================================
Modify: $EPICS_BASE/configure/CONFIG_SITE

# Use POSIX thread priority scheduling (YES or NO)
USE_POSIX_THREAD_PRIORITY_SCHEDULING = YES
====================================================


Be sure to run the above test (i.e. epicsThreadPriorityTestHost) as
root:

[root@dragon O.linux-x86_64]# pwd
/ade/epics/supTop/base/R3.14.8.2/src/libCom/test/O.linux-x86_64
[root@dragon O.linux-x86_64]# ./epicsThreadPriorityTestHost
Seems to support strict priority scheduling



> Thread 50dc00 has exited with leftover thread-specific data after 4
> destructor iterations
> 
> > The main problem I have now is with some of the EPICS extensions at run
> > time.
> >    --- alh (seg faults at run time)
> >    --- StripTool (seg faults)
> >    --- EDM  (works)
> >    --- probe (works)
> >    --- Channel Archiver (works)
> 
> With extensions I expereinced the same problem. Some of them were not
> working.
> Currently I primarly use this FreeBSD box for development and cross
> compilation to RTEMS, so I do not actually use any extensions on this
> box (except edm). 
> 

In order, for the 64-bit platforms to be useful as a full EPICS file
server the extensions will have to be addressed. At least the most used
extensions in the community such as the StripTool and alh.  I have not
tried medm as of yet.



Thanks,
Ernest




> Tyoma.


References:
R 3.14.8.2 on FreeBSD 6.x amd64 Artem Kazakov
Re: R 3.14.8.2 on FreeBSD 6.x amd64 Ernest L. Williams Jr.
Re: R 3.14.8.2 on FreeBSD 6.x amd64 Artem Kazakov

Navigate by Date:
Prev: Re: R 3.14.8.2 on FreeBSD 6.x amd64 Artem Kazakov
Next: RTEMS now on IOC 9010 Blade and new 4 PMC Slot Version Darrell Nineham
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  <20062007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
Navigate by Thread:
Prev: Re: R 3.14.8.2 on FreeBSD 6.x amd64 Artem Kazakov
Next: problem about importing sca to delphi marco_hair
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  <20062007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
ANJ, 02 Sep 2010 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·