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 2025 | 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 2025 |
<== Date ==> | <== Thread ==> |
---|
Subject: | Re: Bus errors accessing VME with base 7.0.6.1 and latest synApps modules |
From: | Kevin Peterson via Tech-talk <tech-talk at aps.anl.gov> |
To: | Mark Rivers <rivers at cars.uchicago.edu>, Till Straumann <till.straumann at psi.ch> |
Cc: | "tech-talk at aps.anl.gov" <tech-talk at aps.anl.gov> |
Date: | Thu, 9 Jun 2022 12:21:07 -0500 |
VME Bus Error accessing A32: 0xbfe00000 machine check Exception next instruction address: 0x032dc280 Machine Status Register: 0x0008b032 Condition Register: 0x40000844 Task: 0x3576c20 "CAC-event"0x3576c20 (CAC-event): task 0x3576c20 has had a failure and has been stopped. 0x3576c20 (CAC-event): The task has been terminated because it triggered an exception that raised the signal 10.
I can't run the Wind River workbench yet; I'm still waiting on IT to start the necessary license servers.
My VME has the VMETRO bus analyzer in it, but it has probably been a decade since I watched someone (Ron Sluiter) use it effectively.
Kevin On 6/9/22 11:05, Mark Rivers via Tech-talk wrote:
If the test program loops from -0.7 to -0.5 the VME bus error address is 0xbfe66664. That is -0.6999988555908203 when interpreted as a double with that address as the most significant 32 bits. That is within the now more restricted range of the output values.