Masscomp 5500 ethernet hardware failure?

Article View: comp.sys.concurrent

Article #17

Back to comp.sys.concurrent Previous Next

#17

From: Dr. Craig Allen Counterman
Date: Thu, 13 Aug 1992 21:37

41 lines
1523 bytes

I have an old, long out of contract, 5500.  It crashed and when it
rebooted it was off the net.  Examination and supervised rebooting
showed that there was a problem with the ethernet.  Powercycling,
reseating the board, general laying on of hands didn't help.  The
error messages (this is unix version 4.0A)

Ethernet 0 at FF0170
Ethernet 0 reset failed

later:
EXOS 0 sext msg with bad kludge pointer
Loading network TCP/IP software
Ethernet 0 reset failed

EXIOCRESET: Network is down
Network download failed


The board is an EXCELAN EXOS 301
7220001700 Rev B
1289

P/N: 9900020-04		REV: C
DC: 8905		ECN: 2063


On powerup, the indicator lamps have sometimes all been off from the
start, but usually lamp #1 is on steadily (which indicates hardware
failure) and sometimes lamp #3 is on steadily as well.

So: any hints?  Is this a recognizable component failure?  Is it
certain to be the ethernet board or is it possible that another board
is interfering with it (the FPU has on occasion failed diagnostics)?

Thanks,
Craig



--
"Dr. Craig Allen Counterman, Ph.D."

Technical Details

Message-ID: <1992Aug13.213756.4150@athena.mit.edu>

Path: arc1-ca.pugleaf.net!sparky!uunet!dtix!darwin.sura.net!mips!mips!bdcsys!news

Show Full Headers

Complete Article Headers

Path: arc1-ca.pugleaf.net!sparky!uunet!dtix!darwin.sura.net!mips!mips!bdcsys!news
From: ccount@athena.mit.edu (Dr. Craig Allen Counterman)
Newsgroups: comp.sys.concurrent
Subject: Masscomp 5500 ethernet hardware failure?
Message-ID: <1992Aug13.213756.4150@athena.mit.edu>
Date: 13 Aug 92 21:37:56 GMT
Sender: news@bdcsys.suvl.ca.us
Organization: ncurrent-request
Lines: 41
Approved: concurrent-request@bdcsys.suvl.ca.us