EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  <20182019  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  <20182019  2020  2021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: Re: IOC Crash with No Exception Generated
From: Ricardo Cardenes via Tech-talk <[email protected]>
To: [email protected]
Cc: Talk EPICS Tech <[email protected]>
Date: Tue, 31 Jul 2018 09:24:51 -1000
Hi Heinz,

What do you mean here with "timer zero passing interrupt"?

Just to clarify the timeline, initially we tested the system with one board and it took ~9:16 for it to fail. We installed a different board (same model, with more RAM) and it went stable for 2 days and some 18:34 hours. The next halt came after ~6:30 hours, and then 3 more halts with varying times between each other (33 to 50 minutes). Then the system decided to keep going for the rest of the night.

I don't really see any pattern, but if you have any insight...

Regards,
Ricardo

On Sun, Jul 29, 2018 at 2:11 AM Heinz Junkes <[email protected]> wrote:
The time it takes to crash reminds me of a timer zero passing interrupt…

Just a feeling,
Heinz


> On 26. Jul 2018, at 03:52, Matt Rippa via Tech-talk <[email protected]> wrote:
>
> ---------- Info / Warning ---------- Address To: differs from Envelope to Talk EPICS Tech != [email protected] (For Mailing lists etc. ok) ------------------------------------
>
> We commissioned a new RTEMS IOC here in Hawaii. The system ran
> for 2 days, 18 hours and 47 minutes before it simply halted. No exception was generated therefore no stack trace was seen. Also no console, no iocsh, no log messages. A system reset recovered our system before halting in the same manner 2 hours later. This occurred 4 times before the night ended.
>
> We speculate bad access or stack corruption but without a stack trace
> we're at a complete loss as to how to diagnose this. This same software release has run for several weeks at our other site with no issues.
> ​
> Is there a way to force an exception (or stack trace), for example with watchdog?
>
> Many thanks for your insight!
> RTEMS 4.10.2/EPICS 3.14.12.7 MVME2307 BSP
>
> ​
>
> --
>


References:
Re: IOC Crash with No Exception Generated Heinz Junkes

Navigate by Date:
Prev: Re: Compiler error on Debian Stretch arm Ralph Lange
Next: dbGetPdbAddrFromLink dropped from 3.15 again Till Straumann
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  <20182019  2020  2021  2022  2023  2024 
Navigate by Thread:
Prev: Re: IOC Crash with No Exception Generated Heinz Junkes
Next: Convert .edl (EDM) display files to .adl (MEDM)? J. Lewis Muir
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  <20182019  2020  2021  2022  2023  2024 
ANJ, 31 Jul 2018 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·