SPARC M7-8
 
SPARC T7-4
 
Oracle SuperCluster M7 Hardware
 
SPARC M8-8
 
SPARC T7-2
 
Oracle SuperCluster M8 Hardware
 
SPARC M7-16
 
SPARC T7-1
 
Sun Fire V490 Server
 

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

Applies to:

Purpose

Provide additional information for message ID: PCIEX-8000-5Y

Details

Predictive Self-Healing Article
PCIEX subsystem problem

Type

Fault

   fault.io.pci.device-invreq

Severity

Major

Description

The transmitting device sent an invalid request.

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

Ensure that the latest drivers and patches are installed. Otherwise schedule a repair procedure to replace the affected device(s). Use fmadm faulty to identify the devices or contact Oracle for support.

Details

The transmitting device sent an invalid request.

This message occurs when a PCI driver queries a component which does not support the request. The request was correctly formed and has not incurred any detected error during transport, however the transaction cannot be fulfilled due to a variety of reasons including illegal access, improper address or invalid command for this device.

This is most likely caused by a piece of software that is not aligned with the capabilities of the PCI component(s) pointed to by this message. The component(s) are listed in the "Affects" portion it's location is listed in the "FRU" portion of "fmadm faulty" or "fmdump" output.

It is extremely unlikely that this is a hardware problem and replacing hardware is not warranted unless it is verified that software is not the root cause.

Verify that the patches associated with the component(s) and FRU(s) are up to date. This should include OS level PCI driver patches as well as any potential firmware patches for the device itself. Apply current versions of any patches not up to date to reduce the potential of this error re-occurring.

Step 1: Find the 36 character EVENT_ID string associated with the fault.

The EVENT_ID can be located using either the fmdump (1M) or fmadm (1M) commands or from the fault message displayed in the console output at the time of the fault. fmdump output is shown in Example 1.1 below.

Note: Be sure to get the correct 36 character EVENT_ID string if more than one is listed. You can identify the correct string by associating the fault with the date and time stamp from the fmdump output. fmadm faulty shows the EVENT_ID (highlighted in blue).

 Example 1.1 - finding the EVENT_ID (36 character string):

 

# fmdump
TIME                    UUID                                 SUNW-MSG-ID
Feb 17 19:36:38.5312    eccf460a-968b-e005-85ac-aecb6e4b7214 PCIEX-8000-5Y

 

Step 2: Use the command; fmadm faulty -u EVENT_ID, to locate the affected components, where EVENT_ID consists of the 36 character string obtained in Step 1 above. The component is located on the FRU(in bold below)  See Example 2.1.

 

Example 2.1 - determining affected component(s):

# fmadm faulty -u  eccf460a-968b-e005-85ac-aecb6e4b7214

---------------        ------------------------------------ -------------- ---------
TIME                   EVENT-ID                             MSG-ID         SEVERITY
---------------        ------------------------------------ -------------- ---------
Feb 17 19:36:38.5312  eccf460a-968b-e005-85ac-aecb6e4b7214 PCIEX-8000-5Y   Major



Fault class : fault.io.pci.device-invreq 33%
Affects     : dev:////pci@8,600000/SUNW,qlc@4
             faulted but still in service

FRU         : "MB" (hc://:component=MB)
            faulty

Fault class : fault.io.pci.device-invreq 33%

Affects     : dev:////pci@8,600000/ethernet@1
             faulted but still in service

FRU         : "PCI 1" (hc://:product-id=SUNW,Sun-Blade-1000:server-id=blade/motherboard=0/hostbridge=0/pcibus=0/pcidev=1)
             faulty

Step 3: Identify the software component(s) that needs to be repaired.

Software under suspicion in this example would be associated with the hardware components listed in the "Affects" field of the output, in this example ethernet or else the QLC chip on the motherboard. Note that both are PCI and not PCIe. Any drivers or firmware for either component need to be checked for currency. Check My Oracle Support for patches with pci and, in this example, ethernet and qlc keywords to search for possible updated patches.

If patches are applied, run the command; fmadm repair EVENT_ID in order to clear the fault status of the hardware components.

In the case that there are no patches, the applicable patches are current or if the problem reappears after applying patches, contact your service provider with the above information. Your service provider may request additional information to attempt to further isolate the issue.

This solution has no attachment