We just experienced a bizarre occurrence with our beamline vme crate.
Suddenly, it started to spontaneously reboot over and over, each time
giving the message "WorkQ Panic. kernel work queue overflow", near the end
of the process of loading all our databases, etc. This continued until we
turned the crate off. I would appreciate any info about where this might
come from and/or how to test if conditions are leading to this state.
We recently switched to an mv162 from an mv167, but are running the same
application we have run for quite awhile, with the exception of version 3.4
of the motor record and device support. Another difference is that I was
getting an error when the crate booted about a missing device support entry
table for an unused motor controller because of a makefile error (since
corrected).
We are running epics 3.13beta11, and vxWorks 5.2.1
Thanks very much.
Dale Brewe
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Dale L. Brewe PNC-CAT/U. of Washington
ph: 630 252 0582 fax: 630 252 0580
Mail:
APS/Argonne National Laboratory
Bldg 435E sector 20
9700 S. Cass Ave.
Argonne, IL 60439
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
- Navigate by Date:
- Prev:
RE: caerr.h typo Jeff Hill
- Next:
Re: ????kernel work queue overflow error???? Ned Arnold
- 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:
Latch record Allan Honey
- Next:
Re: ????kernel work queue overflow error???? Ned Arnold
- 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
|