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

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-mbc.fe

Fujitsu fault codes:

01920101, 01920201, 01920468, 15072200, 15072206, 15072300,
15072301, 15072302, 15072303, 15072304, 15072305, 15072306,
15072307, 15072308, 15072309, 1507230A, 1507230B, 02000303,
02000304, 02000305, 02000306, 02000e00, 02001602, 02001603,
02001b04, 02001b05, 02001b06, 02001b07, 02001e00, 02001e02,
02001f00, 02002500, 02002501, 02002502

Details

Type

Hardware Fault

   mbc.fe

Severity

Major

Description

Fault due to a fatal internal error detected by an MBC chip within itself. This fault can occur on the Motherboard of an M12-1 system, the MBC chip that resides on the CMUL of an M12-2/M12-2S system, or on the XSCFU of an XB-Box.

Faults dealing with the portion of an MBC chip that interfaces with an LSB can be detected by POST. If the fault was detected while running POST, then such event is shown in the following categories:

- fe-cmuch-reg-ue:

02000e00, 02001602, 02001603, 02001b04, 02001b05, 02001b06, 02001b07

An error is detected by writing to the registers of the CMUCH and not getting the expected result when reading back

- fe-stick-err:

02000303, 02000304, 02000305, 02000306

An error is detected by checking stick function

- fe-sram-cmp-err:0

2001e00

An error is detected by writing to SRAM and not getting the expected result when reading back

- fe-sram-data-setup-err:

02001e02

The SRAM appears not be set up correctly when POST looks at it (for example, the SRAM magic number is incorrect)

- fe-fmem-chksum-err:

02001f00

An error is detected when checking the flash memory checksum

- fe-tty-overflow:

02002500, 02002501, 02002502

An error is detected by checking tty function

Other faults are managed by XSCF firmware.

Automated Response

If this failure is detected while PPAR is working, no immediate action is taken. The affected part is marked to be deconfigured, and on next starting up of the part, the following behaviour will be seen:

For M12-1 or M12-2 systems, if this is an MBC internal fault that affects the whole chip, then the platform becomes unbootable.

For M12-2S systems, if this is an MBC internal fault that affects the entire MBC chip, which is placed on CMUL or XSCFU, this building block is deconfigured.

For M12-2S systems, if this is an MBC internal fault that affects the entire MBC chip, which is placed on XSCFU in an XB-Box, this XB-Box is deconfigured.

If this failure is detected while the part is starting up, the part, as described above, will be deconfigured immediately.

Impact

For M12-1 or M12-2 systems, the platform is deconfigured.

For M12-2S systems, when failure is detected on CMUL or XSCFU, this building block is deconfigured.

For M12-2S systems, when failure is detected on XSCFU in an XB-Box, this XB-Box is deconfigured.

Indicted Hardware

For M12-2 systems, CMUL or XSCFU is marked for replacement.

For M12-2S systems, when failure is detected on CMUL, CMUL is marked for replacement.

For M12-2S systems, when failure is detected on XSCFU, XSCFU is marked for replacement.

For M12-2S systems, when failure is detected on XSCFU in an XB-Box, the XSCFU is marked for replacement.

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