Fujitsu M10 Product Notes page 67

Table 3-5 Problems that might occur with XCP 2240 and workarounds (continued)
SPARC M10-
RTI No. 1 4 4S
RTIF2- x x x
140212-013
RTIF2- x x x
140212-014
RTIF2- x x x
140212-016
RTIF2- x
140212-021
Description
Due to the failure of a DIMM, the "CPU
internal fatal error", which suspects the
motherboard unit (MBU), CPU memory
unit lower (CMUL) or the CPU memory
unit upper (CMUU), may be registered
when powering on the physical partition
(PPAR).
Even if the "CPU cache degraded (CPU
#xx)" error is detected, the CHECK LED
of the operation panel may not light up.
When resetting XSCF, the "snmpd
[XXXXX] svrSP: error doAction
ACTION_CONTROL_LED" error
message regarding SNMP may be
displayed on the XSCF serial terminal.
If any of the physical partitions is reset
due to some hardware failure, in the
middle of the execution of the testsb(8)
command, the testsb(8) command may
terminate abnormally.
The following is an example of such an
error.
[Example]
XSCF> testsb PSB_NO
Initial diagnosis is about to start,
Continue?[y|n] :y
SB power on sequence started.
0.....30.....end
Initial diagnosis started. [7200sec]
0..... 30..... 60..... 90.....120.....150.....180.....
210.....240.....
270.....300.....330..
Hardware error occurred by initial
diagnosis.
SB power off sequence started. [1200sec]
0..... 30..... 60..... 90.....120.....150.....180.....
210.....240.....
270.....300.....330.....360.....390.....420.....450
.....480.....510.....
540.....570.....600.....630.....660.....690.....720
.....750.....780.....
810.....840.....870.....900.....930.....960.....990
.....1020.....1050.....
1080.....1110.....1140.....1170.....1200end
Failed to power off. Please check the FRU.
An internal error has occurred. Please
contact your system administrator.
done.
Workaround
There is no effective workaround.
If after replacing the MBU, CMUL or
CMUU in question, the same error is
registered again, replace all the DIMMs
that are mounted on the MBU, CMUL
and the CMUU.
There is no effective workaround.
There is no effective workaround.
Ignore this message.
There is no effective workaround.
[How to restore]
Execute maintenance on the failed
hardware after confirming it with the
showlogs(8) command.
After that, execute the testsb(8) command
again.
Chapter 3 Information on Software 53