Fujitsu M10 Product Notes page 81

Table 3-5 Problems that might occur with XCP 2240 and workarounds (continued)
SPARC M10-
RTI No. 1 4 4S
RTIF2- x x x
140507-004
RTIF2- x x x
140507-005
RTIF2- x x x
140507-006
RTIF2- x x
140507-007
RTIF2- x
140507-008
Description
showpparprogress(8) command
mistakenly shows the status of the
procedure of powering on the system.
In a system which implements daylight
saving time, if the current time is
changed with the "setdate -s" command
to a time that is within one hour of the
ending of daylight saving time, the time
is changed to a time beyond daylight
saving time.
[Example]
If the ending of daylight saving time be
October 31 AM 2:00 and the local time
being attempted to set to October 31 AM
1:40 (JDT), the time is set to the standard
local time of October 31 AM 1:47 (JST).
XSCF> showdate
Wed Apr 30 10:16:57 JDT 2014
XSCF> setdate -y -s 103101402014.00
Fri Oct 31 01:40:00 JST 2014
The XSCF will be reset. Continue? [y|n]
:y
Thu Oct 30 16:40:00 UTC 2014
XSCF> showdate
Fri Oct 31 01:47:16 JST 2014
If a failure is detected in DC-DC
converter (DDC), the "Power subsystem
failure" error log may be registered twice.
When error logs (Critical ultrahigh
temperature at XXX) at the time of
abnormality of components due to high
temperature (ultrahigh temperature
level) are registered and the system is
forcibly stopped, if the "showlogs power"
command is executed, the "Cause"
column of power log may show "-".
After a DC-DC converter (DDC) fault has
been detected, if the system is run
continuously without replacing the FRU
that appears in the error logs, the
following error is mistakenly detected at
every turning off of input power.
Msg: Power-off failure
The testsb(8) command detects the
"STICK Stop Register error (does not
stop)" or the "STICK does not stop
(CPU)" error message and may fail.
Workaround
showpparprogress(8) command for the
right display.
To set up the local time to something
around the daylight saving time, use the
"setdate -u" command and set the time in
UTC.
There is no effective workaround.
Ignore the 2nd error log. Moreover,
replace the faulty FRU as soon as possible.
There is no effective workaround.
Replace the faulty FRU. Moreover, as this
error message has no effect on the
functioning of the system, ignore it.
There is no effective workaround.
[How to Restore]
Collect diagnosis information by
executing the snapshot(8) command.
Chapter 3 Information on Software 67