Datasheet

Intel
®
E8870 Scalable Node Controller (SNC) Datasheet 3-37
Configuration Registers
Scalability Port Physical Layer Errors (Continued)
19 RCS 0 Unc
S2: SP Multi-Bit Data ECC Error
An uncorrectable ECC error was detected in data on an incoming flit.
The uncorrected data will be passed to the processor bus, memory
interface or configuration space. Section 6.1.1, “End-to-end Error
Correction” describes the action taken at these interfaces.
18 RCS 0 Corr
S3: Idle Flit Duplication Error
When a link is not carrying requests or responses, it is sending an idle
pattern. This bit is set when an error is detected in the pattern. It is an
indication of signaling problems on the link, but no information is lost.
17 RCS 0 Corr
S4: Parity Error on the Link
A parity error was detected in an incoming flit. If the Link Error bit is
not also set, Link Level Retry is in progress or has succeeded.
16 RCS 0 Corr
S5: SP Single-Bit Data ECC Error
An correctable ECC error was detected in data on an incoming flit. It is
not corrected at this point, but passed to the processor bus, memory
interface or configuration space. Section 6.1.1, “End-to-end Error
Correction” describes the action taken at these interfaces.
Scalability Port Protocol Layer Errors
15:10 RV 0 NA Reserved
9 RCS 0 Fatal
P1: SP Protocol Error
Log request header.
8RV0NAReserved
7 RCS 0 Fatal
P3: Received Failed or Unexpected Unsupported SP Request
Response Status
6 RCS 0 Fatal
P5: Strayed Transactions
Set when strayed transactions (responses with no matching requests)
are detected by the cluster.
5RCS0Unc
P6: Partial Merge Multi-Bit Data ECC Error
Set when a multi-bit ECC error is detected on a remote partial write.
4RCS0Corr
P9: Partial Merge Single-Bit Data ECC Error
Set when a single-bit ECC error is detected on a remote partial write.
3RCS0Corr
P8: Illegal SP Address Error
This includes access to SP port that is disabled or inoperative,
inbound SP requests with illegal attributes. See Section 4.5.3,
“Scalability Port Requests.”
2RCS0Corr
P10: Received Master Abort Response
The SNC received a Response with status = “master abort.” The SNC
will complete processor reads with all 1’s and drop any state
associated with writes.
If the response type in the RECSPP is PSNRM, the error should be
considered fatal rather than correctable. This response cannot be
generated by working hardware. After receiving this response, the
SNC does not guarantee continued operation.
If a request was generated to an inoperative or disabled SP port, the
SNC may have generated the master abort internally.
Device: NodeID
Function: 2
Offset: 80h(31:0), 84h(63:32), 88h(96:64) (Continued)
Bit Attr Default
ERR
Type
Description