[12016] in Athena Bugs

home help back first fref pref prev next nref lref last post

decmips 7.6G: xess

daemon@ATHENA.MIT.EDU (alexp@MIT.EDU)
Fri May 6 16:59:05 1994

From: alexp@MIT.EDU
Date: Fri, 6 May 94 16:58:58 EDT
To: rdhamlin@MIT.EDU, bugs@MIT.EDU
Cc: alexp@MIT.EDU


Hi, I've been looking at your problem report- are you able to reproduce
this problem on any other machine? If not, It's most likely a
problem on that particular one- possibly related to the heavy load; if
you see the problem again on milanese, I would suggest reporting it to the
Hardware Hotline.  I don't think this is anything due to Xess unless you
see it on other machines or in other circumstances.

Please let me know which situation applies so I can close this out, or 
pursue it further if it is reproducible.

                                            Alex Prengel, Jr.
                                            MIT Academic Computing Services
                                            Software Acquisition Coordinator

>From rdhamlin@MIT.EDU Sat Apr 30 23:44:52 1994
>Received: by gregor.MIT.EDU (5.57/4.7) id AA08634; Sat, 30 Apr 94 23:44:51 -04>00
>Received: from MILANESE.MIT.EDU by MIT.EDU with SMTP
>	id AA02127; Sat, 30 Apr 94 23:44:49 EDT
>From: rdhamlin@MIT.EDU
>Received: by milanese.MIT.EDU (5.57/4.7) id AA15991; Sat, 30 Apr 94 23:44:47 ->0400
>Message-Id: <9405010344.AA15991@milanese.MIT.EDU>
>To: bugs@MIT.EDU
>Subject: decmips 7.6G: xess
>Date: Sat, 30 Apr 94 23:44:47 EDT
>
>System name:		milanese
>Type and version:	KN02ca 7.6G (1 update(s) to same version)
>Display type:		
>
>What were you trying to do?
>use xess---just entering data/formulas
>
>What's wrong:
>
>xess abruptly quit on me without warning.  This happened twice to me on this
>machine today.  (Actually, it happened a third time, but the know bug in
>AUTOLOGOUT was responsible that time.)
>I get a line on my xterm that looks as though xess quit peacefully:
>	[1]  + Done                 xess steam_tbl.xs
>The xess window with its background and cursor remain on my display (until
>I logged out), but the foreground does not refresh.
>This problem seems to be specific to milanese, as I logged into an athena
>workstation remotely and used xess for quite some time with no problems.
>I think that the first time it crashed, there were about 10 users on milanese,>
>and the second about 30.  I have seen the load much worse though.
>
>What should have happened:
>
>Of course, it should keep on running.  But if it has to crash, it ought to
>at least state the reason.
>
>Please describe any relevant documentation references:
>
>
>From rdhamlin@MIT.EDU Sat Apr 30 23:44:52 1994
>Received: by gregor.MIT.EDU (5.57/4.7) id AA08634; Sat, 30 Apr 94 23:44:51 -04>00
>Received: from MILANESE.MIT.EDU by MIT.EDU with SMTP
>	id AA02127; Sat, 30 Apr 94 23:44:49 EDT
>From: rdhamlin@MIT.EDU
>Received: by milanese.MIT.EDU (5.57/4.7) id AA15991; Sat, 30 Apr 94 23:44:47 ->0400
>Message-Id: <9405010344.AA15991@milanese.MIT.EDU>
>To: bugs@MIT.EDU
>Subject: decmips 7.6G: xess
>Date: Sat, 30 Apr 94 23:44:47 EDT
>
>System name:		milanese
>Type and version:	KN02ca 7.6G (1 update(s) to same version)
>Display type:		
>
>What were you trying to do?
>use xess---just entering data/formulas
>
>What's wrong:
>
>xess abruptly quit on me without warning.  This happened twice to me on this
>machine today.  (Actually, it happened a third time, but the know bug in
>AUTOLOGOUT was responsible that time.)
>I get a line on my xterm that looks as though xess quit peacefully:
>	[1]  + Done                 xess steam_tbl.xs
>The xess window with its background and cursor remain on my display (until
>I logged out), but the foreground does not refresh.
>This problem seems to be specific to milanese, as I logged into an athena
>workstation remotely and used xess for quite some time with no problems.
>I think that the first time it crashed, there were about 10 users on milanese,>
>and the second about 30.  I have seen the load much worse though.
>
>What should have happened:
>
>Of course, it should keep on running.  But if it has to crash, it ought to
>at least state the reason.
>
>Please describe any relevant documentation references:
>
>

home help back first fref pref prev next nref lref last post