Processor Reset; Processor Error Handling - Intel BX80619I73820 Design Manual

PECI Interface
7.1.5.6

Processor Reset

The processor PECI client is fully reset on all RESET_N assertions. Upon deassertion of
RESET_N where power is maintained to the processor (otherwise known as a 'warm
reset'), the following are true:
• The PECI client assumes a bus Idle state.
• The Thermal Filtering Constant is retained.
• PECI SOCKET_ID is retained.
• GetTemp() reading resets to 0x0000.
• Any transaction in progress is aborted by the client (as measured by the client no
longer participating in the response).
• The processor client is otherwise reset to a default configuration.
7.1.5.7

Processor Error Handling

Availability of PECI services may be affected by the processor PECI client error status.
Server manageability requirements place a strong emphasis on continued availability of
PECI services to facilitate logging and debug of the error condition.
• Most processor PECI client services are available in the event of a CATERR_N
assertion though they cannot be guaranteed.
• The Ping(), GetDIB(), GetTemp(), RdPkgConfig() and WrPkgConfig() commands will
be serviced if the source of the CATERR_N assertion is not in the processor power
control unit hardware, firmware or associated register logic. Additionally, the
RdPCIConfigLocal() and WrPCIConfigLocal() commands may also be serviced in this
case.
• It is recommended that the PECI originator read Index 0/Parameter 5 using the
RdPkgConfig() command to debug the CATERR_N assertion.
— The PECI client will return the 0x91 completion code if the CATERR_N assertion
is caused by the PECI control hardware, firmware or associated logic errors. In
such an event, only the Ping(), GetTemp() and GetDIB() PECI commands may
be serviced. All other processor PECI services will be unavailable and further
debug of the processor error status will not be possible.
— If the PECI client returns a passing completion code, the originator should use
the response data to determine the cause of the CATERR_N assertion. In such
an event, it is also recommended that the PECI originator determine the exact
suite of available PECI client services by issuing each of the PECI commands.
The processor will issue 'timeout' responses for those services that may not be
available.
— If the PECI client continues to return the 0x81 completion code in response to
multiple retries of the RdPkgConfig() command, no PECI services, with the
exception of the Ping(), GetTemp() and GetDIB(), will be guaranteed.
• The RdIAMSR() command may be serviced during a CATERR_N assertion though it
cannot be guaranteed.
Thermal/Mechanical Specifications and Design Guide 91