Fujitsu SPARC Enterprise T5120, Примечания к продукту

Страница: 86 / 150

74 SPARC Enterprise T5120 and T5220 Servers Product Notes • April 2010
L2 Cache Errors Might Generate an Erroneous
Memory Fault (CR 6592272)
This issue is resolved for servers running the Solaris 10 5/08 OS and later. If you are
running Solaris 10 8/07, you can fix this issue with patch ID 127127-11 or later.
In earlier versions, the issue shows up after an uncorrectable L2 writeback error. A
bogus memory fault message (
SUN4V-8000-E2
) might be reported to the console.
Example:
Workaround: Use
fmdump -eV -
u uuid with the UUID from the console message to
determine if the memory error is bogus. For example:
If the
dram-esr
is
0x1000000000008221
, this CR 6592272 has been encountered,
and the memory error can be ignored. No memory component replacement is
necessary. Use
fmadm repair
uuid to repair the bogus memory error.
6616209
6617012 A power supply fan failure might not generate a
fault.
Note - This issue only applies to fan failures in
power supply 0. A fan failure in power supply 1
will generate a fault. Note - Fixed in System Firmware 7.0.9 or later.
To ensure continuous operation during a
possible power supply fan fault, ensure that
both power supplies are connected to two
separate power circuits.
SUNW-MSG-ID: SUN4V-8000-E2, TYPE: Fault, VER: 1, SEVERITY: Critical
EVENT-TIME: Wed Sep 5 18:49:35 EDT 2007
PLATFORM: SUNW,SPARC-Enterprise-T5220, CSN: -, HOSTNAME: wgs48-100
SOURCE: cpumem-diagnosis, REV: 1.6
EVENT-ID: 59bf6418-5dcb-c1b0-b06a-f26fa18e4ee7
DESC: The number of errors associated with this memory module has
exceeded acceptable levels. Refer to http://sun.com/msg/SUN4V-
8000-E2
for more information.
AUTO-RESPONSE: Pages of memory associated with this memory module
are
being removed from service as errors are reported.
IMPACT: Total system memory capacity will be reduced as pages are
retired.
# fmdump -eV -u 59bf6418-5dcb-c1b0-b06a-f26fa18e4ee7 | grep dram-esr
dram-esr = 0x1000000000008221
TABLE A-1
Fixed Hardware and Mechanical Issues (Continued)
CR Description Workaround