Experimental Physics and
Industrial Control System

Hi Zen,



This message makes me wonder if you are doing asyn callbacks at interrupt level?  If so, you should not do that, you should have your interrupt routine signal another thread which does the asyn callbacks.


>  interrupt: errlogPrintf called from interrupt level

Mark


________________________________
From: [email protected] [[email protected]] on behalf of Szalata, Zenon M. [[email protected]]
Sent: Friday, March 09, 2012 12:59 PM
To: [email protected]
Subject: Here is a Message

While modifying and testing a device driver subclassed from asynPortDriver for a VME module I am getting this message:


A call to 'assert(status == epicsMutexLockOK)'
    by thread 'cbLow' failed in ../../asyn/asynDriver/asynManager.c line 2222.
EPICS Release EPICS R3.14.11 $R3-14-11$ $2009/08/28 18:47:36$.
Local time is 2012-03-09 10:52:43.182719160 PUS
Please E-mail this message to the author or to [email protected]
Calling epicsThreadSuspendSelf()
Thread cbLow (0x1692b30) suspended
interrupt: errlogPrintf called from interrupt level

I am using asyn R4.17.

I am sending this message because the message tells me to.
I will comment out my recent modifications and try to pinpoint which part of my device driver is responsible.

Thanks,
Zen

Replies:

RE: Here is a Message Szalata, Zenon M.

References:

Here is a Message Szalata, Zenon M.

Navigate by Date:

Prev: Here is a Message Szalata, Zenon M.

Next: RE: Here is a Message Szalata, Zenon M.

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: Here is a Message Szalata, Zenon M.

Next: RE: Here is a Message Szalata, Zenon M.

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