Hi,
I was developing a small database and started to get consistent bus crashes:
Bus Error
Program Counter: 0x0000879c
Status Register: 0x3008
Access Address : 0x404d0000
Special Status : 0x04a5
Task: 0xe50e54 "scanPeriod"
task: 0Xe786ac taskwd
I took out all my mods to the point before they started appearing but
they did not go away. I tracked down the line of code that caused them
(in my sub record c code) and it turned out to be the vxWorks 'read'
function. I checked all the parameters in the call and they are fine.
(the read is reading from a tcp socket, not a disk etc). I thought it
unlikely to be vxWorks so I tried it in another crate and the error
disappeared, -> hardware error.
I removed the cpu and pressed all the sockets etc but that hasn't
helped. The other funny thing is that this application also caused a bus
error a few weeks ago in the crate that it now works in, but that problem
was left unfinished rather than being tracked down.
So, the upshot is that we appear to have transient hardware errors in our
systems.
Has anyone come across this before, is there a particular connector that
exhibits this behavour? (mv167)
thanks
Ian A Smith Telephone: +44 (0) 131 668 8257
Royal Observatory Fax: +44 (0) 131 668 1130
Blackford Hill Web: http://www.roe.ac.uk/
Edinburgh
EH9 3HJ
UK
- Navigate by Date:
- Prev:
Re: EPICS PLC Support Dr. Pete Jemian
- Next:
Re: macro substitution Marty Kraimer
- 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: EPICS PLC Support Dr. Pete Jemian
- Next:
[no subject] Jim B. Kowalkowski
- 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
|