Appendix A
Fixed Issues
81
6730610
In certain circumstances you might encounter
these error messages when powering on a T5440
server:
Chassis | major: Jul 27 16:40:17
ERROR: dt_allocprop: prop == NULL:
Not enough memory to expand MD for
new property fwd
Chassis | major: Jul 27 16:40:17
ERROR: dt_allocnode: Not enough
memory to expand MD for new node
mblock
Chassis | critical: Jul 27 16:41:55
FATAL: The Service Processor
software has taken a FATAL
configuration error,
Chassis | critical: the HOST Process
cannot be started.
Chassis | critical: Please examine
the logs to determine the reason for
failure and then
Chassis | critical: reset the
Service Processor
This error is encountered when there is a large
difference between the amount of memory on
the different CMP and memory modules. For
example, this could happen if the memory on
CMP0+MEM0 added up to 128 Gbytes, but the
memory on CMP1+MEM1 were only 16 Gbytes.
This situation might happen in two different
situations; each situation has its own recovery
procedure.
Note - Fixed in System Firmware 7.1.8.a or later.
Case 1
- POST has determined that multiple
FB-DIMMS have failed on a T5440 with 64 8-Gbyte
FB-DIMMS
Recovery 1
- If POST takes a FB-DIMM offline,
you must replace it immediately. If replacing the
failed FB-DIMM is not immediately possible or
desired, you must disable the corresponding
FB-DIMMs on the other CMP/memory modules'
corresponding memory branches to guarantee a
contiguous memory configuration.
Type one of the following:
->
set /SYS/component component_state=
disabled
sc>
disablecomponent
asr-key
Type one of the following commands to display a
list of enabled and disabled devices:
->
show components
sc>
showcomponent
For each FB-DIMM device that is disabled, disable
the corresponding FB-DIMM associated with the
other CMP/memory module units. For example, if
the following device was disabled:
/SYS/MB/MEM0/CMP0/BR0/CH0/D1
then disable the following additional devices:
/SYS/MB/MEM1/CMP1/BR0/CH0/D1
/SYS/MB/MEM2/CMP2/BR0/CH0/D1
/SYS/MB/MEM3/CMP3/BR0/CH0/D1
Case 2
- You have added new FB-DIMM modules
to a T5440 server and have configured one of the
CMP/memory module pairs with significantly
more memory than the other modules
Recovery 2
- Reallocate the FB-DIMMs across the
CMP/memory modules to keep the total number
and types of FB-DIMMs the same on each
CMP/memory module pair.
TABLE A-4
Fixed Firmware and General Software Issues
(Continued)
CR ID
Description
Workaround
Summary of Contents for SPARC Enterprise T5440 Server
Page 4: ......
Page 18: ...8 SPARC Enterprise T5440 Server Product Notes December 2010 ...
Page 38: ...28 SPARC Enterprise T5440 Server Product Notes December 2010 ...
Page 58: ...48 SPARC Enterprise T5440 Server Product Notes December 2010 ...
Page 66: ...56 SPARC Enterprise T5440 Server Product Notes December 2010 ...
Page 92: ...82 SPARC Enterprise T5440 Server Product Notes December 2010 ...