Dale,
> 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, ...
I had a very similar problem a couple of weeks ago. It turns out that the
Markfile in the ioc directory had ARCH defined for mv167 rather than mv162.
It was thus booting the wrong version of vxWorks, not a pretty sight.
I also have had problems with:
- Boards not seated completely
- The APS A32Vme module (position monitors, etc.) had problems on the
mv162, probably because the default base address doesn't work with the
162 BSP.
Mark Rivers
- Navigate by Date:
- Prev:
Re: ????kernel work queue overflow error???? J. Frederick Bartlett ([email protected])
- Next:
enhancements to Andrew Johnson's IPC driver Jeff Hill
- 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: ????kernel work queue overflow error???? J. Frederick Bartlett ([email protected])
- Next:
enhancements to Andrew Johnson's IPC driver Jeff Hill
- 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
|