My Oracle Support Banner

[T5xx0, T3-x, T4-x, T5-x] System panics with 'Fatal error has occured in: PCIe fabric.(0x1)(0x43)' without any trace of HW failures (Doc ID 2850425.1)

Last updated on FEBRUARY 23, 2022

Applies to:

SPARC T3-1 - Version All Versions to All Versions [Release All Releases]
SPARC T3-2 - Version All Versions and later
SPARC T4-2 - Version All Versions to All Versions [Release All Releases]
Information in this document applies to any platform.
We can see that the Motherboard is OK:

MB 7310160-01 XXXXXX-XXXXXXXX 5030 CELESTI SPARC T3-1,MBD+TRAY OK

In ilom/@persist@hostconsole.log we will see:

panic[cpu53]/thread=2a102ed7c80: Fatal error has occured in: PCIe fabric.(0x1)(0x43)
000002a102ed76f0 px:px_err_panic+1cc (1a7e000, 7bea9000, 43, 2a102ed77a0, 1, 0)
%l0-3: 00000300093280c8 0000000001a7e000 0000000000000000 0000000000000001
%l4-7: 0000000000000034 0000000001a7e000 ffffffffffffffff 0000000000000000
000002a102ed7800 px:px_err_fabric_intr+1c0 (300085cc380, 1, 1a7e000, 1, 43, 700)
%l0-3: 0000000000000700 0000000000000001 0000000001a7e398 0000000001a7e000
%l4-7: 0000000001a7e390 0000000001a7e000 0000000000000001 0000030000b1b698
000002a102ed7970 px:px_msiq_intr+1e8 (600955533e8, 1, 300085e0bf8, 600957fdde8, 2, 2a102ed7a80)
%l0-3: 00000600957fa160 00000300085ddd08 00000600957ffd60 00000300085e0bf8
%l4-7: 0000000000000000 0000000003624040 0000000000000000 0000000000000030

ereport.io.pci.fabric ena=9e51840e17e0d401 detector=[ version=0 scheme="dev"
device-path="/pci@400/pci@2/pci@0/pci@f/pci@0" ] bdf=1100 device_id=8112 <--- internal HUB Controller embedded on the MB
vendor_id=10b5 rev_id=aa dev_type=70 pcie_off=60 pcix_off=0 aer_off=0 ecc_ver=
0 pci_status=6010 pci_command=547 pci_bdg_sec_status=a20 pci_bdg_ctrl=23
pcie_status=2 pcie_command=f pcie_dev_cap=20 pcie_link_status=11 remainder=3
severity=40

- severity=40 is translated into 'caused panic'

panic[cpu53]/thread=2a102ed7c80: Fatal error has occured in: PCIe fabric.(0x1)(0x100)
000002a102ed76f0 px:px_err_panic+1cc (1a7e000, 7bea9000, 43, 2a102ed77a0, 1, 0)
%l0-3: 00000300093280c8 0000000001a7e000 0000000000000000 0000000000000001
%l4-7: 0000000000000034 0000000001a7e000 ffffffffffffffff 0000000000000000
000002a102ed7800 px:px_err_fabric_intr+1c0 (300085cc380, 1, 1a7e000, 1, 43, 700)
%l0-3: 0000000000000700 0000000000000001 0000000001a7e398 0000000001a7e000
%l4-7: 0000000001a7e390 0000000001a7e000 0000000000000001 0000030000b1b698
000002a102ed7970 px:px_msiq_intr+1e8 (600955533e8, 1, 300085e0bf8, 600957fdde8, 2, 2a102ed7a80)
%l0-3: 00000600957fa160 00000300085ddd08 00000600957ffd60 00000300085e0bf8
%l4-7: 0000000000000000 0000000003624040 0000000000000000 0000000000000030

ereport.io.pci.fabric ena=9e51840e17e0d401 detector=[ version=0 scheme="dev"
device-path="/pci@400/pci@2/pci@0/pci@f/pci@0" ] bdf=1100 device_id=8112 <--- internal HUB Controller embedded on the MB
vendor_id=10b5 rev_id=aa dev_type=70 pcie_off=60 pcix_off=0 aer_off=0 ecc_ver=
0 pci_status=6010 pci_command=547 pci_bdg_sec_status=a20 pci_bdg_ctrl=23
pcie_status=2 pcie_command=f pcie_dev_cap=20 pcie_link_status=11 remainder=3
severity=100

- severity=100 is translated into 'device has no response'

In ilom/@usr@local@bin@spshexec_show_-script_@X@logs@event@list.out we will see that the OS is panicking:

824 Wed Dec 4 04:36:07 2002 System Log minor
Host: Solaris rebooting
823 Wed Dec 4 04:27:29 2002 System Log minor
Host: Solaris panicking
822 Fri Aug 31 05:37:39 2001 System Log minor
Host: Solaris running

For the above scenarios, we can see that the internal HUB Controller embedded on the MB failed, thus the Motherboard needs to be replaced
Path '/pci@400/pci@2/pci@0/pci@f/pci@0' controls the following, as per SPARC Platforms: Matrix of Recognized Device Paths (Doc ID 1005907.1)

DVD Drive /pci@400/pci@2/pci@0/pci@f/pci@0/usb@0,2/hub@4/device@4/storage@0

USB 0 (rear)
------------
USB 1.x /pci@400/pci@2/pci@0/pci@f/pci@0/usb@0,2/hub@2/device@1
USB 2.0 /pci@400/pci@2/pci@0/pci@f/pci@0/usb@0,2/hub@2/device@1


USB 1 (rear)
------------
USB 1.x /pci@400/pci@2/pci@0/pci@f/pci@0/usb@0,2/hub@2/device@2
USB 2.0 /pci@400/pci@2/pci@0/pci@f/pci@0/usb@0,2/hub@2/device@2

USB 2 (front)
-------------
USB 1.x /pci@400/pci@2/pci@0/pci@f/pci@0/usb@0,2/hub@4/storage@1
USB 2.0 /pci@400/pci@2/pci@0/pci@f/pci@0/usb@0,2/hub@4/storage@1

USB 3 (front)
-------------
USB 1.x /pci@400/pci@2/pci@0/pci@f/pci@0/usb@0,2/hub@4/storage@2
USB 2.0 /pci@400/pci@2/pci@0/pci@f/pci@0/usb@0,2/hub@4/storage@2

rmouse /pci@400/pci@2/pci@0/pci@f/pci@0/usb@0,2/hub@2/device@4/mouse@1
rcdrom /pci@400/pci@2/pci@0/pci@f/pci@0/usb@0,2/hub@2/hub@3/storage@2/disk@0
rkeyboard /pci@400/pci@2/pci@0/pci@f/pci@0/usb@0,2/hub@2/device@4/keyboard@0

Symptoms

Operating System (OS) panics and the system reboots.

Customer will report that the system panicked and there are no traces of HW faults.

Changes

 N/A

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution

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