Intel Xeon E5520 P4X-DPE5520-226-8M586 User Manual

Product codes
P4X-DPE5520-226-8M586
Page of 154
Thermal Specifications
126
Intel
®
 Xeon
®
 Processor 5500 Series Datasheet, Volume 1
Note:
The codes explicitly defined in this table may be useful in PECI originator response 
algorithms. All reserved or undefined codes may be generated by a PECI client device, 
and the originating agent must be capable of tolerating any code. The Pass/Fail mask 
defined in 
 applies to all codes and general response policies may be based 
on that limited information.
6.3.5
Originator Responses
The simplest policy that an originator may employ in response to receipt of a failing 
completion code is to retry the request. However, certain completion codes or FCS 
responses are indicative of an error in command encoding and a retry will not result in 
a different response from the client. Furthermore, the message originator must have a 
response policy in the event of successive failure responses.
Please refer to the definition of each command in 
 for a specific definition 
of possible command codes or FCS responses for a given command. The following 
response policy definition is generic, and more advanced response policies may be 
employed at the discretion of the originator developer.
Table 6-28. Device Specific Completion Code (CC) Definition
Completion
Code
Description
0x00..0x3F
Device specific pass code
0x40
Command Passed
0x4X
Command passed with a transaction ID of ‘X’ (0x40 | Transaction_ID[3:0])
0x50..0x7F
Device specific pass code
CC: 0x80
Error causing a response timeout. Either due to a rare, internal timing condition or a 
processor RESET condition or processor S1 state. Retry is appropriate outside of the RESET 
or S1 states.
CC: 0x81
Thermal configuration data was malformed or exceeded limits.
CC: 0x82
Thermal status mask is illegal
CC: 0x83
Invalid counter select
CC: 0x84
Invalid Machine Check Bank or Index
CC: 0x85
Failure due to lack of Mailbox lock or invalid Transaction ID
CC: 0x86
Mailbox interface is unavailable or busy
CC:0xFF
Unknown/Invalid Mailbox Request
Table 6-29. Originator Response Guidelines
Response
After 1 Attempt
After 3 attempts
Bad FCS
Retry
Fail with PECI client device error
Abort FCS
Retry
Fail with PECI client device error. May be due to illegal command codes.
CC: Fail
Retry
Either the PECI client doesn’t support the current command code, or it has 
failed in its attempts to construct a response.
None (all 0’s) Force bus idle 
(1ms low), retry
Fail with PECI client device error. Client may be dead or otherwise non-
responsive (in RESET or S1, for example).
CC: Pass
Pass
n/a
Good FCS
Pass
n/a