Path: utzoo!mnetor!uunet!husc6!uwvax!oddjob!mimsy!umd5!ames!ucbcad!ucbvax!cbosgd!mandrill!neoucom!wtm
From: wtm@neoucom.UUCP (Bill Mayhew)
Newsgroups: comp.sys.att
Subject: Re: PC7300 refuses to echo characters
Message-ID: <852@neoucom.UUCP>
Date: 16 Dec 87 16:19:35 GMT
References: <653@astroatc.UUCP>
Organization: Northeastern Ohio Universities College of Medicine
Lines: 42
Summary: my observations on the lock-up


1.  I am running ver. 3.51 foundation set & utilities

2.  I *do* have the communications patch installed

3.  Timing of the lock-up is unpredictable.  The first time
    was 3 days after I got the machine.  The second time was
    about a week after that.  The last time, the machine was
    rebooted on Nov. 21, 1987 and ran until Dec. 15, 1987.

4.  A good test is when the slow-down happens, try tail
    /etc/termcap.  The display will freeze every 4 or 6 lines
    of output.  Pressing any ascii key will restart output.
    The keystrokes are received by the shell as is evidenced
    by garbage prepended to the next command typed at the shell
    prompt.

5.  Telinit -Q or kill -1 1 don't have any noticable effect.

6.  ps -fe doesn't show anything out of the ordinary.

7.  I think the problem might be related to the ph process.
    The crashing seems to happen an hour or two after there has
    been a uucp login on ph0.

8.  I don't run any weird daemon programs.  I gave phdaemon the
    boot after the AT&T help line insisted that since it was
    the only non-AT&T thing running it must be to blame.

9.  If you provoke the system by continuing to type stuff during
    the brain-stroke period, the system will die completely,
    requiring use of the dreaded black reset button in back.

10.  One time the slowness happened, I left the machine alone for
    about an hour to meditate with itself.  The slowness appeared
    to heal itself.  (Only a minor clot in a little artery, I
    suppose.)

11.  There  aren't any messages left behind in unix.log.


--Bill