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 | 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 |
<== Date ==> | <== Thread ==> |
---|
Subject: | Re: OSI error messages with VxWorks 6.9.4.1 |
From: | Ron Sluiter <[email protected]> |
To: | EPICS <[email protected]> |
Date: | Mon, 29 Aug 2016 15:32:13 -0500 |
The error messages below are caused by a mismatch between the running version of VxWorks and the tool chain used to build EPICSbase. For example, build EPICSbase using a VxWorks 6.9.3 toolchain and then load it into a VME crate running VxWorks 6.9.4.1 and you will get the error messages below. The reverse also fails; build EPICSbase under 6.9.4.1 and try running it under VxWorks 6.9.3; same errors messages.
The root cause of this problem is that Intel Wind River Systems made changes to some data structures (the specifics of which I no longer recall) that EPICS uses between VxWorks 6.9.3 and 6.9.4.1. Binary compatibility is apparently not guaranteed between "maintenance" versions of VxWorks.
Ron On 8/25/2014 2:41 PM, Ron Sluiter wrote:
We recently tested VxWorks 6.9.4.1 for the 1st time on a teststand and found some new EPICS error messages that we have not seen before.osiSockDiscoverBroadcastAddresses(): status: 0x08x, ifconf.ifc_len: -1osiSockDiscoverBroadcastAddresses(): unable to fetch network interface configurationand,osiLocalAddr(): SIOCGIFCONF ioctl failed because "S_errno_ENXIO"These error messages appeared only once after iocInit and had no discernible effect on IOC performance. We are using base-3.14.12.3.Is anyone else using VxWorks 6.9.4.1? Are other VxWorks 6.9.4.1 users seeing these error messages? Ron