From: utzoo!decvax!ucbvax!info-vax
Newsgroups: fa.info-vax
Title: FPS AP-120B Array Processor
Article-I.D.: ucbvax.267
Posted: Tue Dec  7 22:34:35 1982
Received: Thu Dec  9 01:05:40 1982

>From ABOORNAZIAN@BBNG  Tue Dec  7 22:30:52 1982
Mail-From: ARPANET host BBNG rcvd at 6-Dec-82 1053-PST
Sender: ABOORNAZIAN@BBNG
To: info-vax@SRI-CSL
Cc: aboornazian@BBNG, depesa@BBNF, lanoue@BBNF, dipace@BBNF
Remailed-Date:  6 Dec 1982 2241-PST
Remailed-From: the tty of Geoffrey S. Goodfellow  <Geoff5 at SRI-CSL>
Remailed-To: Info-VAX@SRI-CSL: ;

We're having a problem with our AP-120B and I'd like to know
whether anyone else has seen something similar or has
suggestions.  Something in the interaction between the AP driver
and VMS during DMA transfers of results back from the AP to the
VAX causes the driver to get mixed up when the page it is trying
to write to is not in a working set.  One of two things happens
next.  Either the system crashes outright, or the AP hangs the
UNIBUS and it must be forcibly crashed (@CRASH).  This problem
appeared with the advent of VMS 3.0.  We are running the latest
version of the FPS software, the version which is supposed to
work with VMS 3.0.  Any clues would be greatly appreciated, and,
if you depend on an AP-120B and haven't gone to VMS 3.0, a word
to the wise is sufficient.