Re: Mvme167-35b

[Maren Purves <m.purves@jach.hawaii.edu>]

Li Jingyi wrote:
> 
> Hi all,
> 
> We have a newely bought Mvme167-35B card with 32MB memory.
> When I plug it in the crate and boot, the system halt.
> The vxWorks we currently use is 5.1 version. The following
> is the information on the console:
> 
> boot device          : ei
> processor number     : 0
> host name            : joca
> file name            : /usr/VxWorks_5.1/vw/config/mv167/vxWorks
> inet on ethernet (e) : 152.3.54.5:ffffff00
> host inet (h)        : 152.3.54.3
> user (u)             : epics
> flags (f)            : 0x0
> target name (tn)     : orbit
> startup script (s)   : /usr/applications/ioc/st.cmdmv167
> 
> Attaching network interface ei0... done.
> Attaching network interface lo0... done.
> Loading... 369412 + 103168 + 26458
> Starting at 0x1000...
> 
> Has anyone ever met such a problem and can give me some advise?

Seen this too many times ...

suggestions:
- check if you have an .rhosts file, and if the host that you are 
booting from is in it
- check that you DON't have a line
setenv EPICS_CA_AUTO_ADDR_LIST "NO"
(and a subsequent  EPICS_CA_ADDR_LIST that doesn't include both host
and crate) in your .login file
- check that your startup script doesn't have access restrictions in it
(but that, by itself, would make it halt later if I remember correctly)

Hope this helps,

Maren Purves
(it shouldn't be dependent on architecture)