🚀 go-pugleaf

I would like to start off first by saying thanks to Digital for
looking into this for me (especially the local office).  Seems
my original post on the what these cache parity errors was
somewhat construed as a flame and I while I was frustrated in
not able to get an answer, I should be more careful when wording
posts, especially as they are many people in Digital who read
this group and do not like to see unhappy campers.

The original question came about when all of the sudden I started
receiving cache parity errors on my DECSystem 5500 running Ultrix 4.2A.
The problem was compounded in that at the time I did the upgrade I was
also receiving an FCO, which I mistakingly thought to be the cause.
I saw many other posts about this but no followups to the newsgroup.
I myself went through Customer Support and they too could not give
me a solid answer.  The call was escalated, but still to no avail.

Some people had been told it was a debug flag that had been left on
and made it to distribution.  While this was close, it gave the impression
that someone had forgotten to turn it off which is not the case.

The answer was that in Ultrix 4.2A a flag that was being set on cache
parity errors was now being reported to the error logger along with other
informational messages.  It is thus a feature rather than an oversight
and should be treated thus.  The idea is that if the count starts to
increase very rapidly, this could be warning of a CPU problem.

There was no mention in the manuals, and it appears many people within
Digital are also unaware of it.  I believe my source had to actually
end up talking to the particular engineering group to get the correct
answer.

Again I apologize to Digital, and wish again to thank them for helping
me answer my question.

Cheers,

Max
-- 
Max Maklin                                                P.O. Box 9707 
Technical Analyst	                           3755 Riverside Drive
Cognos Incorporated                              Ottawa, Ontario CANADA
Internet: maklinm@cognos.COM                 UUNet: maklinm@cognos.UUCP