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: | FW: R3.13.10 ca_event problem |
From: | "Jeff Hill" <[email protected]> |
To: | <[email protected]> |
Date: | Wed, 25 Jan 2006 08:44:47 -0700 |
Allan,
The "callbackRequest ring buffer full" message comes from the database function callbackRequest(). This typically indicates that a device's interrupt production rate exceeds the the record processing rate (due to CPU saturation). This is related to a device/record that are configured "scanned on interrupt".
> task 36a5718 CA_event suspended
My best guess at this time is that there is object code corruption resulting from a errant pointer, but that is only a wild guess, based on very limited information.
To debug this, we of course need the stack trace from that CA event thread after this instruction access exception occurs. Type "tt ( event thread's task id )".
> appeared to lose it’s connections to all it’s clients
This would happen if there is CPU saturation. Also watch out for MBUF starvation occurring with newer versions of vxWorks (which dont dynamically expand the MBUF pool should it becomes depleted).
Jeff
|