Sable CPU Module Specification

Sable CPU Module Specification Sable CPU Module Specification

people.freebsd.org
from people.freebsd.org More from this publisher
20.02.2013 Views

Copyright © 1993 Digital Equipment Corporation. If the location found in the B-Cache does not have the same address as the address found in the EV-FILL_ADDR register then the error occurred on the data bus between the 21064 and C4. Generally this type of error is indicative of a hard fault; however if a simple test of the interface passes then the error may be recoverable after scrubbing affected locations and restarting the failing instruction. NOTE If the EDC error has a syndrome of 1F (which indicates an uncorrectable error), this means the data store of the cache was written with an intentionally bad EDC pattern as a result of the CUCERR L signal being asserted during a B-Cache read fill or write update. Refer to Chapter 8, Section 8.2.2 for further details. 7.1.1.3.5 B-Cache Data Single Bit EDC Error Current CPU B-Cache EDC Error C4 Detected Refer to Section 7.1.1.3.3. 7.1.1.3.6 B-Cache Data Uncorrectable EDC Error Current CPU B-Cache EDC Error C4 Detected Refer to Section 7.1.1.3.4. 7.1.1.3.7 21064 Data bus Single Bit EDC Error EDC error occurred on the bus as the data was being driven from the 21064 to the C4. Generally this type of error is indicative of a hard fault; however if a simple test of the interface passes then the error may be recoverable after scrubbing affected locations and restarting the failing instruction. Refer to Section 7.1.1.3.3. 7.1.1.3.8 21064 Data bus Uncorrectable EDC Error EDC error occurred on the bus as the data was being driven from the 21064 to the C4. Generally this type of error is indicative of a hard fault; however if a simple test of the interface passes then the error may be recoverable after scrubbing affected locations and restarting the failing instruction. Refer to Section 7.1.1.3.4. Exceptions and Interrupts 171

Copyright © 1993 Digital Equipment Corporation. 7.1.1.3.9 B-Cache Tag or Tag Control Parity Error Current CPU B-Cache Parity Error C4 Detected First the actual cause of the error should be determined. This is done by calculating the expected Tag Control and Tag parity based on the data latched in the B-Cache Uncorrectable Error Register, and the B-Cache Uncorrectable Error Address Register. The result will indicate whether the error was a Tag Control Store Error, a Tag Store error, or both. Tag Control Store Errors Restricted to reads only, PAL must scrub the parity error from the Tag Control store using the standard B-Cache initialization procedure. This error is FATAL to the context the cached location is referenced in. Tag Store Errors Restricted to reads only, PAL must scrub the parity error from the Tag store using the standard B-Cache initialization procedure, and if the Dirty bit on the cache block in question was set, a SYSTEM FATAL Error should be signaled to the system software. Otherwise only error logging is required. Refer to Chapter 8, Section 8.2.1, for further details. If a tag parity error occurs where an even number of tag bits change state, then during vicimization of a dirty cache block, it is possible to generate a WRITE DATA not ACK’ed error (causing a machine check). When this occurs a SYSTEM FATAL Error should be signaled to the system software. Refer to Section 8.4.3 for further details. 7.1.1.3.10 Cobra-bus Parity Error Based on logged information and simple R/W to devices on Cobra-bus determine nature of failure. Disable failing module if possible and restart execution otherwise system FATAL. Refer to Table 77 for further details. 7.1.1.3.11 Invalid Cobra-bus Address This error occurs when a process has mapped physical addresses in the system that don’t exist, or if an error on an address bus or a ‘‘double’’ bit error has occurred in a B- Cache Tag Store. PAL should verify that the error was a legitimately invalid address as a result of incorrect mapping and pass control to the access violation exception handler. If the address logged is a legitimate physical address, and no Cobra-bus parity errors have been logged, then it is SYSTEM FATAL. (Unprotected address bus or double bit parity protected address bus error) A C/A Parity Error may result in the C/A not ack’ed bit being set in one of the commander CSR’s. This is due to the fact that responders will not ack a C/A that has bad parity. 172 Exceptions and Interrupts

Copyright © 1993 Digital Equipment Corporation.<br />

If the location found in the B-Cache does not have the same address as the address<br />

found in the EV-FILL_ADDR register then the error occurred on the data bus between<br />

the 21064 and C4. Generally this type of error is indicative of a hard fault; however if<br />

a simple test of the interface passes then the error may be recoverable after scrubbing<br />

affected locations and restarting the failing instruction.<br />

NOTE<br />

If the EDC error has a syndrome of 1F (which indicates an uncorrectable error),<br />

this means the data store of the cache was written with an intentionally<br />

bad EDC pattern as a result of the CUCERR L signal being asserted during<br />

a B-Cache read fill or write update.<br />

Refer to Chapter 8, Section 8.2.2 for further details.<br />

7.1.1.3.5 B-Cache Data Single Bit EDC Error<br />

Current <strong>CPU</strong> B-Cache EDC Error C4 Detected<br />

Refer to Section 7.1.1.3.3.<br />

7.1.1.3.6 B-Cache Data Uncorrectable EDC Error<br />

Current <strong>CPU</strong> B-Cache EDC Error C4 Detected<br />

Refer to Section 7.1.1.3.4.<br />

7.1.1.3.7 21064 Data bus Single Bit EDC Error<br />

EDC error occurred on the bus as the data was being driven from the 21064 to the<br />

C4. Generally this type of error is indicative of a hard fault; however if a simple test<br />

of the interface passes then the error may be recoverable after scrubbing affected<br />

locations and restarting the failing instruction.<br />

Refer to Section 7.1.1.3.3.<br />

7.1.1.3.8 21064 Data bus Uncorrectable EDC Error<br />

EDC error occurred on the bus as the data was being driven from the 21064 to the<br />

C4. Generally this type of error is indicative of a hard fault; however if a simple test<br />

of the interface passes then the error may be recoverable after scrubbing affected<br />

locations and restarting the failing instruction.<br />

Refer to Section 7.1.1.3.4.<br />

Exceptions and Interrupts 171

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!