Asset ID: |
1-79-1536606.1 |
Update Date: | 2017-03-16 |
Keywords: | |
Solution Type
Predictive Self-Healing Sure
Solution
1536606.1
:
M10-jtag.device - JTAG write failure to a specific chip
Related Items |
- Fujitsu M10-4
- Fujitsu M10-1
- Fujitsu M10-4S
|
Related Categories |
- PLA-Support>Sun Systems>Sun_Other>Sun Collections>SN-OTH: Sun PSH
|
In this Document
Applies to:
Fujitsu M10-1 Fujitsu M10-4 Fujitsu M10-4S SPARC
Purpose
Provide additional information for message IDs: M10-jtag.device
Fujitsu fault codes:
01920203, 01920213
Details
Type
- Hardware Fault
- jtag.device
Severity
- Major
Description
-
Fault due to a JTAG write failure to a specific chip.
The JTAG write operation is performed when configuring the chips. JTAG is used to access CPU chips or XB chips on XBU.
Automated Response
- If this fault takes place while the platform is powering up or while a FRU is powering up, then the FRU with the chip will not be configured into the system.
Otherwise, no immediate action is taken. The platform administrator should schedule a service action.
Impact
- If the chip being accessed is a CPU chip: The CPU chip is deconfigured when the PPAR using the CPU chip reboots.
NOTE: For M10-1, this means the platform will become unbootable. If the chip being accessed is an XB chip: An XB way of PPARs which are using this XB chip is deconfigured.
Indicted Hardware
- If the chip being accessed is a CPU chip:
For M10-1 systems, the MBU is marked for replacement. For M10-4/4S systems: The CMUU or CMUL, where the faulty CPU chip is mounted, is marked for replacement. If the first suspect is CMUU, there is a small chance that MBC on CMUL is faulty. If the chip being accessed is a XB chip: For M10-4S systems, the XBUQ is marked for replacement. There is small chance that MBC on CMUL is faulty. For XB-Box, the XBUX is marked for replacement. There is small chance that MBC on MSCFUX is faulty. For M10-4/4S system with 4 CPU chip in a box, configuration of the PCIe fabric will be changed, triggered by CPU chip deconfiguration. This takes place when ioreconfigure is set to true by setpparmode command.
Configuration of PCIe fabric is changed as follows:
- When CPU#0 on CMUL is deconfigured: Configuration of PCIe switch 0 is changed to allow access from CPU#0 on CMUU to the built-in SAS chip, USB chip and GbE i/f #0 and #1. Configuration of PCIe switch 1 is changed to allow access from CPU#0 on CMUU to the first PCIe slot.
- When CPU#1 on CMUL is deconfigured: Configuration of PCIe switch 2 is changed to allow access from CPU#1 on CMUU to the fourth and fifth PCIe slots. Configuration of PCIe switch 3 is changed to allow access from CPU#1 on CMUU to the eighth and ninth PCIe slot.
- When CPU#0 on CMUU is deconfigured: Configuration of PCIe switch 0 is changed to allow access from CPU#0 on CMUL to the built-in GbE i/f #2 and #3. Configuration of PCIe switch 1 is changed to allow access from CPU#0 on CMUL to the second and third PCIe slots.
- When CPU#1 on CMUU is deconfigured: Configuration of PCIe switch 2 is changed to allow access from CPU#1 on CMUL to the sixth and seventh PCIe slots. Configuration of PCIe switch 3 is changed to allow access from CPU#1 on CMUL to the tenth and eleventh PCIe slot.
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
|