Sun Microsystems, Inc.  Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-79-2243429.1
Update Date:2017-08-14
Keywords:

Solution Type  Predictive Self-Healing Sure

Solution  2243429.1 :   M12-ioc.ch.leaf.se-no-credit-pci - Internal error detected by an IOC in a CPU chip  


Related Items
  • Fujitsu SPARC M12-1
  •  
  • Fujitsu SPARC M12-2S
  •  
  • Fujitsu SPARC M12-2
  •  
Related Categories
  • PLA-Support>Sun Systems>Sun_Other>Sun Collections>SN-OTH: Sun PSH
  •  




In this Document
Purpose
Details
References


Applies to:

Fujitsu SPARC M12-2S
Fujitsu SPARC M12-2
Fujitsu SPARC M12-1
SPARC

Purpose

Provide additional information for message ID: M12-ioc.ch.leaf.se-no-credit-pci

Fujitsu fault codes:

15050600, 15050601

Details

Type

Hardware Fault
   ioc.ch.leaf.se-no-credit-pci

Severity

Major

Description

Fault due to serious internal error detected by an IOC in a CPU chip.

Automated Response

No immediate action is taken.  However, the bus error may cause the domain to panic.  If the domain does not panic, then the domain does not require immediate attention. 
The platform administrator should make arrangements to make sure the domain does not use the IO Channel for an extended period of time.

Impact

Nothing is deconfigured.

Indicted Hardware

This is caused when PCIe device or PCIe switch does not respond. Therefore, IOC cannot specify “who” is not responding, maybe, it is onboard device, or PCIe card.
When this problem happens, a Solaris panic is quite likely.  Analyzing the panic dump, may show which PCIe device faced failure.

The fault affects an IOC.  Software on the domain may fail to access PCIe device.
If the fault was detected while running OBP, then there may be some subsequent error/fault caused by 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 hardware may be functioning, it is not intended nor recommended that the faulted component(s) remain in the system for a prolonged period of time.
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 Fujitsu M10 Diagnosis (Doc ID 1525156.1)


Attachments
This solution has no attachment
  Copyright © 2018 Oracle, Inc.  All rights reserved.
 Feedback