Hi Andrew,
My initial posting was about a new Pentium4 Dual Core IOC.
However, I was not running an SMP vxWorks Image.
So, my original problem must be related to a change in the memLib API
from Windriver,
I will investigate that a bit more based on the information from Jeff.
Meanwhile, I decided to go ahead and build a SMP vxWorks image. :)
You are right, changes are definitely needed
I can't even run the libCom Tests since routines like "intLock" and
"taskLock" are not available.
Now, we must use spinlocks and other atomic routines in the vxWorks SMP API
I agree an excellent codeathon activity :-)
Press any key to stop auto-boot...
1
auto-booting...
boot device : gei
unit number : 0
processor number : 0
host name : rsh
file name :
/afs/slac/g/lcls/epics/iocCommon/ioc-b34-cd05/vxWorksV/vxWorks
inet on ethernet (e) : 134.79.219.51:fffffc00
host inet (h) : 134.79.19.73
gateway inet (g) : 134.79.219.1
user (u) : cdvx
flags (f) : 0x0
target name (tn) : ioc-b34-cd05
startup script (s) :
/afs/slac/g/lcls/epics/iocCommon/ioc-b34-cd05/startup.cmd
Loading... 1634768 + 276224
Starting at 0x408000...
Loading symbol table from
rsh:/afs/slac/g/lcls/epics/iocCommon/ioc-b34-cd05/vxWorksV/vxWorke
]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]
]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]
]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]
]]]]]]]]]]] ]]]] ]]]]]]]]]] ]]
]]]] (R)
] ]]]]]]]]] ]]]]]] ]]]]]]]] ]] ]]]]
]] ]]]]]]] ]]]]]]]] ]]]]]] ] ]] ]]]]
]]] ]]]]] ] ]]] ] ]]]] ]]] ]]]]]]]]] ]]]] ]] ]]]] ]]
]]]]]
]]]] ]]] ]] ] ]]] ]] ]]]]] ]]]]]] ]] ]]]]]]] ]]]] ]] ]]]]
]]]]] ] ]]]] ]]]]] ]]]]]]]] ]]]] ]] ]]]] ]]]]]]] ]]]]
]]]]]] ]]]]] ]]]]]] ] ]]]]] ]]]] ]] ]]]] ]]]]]]]]
]]]]
]]]]]]] ]]]]] ] ]]]]]] ] ]]] ]]]] ]] ]]]] ]]]]
]]]] ]]]]
]]]]]]]] ]]]]] ]]] ]]]]]]] ] ]]]]]]] ]]]] ]]]] ]]]]
]]]]]
]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]
]]]]]]]]]]]]]]]]]]]]]]]]]]]]] Development System
]]]]]]]]]]]]]]]]]]]]]]]]]]]]
]]]]]]]]]]]]]]]]]]]]]]]]]]] VxWorks 6.8 SMP
]]]]]]]]]]]]]]]]]]]]]]]]]] KERNEL: WIND version 2.13
]]]]]]]]]]]]]]]]]]]]]]]]] Copyright Wind River Systems, Inc.,
1984-2009
CPU: GE Intelligent Platforms Embedded Systems - XVB601-BSP-VXW SMP -
SYMMETRIC_IO_MODE. .
Memory Size: 0xcb6fa000. BSP version 2.0/01.04.
Created: Feb 12 2011, 00:39:27
ED&R Policy Mode: Deployed
WDB Comm Type: WDB_COMM_END
WDB: Ready.
Executing startup script
'/afs/slac/g/lcls/epics/iocCommon/ioc-b34-cd05/startup.cmd'...
# ===================================================================
# IOC Application Startup
#
==============================================================================
# Execute the startup script for the IOC specific application
#
==============================================================================
#
##cd
"/afs/slac/g/lcls/epics/TestStand/iocTop/R3-14-12/performanceTest/Development/iocBoot/"
##< st.cmd
# Run the libCom Tests from EPICS BASE:
cd "/afs/slac/g/lcls/epics/base/base-R3-14-12"
value = 0 = 0x0
ld(0,0, "bin/vxWorks-pentium4/vxTestHarness.munch")
Warning: module 0xd4d643c holds reference to undefined symbol intUnlock.
Warning: module 0xd4d643c holds reference to undefined symbol intLock.
Warning: module 0xd4d643c holds reference to undefined symbol taskVarAdd.
Warning: module 0xd4d643c holds reference to undefined symbol taskVarDelete.
ld(): module contains undefined symbol(s) and may be unusable.
value = 0 = 0x0
Done executing startup script
'/afs/slac/g/lcls/epics/iocCommon/ioc-b34-cd05/startup.cmd'.
ioc-b34-cd05>
Andrew Johnson wrote:
On Friday 11 February 2011 13:17:22 Jeff Hill wrote:
I have the following running under ...
vxWorks 6.8:
Intel Dual Core
You must be one of the first sites running EPICS on the new symmetric
multiprocessing (SMP) vxWorks!
Ernest, if you have more than one core enabled I can _guarantee_ that your IOC
is not going to run properly. Our vxWorks OSD code is not ready for SMP
operation yet, it needs someone to go through it with a fine tooth-comb, which
might be a good Codeathon project for one of your guys.
Must I throw the "-mlong" flag?
I thought that was only for the PowerPC architecture.?
It's not going to be as simple as that.
Please try running the libCom test suite on this CPU first:
cd "/path/to/epics/base"
ld 0,0, "bin/vxWorks-xxx/vxTestHarness.munch"
epicsRunLibComTests
Any test failures in the results should give a few ideas of places that will
need a closer look.
- Andrew
- Replies:
- Re: no space in pool for a new client (below max block thresh) in EPICS R3.14.12 Andrew Johnson
- References:
- Re: no space in pool for a new client (below max block thresh) in EPICS R3.14.12 Ernest L. Williams Jr.
- RE: no space in pool for a new client (below max block thresh) in EPICS R3.14.12 Jeff Hill
- Re: no space in pool for a new client (below max block thresh) in EPICS R3.14.12 Andrew Johnson
- Navigate by Date:
- Prev:
Re: no space in pool for a new client (below max block thresh) in EPICS R3.14.12 Ernest L. Williams Jr.
- Next:
Atomtex radiation monitors Bryce Karnaghan
- 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: no space in pool for a new client (below max block thresh) in EPICS R3.14.12 Ernest L. Williams Jr.
- Next:
Re: no space in pool for a new client (below max block thresh) in EPICS R3.14.12 Andrew Johnson
- 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
|