Siemens SPARC ENTERPRISE M8000 User Manual
Page 32
24
SPARC Enterprise M8000/M9000 Servers Product Notes for XCP Version 1072 • September 2008
6614737
The DR deleteboard(8) and moveboard(8)
operations might hang if any of the following
conditions exist:
• A DIMM has been degraded.
• The domain contains system boards with
different memory size.
This has been fixed in patch 137111-01.
[Workaround]
Avoid performing DR operations if any of the
listed conditions exist.
To determine whether the system contains
degraded memory, use the XSCF
showstatus
(8) command. For sample output,
see
“Identifying Degraded Memory in a
To determine whether the domain contains
system boards with different memory sizes,
display the list of memory sizes using the
XSCF showdevices(8) command or the
prtdiag
(8) command on the domain. For
sammple of output, see
Memory Sizes in a System Board” on page 29
If a DR command hangs, reboot the domain to
recover.
6619224
For Solaris domains that include SPARC 64 VII
processors, a single domain of 256 threads (128
cores) or more might hang for an extended
period of time under certain unusual
situations. Upon recovery, the uptime
command will show extremely high load
averages.
This has been fixed in patch 137111-03.
[Workaround]
For Solaris domains that include SPARC 64 VII
processors, do not exceed a domain size of 256
virtual CPUs in a single Solaris domain. This
means a maximum of 32 CPU chips in a single
domain configuration (maximum
configuration for an M8000 server).
6623226
The Solaris command lockstat(1M) or the
dtrace lockstat provider might cause a system
panic.
Do not use the Solaris lockstat(1M)
command or the dtrace lockstat provider.
6625734
Systems with large number of processors in a
single domain environment may have
suboptimal performance with certain
workloads.
Use processor sets to bind application
processes or LWPs to groups of processors.
Refer to the psrset(1M) man page for more
information.
TABLE 4
Solaris OS Issues and Workarounds (Continued)
CR ID
Description
Workaround