Sable CPU Module Specification
Sable CPU Module Specification Sable CPU Module Specification
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
- Page 135 and 136: Copyright © 1993 Digital Equipment
- Page 137 and 138: 4.8 Multiprocessor Configuration CS
- Page 139 and 140: 4.9 System Interrupt Clear Register
- Page 141 and 142: 4.10 Address Lock Register - CSR13
- Page 143 and 144: 4.11 Miss Address Register - CSR14
- Page 145 and 146: Table 46 (Cont.): C4 Revision Regis
- Page 147 and 148: Table 48 (Cont.): Interval Timer In
- Page 149 and 150: Table 50: D-bus Microcontroller Clo
- Page 151 and 152: Figure 58: Granting Order rule 4 CP
- Page 153 and 154: Copyright © 1993 Digital Equipment
- Page 155 and 156: Table 54 (Cont.): BIU_CTL Field Des
- Page 157 and 158: Table 57: CPU EEPROM Defaults Locat
- Page 159 and 160: Copyright © 1993 Digital Equipment
- Page 161 and 162: Copyright © 1993 Digital Equipment
- Page 163 and 164: Copyright © 1993 Digital Equipment
- Page 165 and 166: Copyright © 1993 Digital Equipment
- Page 167 and 168: Copyright © 1993 Digital Equipment
- Page 169 and 170: Copyright © 1993 Digital Equipment
- Page 171 and 172: Copyright © 1993 Digital Equipment
- Page 173 and 174: Copyright © 1993 Digital Equipment
- Page 175 and 176: Copyright © 1993 Digital Equipment
- Page 177 and 178: Copyright © 1993 Digital Equipment
- Page 179 and 180: Copyright © 1993 Digital Equipment
- Page 181 and 182: Copyright © 1993 Digital Equipment
- Page 183 and 184: Copyright © 1993 Digital Equipment
- Page 185: Copyright © 1993 Digital Equipment
- Page 189 and 190: Copyright © 1993 Digital Equipment
- Page 191 and 192: Copyright © 1993 Digital Equipment
- Page 193 and 194: Copyright © 1993 Digital Equipment
- Page 195 and 196: Copyright © 1993 Digital Equipment
- Page 197 and 198: Copyright © 1993 Digital Equipment
- Page 199 and 200: Copyright © 1993 Digital Equipment
- Page 201 and 202: Copyright © 1993 Digital Equipment
- Page 203 and 204: Copyright © 1993 Digital Equipment
- Page 205 and 206: Copyright © 1993 Digital Equipment
- Page 207 and 208: Copyright © 1993 Digital Equipment
- Page 209 and 210: Copyright © 1993 Digital Equipment
- Page 211 and 212: CHAPTER 11 PHYSICAL AND ELECTRICAL
- Page 213 and 214: Table 81 (Cont.): MCA240 J5 SIDE 1
- Page 215 and 216: Table 82 (Cont.): MCA44 J1 Side 1 S
- Page 217 and 218: 11.3 CPU Module Max DC Power Requir
- Page 219 and 220: Copyright © 1993 Digital Equipment
- Page 221 and 222: Figure 68: module clocks Cobra - b
- Page 223 and 224: Table 85 (Cont.): System bus AC and
- Page 225 and 226: APPENDIX A ALPHA ARCHITECTURE OPTIO
- Page 227 and 228: Copyright © 1993 Digital Equipment
- Page 229 and 230: Copyright © 1993 Digital Equipment
- Page 231 and 232: Copyright © 1993 Digital Equipment
- Page 233 and 234: Copyright © 1993 Digital Equipment
- Page 235 and 236: Copyright © 1993 Digital Equipment
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