Article View: comp.sys.dec
Article #2672Re: Cache parity errors in the error logger for Ultrix
From: Erik C. Sowa
Date: Wed, 07 Oct 1992 21:11
Date: Wed, 07 Oct 1992 21:11
13 lines
1246 bytes
1246 bytes
>>>>> "Max" == Max Maklin <maklinm@cognos.com> writes: Max> The answer was that in Ultrix 4.2A a flag that was being set on cache Max> parity errors was now being reported to the error logger along with other Max> informational messages. It is thus a feature rather than an oversight Max> and should be treated thus. The idea is that if the count starts to Max> increase very rapidly, this could be warning of a CPU problem. As a fellow "victim" of the cache parity error messages, I would like to know more about this. Why do they occur? What rate indicates a problem? What software is likely to cause them? When should I start to worry? -- erik sowa (sowa@amdew.llnl.gov)
Technical Details
Message-ID:
<SOWA.92Oct7141113@amdew.llnl.gov>Path:
arc1-ca.pugleaf.net!sparky!uunet!paladin.american.edu!darwin.sura.net!sgiblab!pacbell.com!lll-winken!sowaReferences:
<1992Oct6.234449.17673@cognos.com>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!sparky!uunet!paladin.american.edu!darwin.sura.net!sgiblab!pacbell.com!lll-winken!sowa From: sowa@amdew.llnl.gov (Erik C. Sowa) Newsgroups: comp.sys.dec Subject: Re: Cache parity errors in the error logger for Ultrix Message-ID: <SOWA.92Oct7141113@amdew.llnl.gov> Date: 7 Oct 92 21:11:13 GMT References: <1992Oct6.234449.17673@cognos.com> Sender: usenet@lll-winken.LLNL.GOV Organization: LLNL Chemistry and Materials Science Lines: 13 Nntp-Posting-Host: amdew.llnl.gov In-reply-to: maklinm@cognos.com's message of 6 Oct 92 23:44:49 GMT