"Ball, Patrick G." wrote:
>
> Steve,
> I was originally told that the problem was with the twin processors
> on the C box (A SUN problem???).
I don't think it was a Sun problem.
Here is the output of 2 dual processor Sparc20 & Sparc10 sun boxes (non
Foxboro)
[dbond@dino dbond]$ psrinfo -v
Status of processor 0 as of: 04/19/01 08:35:42
Processor has been on-line since 12/10/99 13:44:13.
The sparc processor operates at 75 MHz,
and has a sparc floating point processor.
Status of processor 2 as of: 04/19/01 08:35:42
Processor has been on-line since 12/10/99 13:44:17.
The sparc processor operates at 75 MHz,
and has a sparc floating point processor.
[dbond@dino dbond]$ uptime
8:35am up 495 day(s), 18:52, 5 users, load average: 0.01, 0.02,
0.03
[dbond@goofy dbond]$ psrinfo -v
Status of processor 0 as of: 04/19/01 08:34:04
Processor has been on-line since 11/19/99 06:15:10.
The sparc processor operates at 60 MHz,
and has a sparc floating point processor.
Status of processor 2 as of: 04/19/01 08:34:04
Processor has been on-line since 11/19/99 06:15:14.
The sparc processor operates at 60 MHz,
and has a sparc floating point processor.
[dbond@goofy dbond]$ uptime
8:34am up 517 day(s), 2:19, 8 users, load average: 0.06, 0.05,
0.06
[dbond@goofy dbond]$
> The fix was to disable one of the
> processor, but we were upgrading for a faster machine. I think that is why
> they changed to D and E boxes. ???
We used the Foxboro upgrade to 150Mhz single processor which fixed the
lockups which we saw with the AW51C. This is the report from an upgraded
AW51C
[dbond@6GA111 dbond]$ psrinfo -v
Status of processor 0 as of: 04/19/01 08:42:03
Processor has been on-line since 05/23/00 09:22:16.
The sparc processor operates at 150 MHz,
and has a sparc floating point processor.
[dbond@6GA111 dbond]$ uptime
8:42am up 330 day(s), 23:20, 2 users, load average: 0.30, 0.18,
0.15
Darryl Bond
>
> Patrick
> PSDF
>
> > -----Original Message-----
> > From: Murray, Steve [SMTP:[EMAIL PROTECTED]]
> > Sent: Wednesday, April 18, 2001 2:25 PM
> > To: 'Foxboro DCS Mail List'
> > Subject: RE: Upgrading Foxboro Boxes
> >
> > Hi Patrick,
> >
> > We bought a AW51C a few years ago as part of a new system. It would
> > crash
> > for no apparent reason and the Foxboro installation team replaced it with
> > a
> > AW51B before turning the system over to us. We were later told that
> > Foxboro
> > quit using the Cs altogether.
> >
> > Stephen Murray
> > Asarco
> >
> > -----Original Message-----
> > From: Ball, Patrick G. [mailto:[EMAIL PROTECTED]]
> > Sent: Wednesday, April 18, 2001 10:59 AM
> > To: 'Foxboro DCS Mail List'
> > Subject: RE: Upgrading Foxboro Boxes
> >
> >
> > Robert,
> > I am located at the PSDF (Power System Development Facility) her in
> > Wilsonville, AL. back a couple of years ago, we upgraded to an AW51C from
> > AW51A box (Ver. 4.1). We also have OSI PI system. I thought the A box was
> > slow, but when we got our C box, it would run fine without PI running, but
> > when PI was started the C box would crash in about 45 minutes. We had to
> > get
> > an AW51E box to fix the problem. We did work it out since we had just
> > upgraded to a C box. I know this probably does not answer your question,
> > but
> > I thought I would throw this in.
> >
> > Patrick G. Ball
> > Internet Address -- mailto:[EMAIL PROTECTED]
> > Intercompany -- 8-824-5877
> > Bell Phone -- 1-205-670-5877
> > Beeper -- 1-877-986-6814
> > <http://psdf.southernco.com/>
> >
> > This transmission is for the intended addressee only and is confidential
> > information. If you have received this transmission in error, please
> > delete
> > it and notify the sender. The contents of this E-mail are the opinion of
> > the
> > writer only and are not endorsed by ASARCO Inc. unless expressly stated
> > otherwise.
> >
> > -----------------------------------------------------------------------
> > This list is neither sponsored nor endorsed by the Foxboro Company. All
> > postings from this list are the work of list subscribers and no warranty
> > is made or implied as to the accuracy of any information disseminated
> > through this medium. By subscribing to this list you agree to hold the
> > list sponsor(s) blameless for any and all mishaps which might occur due to
> >
> > your application of information received from this mailing list.
> >
> > To be removed from this list, send mail to
> > [EMAIL PROTECTED]
> > with "unsubscribe foxboro" in the Subject. Or, send any mail to
> > [EMAIL PROTECTED]
>
> -----------------------------------------------------------------------
> This list is neither sponsored nor endorsed by the Foxboro Company. All
> postings from this list are the work of list subscribers and no warranty
> is made or implied as to the accuracy of any information disseminated
> through this medium. By subscribing to this list you agree to hold the
> list sponsor(s) blameless for any and all mishaps which might occur due to
> your application of information received from this mailing list.
>
> To be removed from this list, send mail to
> [EMAIL PROTECTED]
> with "unsubscribe foxboro" in the Subject. Or, send any mail to
> [EMAIL PROTECTED]
-----------------------------------------------------------------------
This list is neither sponsored nor endorsed by the Foxboro Company. All
postings from this list are the work of list subscribers and no warranty
is made or implied as to the accuracy of any information disseminated
through this medium. By subscribing to this list you agree to hold the
list sponsor(s) blameless for any and all mishaps which might occur due to
your application of information received from this mailing list.
To be removed from this list, send mail to
[EMAIL PROTECTED]
with "unsubscribe foxboro" in the Subject. Or, send any mail to
[EMAIL PROTECTED]
