SPARC T8-1
 
SPARC T8-4
 
SPARC M7-8
 
SPARC T7-4
 
Oracle SuperCluster M7 Hardware
 
SPARC M8-8
 
SPARC T8-2
 
SPARC T7-2
 
Oracle SuperCluster M8 Hardware
 
SPARC M7-16
 
SPARC T7-1
 

PLA-Support>Sun Systems>Sun_Other>Sun Collections>SN-OTH: Sun PSH
 

In this Document

Purpose

Scope

Details

References

Applies to:

Purpose

This document provides additional information for message ID: PCIEX-8000-YJ

Scope

Details

Type

Hardware Fault

   fault.io.pciex.bus-linkerr-corr

   fault.io.pciex.device-pcie-ce

Severity

Major

Description

Too many recovered PCI Express bus errors have been detected, which indicates a problem with the specified bus or with the specified transmitting device. This may degrade into an unrecoverable fault

Automated Response

One or more device instances may be disabled

Impact

Loss of services provided by the device instances associated with this fault

Suggested Action for System Administrator

The recommended service action for this event is to schedule replacement of the affected component(s) at the earliest possible convenience. Although the PCI Express link may be functioning, it is not intended nor recommended that the faulted component(s) remain in the system for a prolonged period of time.

SPARC T5-x systems can be affected by several CR's that cause a a failure diagnosis that can be resolved with patches.

Please see the following document:

Solaris 10 and Solaris 11 Fault Management Architecture (FMA) on SPARC T5-2 Systems May Report PCIEX-8000-YJ Major Events (Doc ID 2007819.1)

SPARC T5-2 PCIe fault events triggered by Replay Timeout errors (rto) exceeding threshold (Doc ID 1966605.1)

I/O SERD threshold values are set too low and may result in PCIEX-8000-J5, PCIEX-8000-YJ and PCIEX-8000-KP faults. (Doc ID 1617956.1)

 

For Fujitsu M10 platforms only, the XSCFU data should be collected and the information from the XSCF "showlogs error" command should be used to determine the resolution, in preference to using the Solaris PCIEX-8000-YJ fault diagnosis and indictment of any suspected faulty parts.

See bug 20547720 and, if applicable, add the customer SR to this bug.

Refer to the following document for the latest procedures for displaying event content in preparation for submitting a service request and applying any post-repair actions that may be required.

PSH Procedural Article for Solaris FMA-Based Diagnosis (Doc ID 1173733.1)

References

This solution has no attachment