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

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

In this Document

Purpose

Details

References

Applies to:

Purpose

Provide additional information for message ID: M12-asic.power.fail

Fujitsu fault code:

01A70100, 01A70103, 01A70104, 01A70130, 01A70132, 01A70133, 01A70160,
01A70162, 01A70163, 01A70201, 01A70205, 01A70231, 01A70234, 01A70261,
01A70264, 01A70306, 01A70335, 01A70336, 01A70365, 01A70437, 01A70538,
01A7063a, 01A7063c, 01A7063d, 01A7063e, 01A7073b, 01A7073f

Details

Type

Hardware Fault

   asic.power.fail

Severity

Major

Description

There are two types of faults that are detected:

-A failure reading or writing an interrupt mask for a particular ASIC or CPU chip, due to a power failure the affects the ASIC or CPU chip.  The power failure will cause its own ereport/fault, and this fault just logs an additional symptom of the power failure.  The following types of chips can be identified at failure:

-A CPU chip;
-An XB chip
-An MBC chip

-A fatal error happens on an ASIC (a failure that would normally produce an fatal error, such as 05010000). However, when this fatal error occurs the XSCF detects that a DDC failure has occurred, and thus produces a power failure event instead of a fatal error. For this type of fault, only the fact that the fault occurred is known (not even the type of ASIC that had the fatal error is identified).

Automated Response

If this is a power failure of a Motherboard on an M12-1 or M12-2 system, the entire platform is reset.

If this is the power failure of a Building Block on an M12-2S system, then reset all the domains in the PPAR for the Building Block.

If this is a power failure of an XB-Box on a M12-2S system, then the PPARs, which are using the XB-Box to form a PPAR, is reset.

Impact

Nothing is deconfigured. It is expected that another fault will identify the part to be deconfigured.

Indicted Hardware

Depending on where the failure is detected, the suspect is as listed below:

When this failure happened on M12-1, MBU is the suspect.
When this failure is detected on CMUU/CMUL on M12-2/2S, CMUL is the suspect.
When this failure is detected on XBU on M12-2/2S, XBU is the first suspect, and CMUL is the second suspect.
When this failure is detected on XBUX on XB-Box, XBUX is the first suspect.  And, there is slight chance XBBPX is faulty.

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)

This solution has no attachment