Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!rutgers!cs.utexas.edu!uunet!cbmvax!grr
From: grr@cbmvax.UUCP (George Robbins)
Newsgroups: comp.unix.ultrix
Subject: Re: Hanging Ultrix XMI/BI systems
Message-ID: <8045@cbmvax.UUCP>
Date: 30 Sep 89 00:54:09 GMT
References: 
Reply-To: grr@cbmvax.UUCP (George Robbins)
Distribution: comp
Organization: Commodore Technology, West Chester, PA
Lines: 42

In article  saus@media-lab.media.mit.edu (Mark Sausville) writes:
> 
> Hardware: VAX 6320 with network, kdb50, ci (hsc), and 4 dmb32 (16xrs232)
> 
> The system hung...
> 
> This problem seemed to be entirely repaired by the new driver code.
> To make a long story short, the problem came back after about 6 weeks,
> and we have been seeing a hang every 24 hours or so.  After going
> through the story again with DEC, they recommended that we upgrade to
> 3.1, to ensure that we had good code.
> 
> We upgraded last night and (you guessed it) we had our first hang today.
> It was followed by a panic (progress?).

Please, when relating tales of woe, include enough "hard" information so
that others may correlate it with their own experience.  Which panic?  If
the system hangs, is it no echo, echo but no action, etc.  For a hang it
may help to know what module the PC was in etc.  Not to get carried away,
but just enough to "label" the problem.

> We're proceding with analysis of the problem, but turnaround on crash
> dumps with DEC is less than instant.  The DEC hardare people are going
> to get involved again, but they're a lot better on VMS.  I'm not
> asking for a diagnosis here.  I would like to hear from people who
> have had similar problems.

Sigh... I'm still working on/with DEC on the LAT cooked/cbreak/raw vs.
server passthru problem.  It took months to get them to *do* anything,
the first try didn't cut it and now they want to look at my machine
that worked just fine with 1.x and 2.x up till the intromission of
Ultrix 3.1. 

Sometime I think chapter 1 on the Ultrix installation manual should
be devoted to describing how to effectively work the software "support"
mechanism.  Getting from the "fixes to known problems" to the "define
and correct new bugs" is much bigger step then you'd want to imagine.

-- 
George Robbins - now working for,	uucp: {uunet|pyramid|rutgers}!cbmvax!grr
but no way officially representing	arpa: cbmvax!grr@uunet.uu.net
Commodore, Engineering Department	fone: 215-431-9255 (only by moonlite)