[2660] in Release_7.7_team
[cfox@MIT.EDU : blank screen during update]
daemon@ATHENA.MIT.EDU (Greg Hudson)
Thu Mar 22 11:40:53 2001
Date: Thu, 22 Mar 2001 11:40:44 -0500
Message-Id: <200103221640.LAA16266@nephthys.mit.edu>
From: Greg Hudson <ghudson@MIT.EDU>
To: release-team@mit.edu
So, this is quite the issue. It looks from my point of view like this
happens to every Solaris machine which auto-updates (a manual
"update_ws" doesn't see this problem), and while the update succeeds,
anyone who happens to be looking at it during the process will assume
that the machine has hung and will likely interrupt the update.
Normally, I would say, "okay, looks like we need to do a miniroot
update," since we have the machinery in place for that. But it so
happens that miki discovered yesterday that the miniroot doesn't work
for machines already running Solaris 2.7 (afsd hangs, even if you
clear the cache first; it's not clear what afsd can see on a 2.7
machine that's different from a 2.6 machine, so it's hard to know what
to look at).
So, options:
* Put a loud warning in mail to release-announce. Suboptimal
because not everyone who watches machines auto-updating is
on release-announce, and even people who are might not read
the mail or might not read it or remember it.
* Fix the problem. Optimal, but could take a while.
* Give up on trying to put out these Solaris patches.
------- Forwarded transaction
[4566] daemon@ATHENA.MIT.EDU (Camilla R Fox) testers 03/22/01 10:52 (22 lines)
Subject: blank screen during update
Message-Id: <200103221551.KAA21399@myxomycete.mit.edu>
To: testers@MIT.EDU
Cc: ajfox@MIT.EDU, wdc@MIT.EDU
In-Reply-To: <200103221502.KAA00632@whirlwind.mit.edu>
Date: Thu, 22 Mar 2001 10:51:59 -0500
From: Camilla R Fox <cfox@MIT.EDU>
When I walked into SIPB last night, xcb (ultra 10) was at a blank white
screen, pinging, but not answering athinfo. I didn't figure out that
it was in the middle of an update, but I got distracted by a user and
wandered off after poking at the keyboard a bit.
When I came back, it was booting up, and I figured out that it had taken
an update. The update.log looks normal.
As well as Abby, I know Bill assumed that an ultra he was updating
yesterday had crashed in mid-update. He booted the machine and re-tried
the update; I didn't hear what happened to that, or the exact symptoms,
though.
-Camilla
--[4566]--
------- End forwarded transaction
