Bernd,
We are quite familiar with this anomaly. Here are some suggestions:
TO ELIMINATE THE PROBLEM:
- Upgrade your EPICS release to 3.13.6 which uses Tornado 2.02.
Some of our most troublesome iocs have never experienced the
problem since moving to this new version of vxWorks.
TO MINIMIZE THE PROBLEM in R3.13.2:
- Install a faster CPU. We also have noticed that heavily loaded
CPUs are the most susceptible.
TO MINIMIZE THE PROBLEM prior to R3.13.2:
- Place the following lines in your st.cmd file to make tNetTask
a higher priority than any EPICS tasks ...
# Assign a higher priority to tNetTask
taskPrioritySet(taskNameToId("tNetTask"),30)
Hope this helps ....
Ned
>Hi all,
>
>I have a problem, that Jim Olsen (SLAC) has described in a tech-talk
>mail in february 2000. We are using Epics 3.13.1 and the tNetTask ist
>taking all CPU-time sometimes (happened 2 times now). That causes most
>IOC tasks to hang. It seems to me this is triggered due to heavy network
>traffic. I discovered that during network problems the CPU-load of the
>IOC goes up to 100%. But it's not allways hanging afterwards. In the
>tech-talk archive I didn't find a solution for this problem. Do you
>remember how this problem was fixed ? Which patch is needed?
>
>Thanks
>
>Bernd
>
>
- Replies:
- Re: tNetTask consumes all CPU time anj
- Navigate by Date:
- Prev:
Re: AO Record: New Drive Limit Mode? Ralph . Lange
- Next:
Re: tNetTask consumes all CPU time anj
- 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:
tNetTask consumes all CPU time Bernd Schoeneburg
- Next:
Re: tNetTask consumes all CPU time anj
- 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
|