info-vax@ucbvax.ARPA (09/17/84)
From: NEWMAN%SAV@LLL-MFE.ARPA
I asked around the company about the UDA50 problem and here is one of the
responses I got that seemed to make some sense. Hope this helps...
Gerard Newman
-------------------------------
Arpa: Newman%SAV@LLL-MFE.Arpa
USPS: Gerard Newman
Science Applications International
800 Oak Ridge Turnpike
Oak Ridge, TN 37830
AT&T: (615) 482-9031
--------------------------------------------------------------------------------
From: OAK::SECRIST 17-SEP-1984 08:24
To: LAJ::NEWMAN
Subj: RE: Any ideas ?
I had a VAX-11/750 with a UDA-50, RA80, under VAX/VMS Version 3.4...
and I had several WEIRD problems, some of which were our own doing
as we were writing a device driver that wasn't, well - correct. But
in the course of all this we asked out field service people about
fixing some of the maladies... and they researched all sorts of
funky symptoms on UDA-50s and got back to us with them. Most of them
were rejected - but yours sounds familiar somehow.
Ideas. There was one version on the formatter for the RAxxs that was
known to be faulty and cause bad things. Contact your field service
person and have him get you the LATEST rev of the formatter (I don't
rememeber what it was) and re-format your packs with that. (Not INIT,
or BAD, mind you - formatting.) That is a known bug about the vintage
of the V3.4 system you're talking about.
Secondly, if you get the latest rev. of the formatter you may find
when you find upon running it that it will want a higher rev. of the
UDA-50 microcode than is present in your controller. This is a
desirbale thing, because it helped me when I was having strange UDA-50
oddness. I think either "K" or "U" was the rev.-level, but I don't
really remember: the diag. will fail and say "you need at least rev.
level xxx to run this diagnostic".
I hope that helps - present this case to your field service people
and if it needs substantation I can call back the couple of local
DEC guys involved and get specifics for you.
Richard Secrist