20.02.2013 Views

Sable CPU Module Specification

Sable CPU Module Specification

Sable CPU Module Specification

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Copyright © 1993 Digital Equipment Corporation.<br />

Table 75: Uncorrectable Data Store Error Severity Matrix<br />

Address Context Dirty Severity<br />

User Yes Process Fatal if corrupted data used - Scrub<br />

No Scrub location - recoverable<br />

System Yes System Fatal if corrupted data used<br />

No Scrub location - recoverable<br />

The 21064 will detect Uncorrectable EDC errors only when executing a Load, or Load<br />

Lock instruction. When the error is detected the following sequence of events will<br />

occur:<br />

1. Data put into I or D-Cache (appropriately) unchanged, block gets validated.<br />

2. Machine check<br />

3. BIU_STAT: FILL_EDC set, and FILL_IRD set for I-Stream reference cleared for<br />

D-Stream. (FILL_SEQ set if multiple errors occur.)<br />

4. FILL_ADDR[33:5] & BIU_STAT[FILL_QW] gives bad quadword’s address<br />

5. If D-Stream FILL_ADDR[4..2] contain PA bits [4..2] of location which the failing<br />

load instruction attempted to read.<br />

6. FILL_SYNDROME contains syndrome bits associated with the failing quadword.<br />

7. BIU_ADDR,BIU_STAT[6..0] locked - contents are UNPREDICTABLE<br />

8. If I-Stream DC_STAT locked - contents are UNPREDICTABLE, If D-Stream DC_<br />

STAT locked, RA identifies register which holds the bad data, LW,LOCK,INT,VAX_<br />

FP identify type of load instruction<br />

9. BC_TAG holds the results of the external cache tag probe if the external cache<br />

was enabled for this transaction.<br />

When detected by the 21064 (as part of the machine check handler), if the physical<br />

address of the location with the Uncorrectable error is not resident in the B-Cache<br />

then the error was a bus error and should be re-tried.<br />

The B-Cache controller could detect the error under several different circumstances,<br />

and the way it is handled depends on how it was discovered. Table 76 shows the<br />

complete error handling matrix for B-Cache Data Uncorrectable errors detected by<br />

the B-Cache controller. Uncorrectable errors are detected/reported when a Systembus<br />

Reads HIT Dirty Locations, a B-Cache entry is victimized, or a masked write to<br />

a shared location occurs.<br />

When detected by the B-Cache Controller, if the physical address of the location with<br />

the Uncorrectable error is not resident in the B-Cache then the error was a bus error<br />

and severity of the error is the same as if a DIRTY B-Cache location was found with<br />

an Uncorrectable Error - this location should be flushed to main memory where it<br />

will be written with BAD EDC.<br />

184 Fault Management/Error Recovery

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

Saved successfully!

Ooh no, something went wrong!