DEFINITY Enterprise Communications Server Release 7
Maintenance for R7r
555-230-126
Issue 4
June 1999
Maintenance Object Repair Procedures
9-1348PROCR (RISC Processor Circuit Pack)
9
Processor Cache Parity Audit (#896)
This audit checks the state of the Cache Parity bit maintained by the R3000 CPU.
If this bit is set, there may be problems with either the CPU, the Instruction, or
Data Cache. An indication of bad cache parity won’t itself mean that the system
won’t operate, but minor to severe performance degradation may be present. For
example, a single bad bit in either cache could cause this bit to be set. If the
faulty word is seldom accessed, the impact will be small. If the bit is accessed
frequently, there could be serious problems with much, or all, of the cache (stuck
data bit) with the only direct indication again being the cache parity error or
cache test error.
Table 9-529. TEST #896 Processor Cache Parity Audit
Error
Code
Tes t
Result Description/ Recommendation
100 ABORT The requested test did not complete within the allowable time period.
1. Retry the command.
1022 ABORT Internal system error
1. Retry the command.
1335 ABORT This test is only run on the active SPE since the standby processor does not
use the cache memory. Cache failures may cause cause cache parity errors
on the active SPE which can be logged against a standby SPE is an SPE
interchange has taken place.
If a PROC 1026 error code is present in the hardware error log for a processor
on the standby SPE:
a. Enter the test memory long command to run the Processor Cache test
(#895) to verify that the cache has not failed.
b. Request an SPE interchange by entering reset system interchange
and run the short processor test sequence test processor while the
processor is on the active SPE.
c. If all test pass but a MAJOR alarm is present as a result of a 1026 error
in the hardware error log, replace the processor circuit pack since
multiple cache parity errors have occurred in the past and will probably
occur again which can cause call processing failures.
2500 ABORT Internal system error
1. Retry the command.
1338 ABORT The test is not allowed to run since a planned SPE interchange is in progress.
This may be caused by a planned interchange initiated automatically during 24
hour scheduled testing.
1. Wait 3 minutes and retry the command.
Continued on next page
