Fujitsu M10 Product Notes page 86

Table 3-5 Problems that might occur with XCP 2240 and workarounds (continued)
SPARC M10-
RTI No. 1 4 4S
RTIF2- x x x
140605-006
Fujitsu M10/SPARC M10 Systems Product Notes for XCP Version 2240 ･ March 2015
72
Description
540.....570.....600.....630.....660.....690.....720
.....750.....780.....\
810.....840.....870.....900.....930.....960.....990
.....1020.....1050.....-
1080.....1110.....1140.....1170.....end
Timeout detected during unconfiguration
of PSB#00-0.
XSCF>
When the OS panics, a large volume of
panic messages may be sent to the XSCF.
In this case, the XSCF cannot handle the
large volume of panic messages. As a
result, the codd process fails and
OS-panic error logs are registered in
large quantities as shown below.
[Example] OS panic and process failure
error logs
XSCF> showlogs error -v
Date: Dec 20 14:44:26 JST 2013
Code: 40000000-00ffff0000ff0000ff-
01b900060000000000000000
Status: Warning Occurred: Dec 20
14:44:26.513 JST 2013
FRU: /UNSPECIFIED
Msg: XSCF command: System status
change (OS panic) (PPARID#00, path: 00)
Diagnostic Code:
00000000 00000000 0000
00000000 00000000 0000
00000000 00000000 0000
00000000 00000000 00000000 00000000
00000000 00000000 0000
Date: Dec 20 15:00:01 JST 2013
Code: 20000000-00fcff00b0000000ff-
010400010000000000000000
Status: Notice Occurred: Dec 20
14:59:56.838 JST 2013
FRU: /FIRMWARE,/XBBOX#81/XSCFU
Msg: SCF process down detected
Diagnostic Code:
00000000 00000000 0000
51000000 00000000 0000
00000000 00000000 0000
636f6464 2e323537 382e627a 32000000
00000000 00000000 0000
You can check codd by confirming that
the first four bytes on the fourth line of
the [Diagnostic Code:] have the value
"636f6464".
Workaround
There is no effective workaround.
[How to restore]
The system is restored when the XSCF is
reset by codd process failure.