Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!clyde!rutgers!husc6!cmcl2!brl-adm!umd5!grebyn!karl
From: karl@grebyn.UUCP
Newsgroups: comp.unix.wizards
Subject: Re: Ultrix1.2-uVaxII crashing - Help requested
Message-ID: <4682@grebyn.COM>
Date: Fri, 14-Aug-87 08:15:02 EDT
Article-I.D.: grebyn.4682
Posted: Fri Aug 14 08:15:02 1987
Date-Received: Sat, 15-Aug-87 17:24:54 EDT
References: <1988@batcomputer.tn.cornell.edu> <633@bingvaxu.cc.binghamton.edu>
Organization: Grebyn Corporation; Vienna, VA
Lines: 23

In article <633@bingvaxu.cc.binghamton.edu>, sullivan@marge.math.binghamton.edu (fred sullivan) writes:
> In article <1988@batcomputer.tn.cornell.edu> hurf@tcgould.tn.cornell.edu (Hurf Sheldon) writes:
> >
> > I have been getting the appended messages preceding a crash on
> > a uVaxII running Ultrix1.2 with the following hardware:
> >
> >machine check 82: write bus error, VAP is virtual
> 

[Text of first reply recommending replacement of memory board deleted to
make postnews happy.]

Another way that I fixed this problem when I encountered it was to pull any
other boards (e.g., controllers, etc.) out of the memory slots.  Although
you are supposedly allowed to have other boards in slots 2 & 3 of the Qbus,
I found there were some glitches that caused this sort of behavior.  So, I
threw the controllers further down the bus, and haven't had this sort of
problem since.

-- Karl -- 
DDN:	nyberg@ada20.isi.edu
INET:   karl@grebyn.com - AKA - karl%grebyn.com@seismo.css.gov
uucp:   {decuac, seismo}!grebyn!karl