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
>
>
>
> --
>
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
- Replies:
- Re: IOC Crash with No Exception Generated Ricardo Cardenes via Tech-talk
- Navigate by Date:
- Prev:
RE: Signing off Kline, David
- Next:
Detect VC++ version in Makefile? Mark Rivers
- 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: IOC Crash with No Exception Generated Ricardo Cardenes via Tech-talk
- Next:
Re: IOC Crash with No Exception Generated Ricardo Cardenes via Tech-talk
- 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
|