Re: Slow loading of symbol table on MVME162

[edmond desmond <desmond2@bnl.gov>]

Dear Mark:

We were experiencing the same load time of exactly 50 seconds for not only 162s but
ppc controllers as well.  Steve Adler, here at BNL, found that by using tftp to load

the kernel and symbol table results an expected load time of some 5 seconds.
Steve found a reference regarding this in the vxworks news group at comp.os.vxworks.

I have included the mail reply from Steve to that newsgroup below.

Newsgroups: comp.os.vxworks
Subject: Re: FTP active connection
Date: Mon, 21 Sep 1998 08:48:13 -0500
From: "Randy Lee" <lebo@mvisXXX.com>
Organization: http://www.supernews.com, The World's Usenet: Discussions Start
Here
Message-ID: <6u5sgg$1a5$1@supernews.com>
References: <6tqupe$q0o$1@fe2.cs.interbusiness.it>

When the client breaks a connection, the connection will close after a
timeout period.  The default timeout is around 90s although I believe you
can modify it as a #define in the FTP header file.

There is also a #define in the FTP header which defines the max simultanious
FTP connections.  I don't know how to query the FTP server for number of
current connections.

Hope this helps

- -Randy
The boot flag of 0x80 must be set to set the tftp protocol.

Regards,
Ed Desmond

Mark Rivers wrote:

> I am having a problem with very slow loading of the vxWorks symbol table on an
> MVME162 CPU.
>
> I have a bunch of IOCs with MVEM167 CPUs.  These take only 5 seconds to load the
> vxWorks symbol table, which is 153837 bytes in size.
>
> My MVME162 CPU takes exactly 50 seconds to load the symbol table, which is
> 153914 bytes in size, i.e. almost identical size. It takes 10 times longer
> than on an MVME167.
>
> The boot parameters for each CPU are the same.
>
> I am booting from a Digital Unix system, so I was willing to blame some quirk
> of that system.
>
> However, I just went to another CAT beamline here at the APS.  They have the
> identical problem, and they are booting from a Solaris 2.6 system.  Tim Mooney
> tells me that he saw the problem for the first time a couple of weeks ago when
> he began using Solaris 2.6 for the first time.
>
> Has anyone else seen this problem?  Ideas on what could be wrong?
>
> Thanks,
> Mark Rivers



--
Edmond Desmond
phone: (516) 344-4768
email desmond2@bnl.gov