Sun Fire[TM] 12K/15K/E20K/E25K: domain panic, "pcisch-XX : Fatal PCI bus error(s)"

Asset ID:	1-72-1617929.1
Update Date:	2017-11-08
Keywords:

Solution Type Problem Resolution Sure

Solution 1617929.1 : Sun Fire[TM] 12K/15K/E20K/E25K: domain panic, "pcisch-XX : Fatal PCI bus error(s)"

Applies to:

Sun Fire 12K Server - Version All Versions to All Versions [Release All Releases]
Sun Fire 15K Server - Version All Versions to All Versions [Release All Releases]
Sun Fire E20K Server - Version All Versions to All Versions [Release All Releases]
Sun Fire E25K Server - Version All Versions to All Versions [Release All Releases]
Information in this document applies to any platform.

Symptoms

A Sun Fire[TM] 12K/15K/E20K/E25K domain panics with the following panic string:

Jan 20 04:13:44 2014 panic[cpu165]/thread=2a1019bfc80: pcisch-13: Fatal PCI bus error(s)
Jan 20 04:13:44 2014
Jan 20 04:13:44 2014
Jan 20 04:13:44 2014 000002a101a27e60 pcisch:pbm_error_intr+158 (300d42a8440, 300a02ca240,
70084f00, 300a02ca240, 0, 300d492fcc0)

Cause

Possible faulty component

Solution

The pcisch driver may panic on Sun Fire 12K/15K/E20K/E25K domains due to a parity error on the

PCI Bus. In most cases this is due to a faulty hardware component. However, please provide the

following information, and contact Oracle to have the data reviewed for the root cause:

1. Provide the panic string from the console messages or /var/adm/messages.

2. Provide a new SC (system controller) and domain explorer

3. Provide the corefile for the event.

To determine the device path implicated in the pcisch panic stack above, please see below:

Reviewing the /etc/path_to_inst, we see that pcisch-13 is:

"/pci@fc,600000" 13 "pcisch"
"/pci@fc,600000/SUNW,qlc@1" 6 "qlc"
"/pci@fc,600000/SUNW,qlc@1/fp@0,0" 16 "fp"
"/pci@fc,600000/SUNW,qlc@1/fp@0,0/ssd@w50060e800547fd10,2c" 126 "ssd"
"/pci@fc,600000/SUNW,qlc@1/fp@0,0/ssd@w50060e800547fd10,2b" 128 "ssd"
"/pci@fc,600000/SUNW,qlc@1/fp@0,0/ssd@w50060e800547fd10,2a" 129 "ssd"
"/pci@fc,600000/SUNW,qlc@1/fp@0,0/ssd@w50060e800547fd10,29" 130 "ssd"

Then, use these documents to determine the location.

Sun Fire[TM] 12K, 15K, E20K, and E25K: Determining slot numbers from I/O device paths (Doc ID 1001879.1)

Sun Fire[TM] 12K/15K/E20K/E25K: Cheat Sheet: hsPCI, hsPCI+ and hsPCI-X Cartridge Locations (Doc ID 1017493.1)

In the above example, we find that the path maps to Expander 7 (EX7), IO board (IO7), PCI slot 0 ( C3V0 ) which is in the lower right-hand slot.

References

<NOTE:1001879.1> - Sun Fire[TM] 12K, 15K, E20K, and E25K: Determining slot numbers from I/O device paths
<NOTE:1017493.1> - Sun Fire[TM] 12K/15K/E20K/E25K: Cheat Sheet: hsPCI, hsPCI+ and hsPCI-X Cartridge Locations
<NOTE:1397146.1> - Sun Fire E20K/E25K Server: system continuously panics due to Fatal PCI bus error(s), even after hardware is replaced
<NOTE:1003311.1> - Sun Fire[TM] 12K/15K: PCI SERR "PCI error occurred on device #x"

Attachments

This solution has no attachment