🚀 go-pugleaf

Some time ago (seems like months), I posted a note concerning a conflict
between Masscomp's first release of X11 and tape operations. After some
sleuthing, I found a cryptic note that suggested that this problem would
go away if I got a newer rev. graphics controller (GCM.) At the same
time, I brought my cpu up to the current rev. level, and PRESTO-CHANGO
the problem went away.

The symptom of this problem is when the Xgcm server is running, the first
attempt to access the tape drive hangs the system. A stack backtrace from
the kernel debugger shows that the system issued a command "go" to the
tape device driver which never comes back (apparently because it gets 
munged by the GCM some how???) 

If you have this problem and are under service, they should bring you up
to date. If you don't have sevice, then you have to swap your boards. We
use the Module Mailer service (which is one part of the organization
that does not appear to have gotten confused by the merger of Masscomp
and Concurrent.)
-- 
Dale Chayes Lamont-Doherty Geological Observatory of Columbia University
Route 9W, Palisades, N.Y.  10964	dale@lamont.ldgo.columbia.edu
voice:	(914) 359-2900 extension 434	fax: (914) 359-6817



The MASSCOMP USERS' SOCIETY newsgroup is comp.sys.masscomp.
Articles to: masscomp@soma.bcm.tmc.edu or uunet!soma.bcm.tmc.edu!masscomp
Administrative stuff: masscomp-request@soma.bcm.tmc.edu
Stan Barber, Moderator