Eric Norum wrote:
Hmm....
This sounds like a task starvation issue. It appears that the read task
is looping at a higher priority than the event timer callback task and
so is preventing the callback from running. My suspicion is that it's
the vxWorks version of select() which is not rounding the timeout up to
at least one tick. If so, the problem will still be present in the
latest version of ASYN.
I called spy and found that the asyn port thread is indeed using up all
CPU time at higher priority than e.g. CA or the timerQueues.
--
Dr. Dirk Zimoch
Swiss Light Source
Paul Scherrer Institut
Computing and Controls
phone +41 56 310 5182
fax +41 56 310 4413
- Replies:
- Re: asynDriver / epicsTimer bug Eric Norum
- References:
- asynDriver / epicsTimer bug Dirk Zimoch
- Re: asynDriver / epicsTimer bug Dirk Zimoch
- Re: asynDriver / epicsTimer bug Eric Norum
- Navigate by Date:
- Prev:
Re: asynDriver / epicsTimer bug Eric Norum
- Next:
Re: asynDriver / epicsTimer bug Eric Norum
- 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: asynDriver / epicsTimer bug Eric Norum
- Next:
Re: asynDriver / epicsTimer bug Eric Norum
- 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
|