EPICS Home

Experimental Physics and Industrial Control System


 
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  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 
<== Date ==> <== Thread ==>
Subject: asynDriver / epicsTimer bug
From: Dirk Zimoch <[email protected]>
To: TECHTALK <[email protected]>
Date: Tue, 30 May 2006 18:05:40 +0200
Hi Marty, Jeff et al

When asynOctet->read() (or at least readRaw() of the TCP port driver) is called on vxWorks with pasynUser->timeout < 1/sysClkRateGet() [normally about 16 ms], the read call hangs and does never time out.

I think it is actually a problem with epicsTimer, which never expires for timeouts < 1/sysClkRateGet(). But I have not tested this.

I think, a timer should wait at least the specified amount of time, thus always round up to at least one tick.

Dirk

--
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
RE: asynDriver / epicsTimer bug Jeff Hill
Re: asynDriver / epicsTimer bug Dirk Zimoch
Navigate by Date:
Prev: FFTW for vxWorks? 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: FFTW for vxWorks? 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