[net.micro.att] Problems with 3B2's locking up

david@ukma.UUCP (David Herron, NPR Lover) (05/23/85)

I directly work with 4 3B2's and the University has 21 total.  Of the
4 I work with, we have had 1 that's always been crashing every day.
And the other 3 have had similar problems at times.

One thing that happens is that it forgets how to let people log in.
This includes to root.  It will ask for login name/password but not
net you log in.

Another thing is it gives the "SYSTEM FAILURE:  CONSULT SYSTEM ADMINISTRATOR'S
GUIDE" message.  Just out of the blue.  The last time it happened, I brought
it into formware mode and tried to run diagnostics.  But that kept giving
me a message talking about an unexpected interrupt.  And it wouldn't turn
off either!  (Yes, I did try hitting RESET and STANDBY.  No luck here.)

Eventually we got brave and unplugged it.  It eventually reset and
rebooted and has been working for days since then.

These machines are all configured as:

     2 mb main memory
     32 mb hard disk
     1 ports board (4 serials + parallel)
     1 3bnet board

They also all run uucp connections at 9600 baud, one at 1200 baud.
(come to think of it ... the machine with the 1200 baud connection is the
one that's been giving us the most problems, it's connected to a
racal-vadic 3451a modem)

2 of the machines haven't been seeing much usage, the other 2 have
(one of which is the flaky machine)


Anybody have any ideas?

Anybody else experiencing such problems?


-- 
--- David Herron
--- ARPA-> ukma!david@ANL-MCS.ARPA or ukma!david<@ANL-MCS> 
---	   or david%ukma.uucp@anl-mcs.arpa
---        Or even anlams!ukma!david@ucbvax.arpa
--- UUCP-> {ucbvax,unmvax,boulder,oddjob}!anlams!ukma!david
---        {ihnp4,decvax,ucbvax}!cbosgd!ukma!david

	"It's *Super*User* to the rescue!"

heiby@cuae2.UUCP (Heiby) (05/25/85)

You don't mention what release of the Unix Operating System you are
running.  Older versions had some problems with ports locking up,
although I don't have the details at hand.  The current release,
System V Release 2.0 AT&T 3B2 Version 2, has those problems corrected.
If you have not upgraded to System V Release 2.0, I'd strongly recommend
that you do so.  If you are already at the latest release, I'd say you
have a hardware problem (spurious interrupt?) and should make good use
of your hardware maintenance agreement.
-- 
Ron Heiby	heiby@cuae2.UUCP	(via wnuxa or wnuxb)
AT&T-IS, /app/eng, Lisle, IL	(312) 810-6109