[1885] in Release_7.7_team
Re: U5's crashing after updating
daemon@ATHENA.MIT.EDU (Garry Zacheiss)
Tue Jul 27 12:01:33 1999
Message-Id: <199907271601.MAA21017@mccibm1.mit.edu>
To: Bill Cattey <wdc@MIT.EDU>
Cc: ops@MIT.EDU, release-team@MIT.EDU
In-Reply-To: Your message of "Tue, 27 Jul 1999 11:51:26 EDT."
<UrbRJyoGgE6e0H_co0@mit.edu>
Date: Tue, 27 Jul 1999 12:01:30 EDT
From: Garry Zacheiss <zacheiss@MIT.EDU>
I can't get time stamps on the rebooting message, but the time
stamp on the final line in /etc/athena/version should be a reasonable
indicator of whether or not the machines all took the update at the same
time. Here's the information for the machines I could reach:
Athena Workstation (sun4) Version 8.3.13 Tue Jul 27 05:33:10 EDT 1999
Athena Workstation (sun4) Version 8.3.13 Tue Jul 27 04:30:39 EDT 1999
Athena Workstation (sun4) Version 8.3.13 Tue Jul 27 05:28:29 EDT 1999
Athena Workstation (sun4) Version 8.3.13 Tue Jul 27 04:11:45 EDT 1999
Athena Workstation (sun4) Version 8.3.13 Tue Jul 27 05:15:05 EDT 1999
which correspond to, in order:
m56-129-17
m12-182-5
w20-575-94
rotch-32
rotch-36
Because the Sun update takes such a short time and these times are so
widely varying, I don't think the theory that some infrastructure glitch
would cause the problem is very plausible. I was awake during this
time, and there were no network outages that would effect machines in
all these locations; the same is true for power outages.
Since these machines are all 24 bit Ultra 5's, my first thought
would be to blame the framebuffer in these machines, since we've seen it
cause strange hangs on these machines before. Of course, I admit this
is just wild speculation.
Garry
