T5-4/T5-8 : PCIE fabric error panic or/and ereports on Oracle 8Gb Qlogic FC HBA card (QLE2562) populated slots (Doc ID 1559361.1)

Last updated on MARCH 26, 2024

Applies to:

Symptoms

Oracle 8Gb Qlogic FC HBA card (QLE2562)

HBA #1 = Option SG-XPCIE2FC-QF8-Z PN 371-4325 firmware will negotiate at PCIe Gen2 x4 speeds therefore should not be installed in T5 servers
Physical Service Item FRU: 371-4325
Packaged FRU: -
Marketing FRU: SG-XPCIE2FC-QF8-Z

HBA #2 = Option 7106958 / 7076908 PN 7076907 firmware will negotiate at PCIe Gen1 x8 speeds and can be installed on T5 servers
Physical Service Item FRU: 7076907
Packaged FRU: 7076908
Marketing FRU: 7106958

SPARC T5-4 and SPARC T5-8 systems configured with HBA #1(see legend above) may panic on a fabric error, referencing one of the HBA #1(see legend above) populated slots, or report ereports on HBA #1(see legend above) populated slots with the HBA running at PCIe Gen2.

++ PCIe panic ++

The stack may differ, however the common symptom will be various correctable events reported against installed HBA #1(see legend above), for example;

ereport.io.pci.fabric ena=2741168c7b21001 detector=[ version=0 scheme="dev"
device-path="/pci@380/pci@1/pci@0/pci@a" ] bdf=250 device_id=80bf vendor_id=
111d rev_id=3 dev_type=60 pcie_off=40 pcix_off=0 aer_off=100 ecc_ver=0
pci_status=10 pci_command=147 pci_bdg_sec_status=0 pci_bdg_ctrl=3 pcie_status=
1 pcie_command=12f pcie_dev_cap=8024 pcie_link_status=3042 pcie_dev_ctl2=0
pcie_adv_ctl=1e5 pcie_ue_status=0 pcie_ue_mask=0 pcie_ue_sev=460031
pcie_ue_hdr0=0 pcie_ue_hdr1=0 pcie_ue_hdr2=0 pcie_ue_hdr3=0 pcie_ce_status=
1100 pcie_ce_mask=0 remainder=1 severity=3

++ Correctable PCIe events ++

This is the most common symptom and will report correctable errors against the HBA #1(see legend above), for example from {snapshot}/fma/@usr@local@bin@fmdump_-ev.out;

ereport.chassis.post.io.pciex.correctable@/SYS/RCSA/PCIEx/CAR

++ PCIe link initialization failures ++

Another common fault is a failure by HyperVisor to correctly train the PCI links during initialisation, for example from {snapshot}/fma/@usr@local@bin@fmdump_-ev.out;

ereport.io.pciex.link-init-fail@/SYS/RCSA/PCIEx

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.