We recently diagnosed an insidious problem here at the APS.
As with most really insidious problems, this one is caused by
a combination of errors.
We have a Tracewell System 22 VME crate with field swappable
power supply and fan tray that has been experiencing "Oms58_motor"
task crashes for over a year with increasing frequency.
After lots of board swapping, unplugging and plugging things in
and out, we finally determined that the Tracewell VME Power
Monitor is outputting ACFAIL* glitches (~ 7ns) on the VMEbus.
This, combined with the fact that the OMS VME58 board
processes the ACFAIL* line unfiltered, resulted in the VME58
board intermittently rebooting, which in turn caused a VME bus
error, which in turn caused the "Oms58_motor" task to crash.
(Note that the OMS MAXv does not monitor the ACFAIL* signal;
so this problem cannot happen with a MAXv.)
Lesson learned; if you have intermittent VME bus errors on the
memory address of an OMS VME58 board, and board swapping
does not resolve the problem, then check the ACFAIL* signal for
glitches.
Hoping this saves someone days of frustration,
Ron
- Navigate by Date:
- Prev:
Re: sscan and averaging [SEC=UNCLASSIFIED] Tim Mooney
- Next:
which manual describes command-line options of vxWorks gnu Compiler 王林
- 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: sscan and averaging [SEC=UNCLASSIFIED] Tim Mooney
- Next:
which manual describes command-line options of vxWorks gnu Compiler 王林
- 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
|