Fujitsu SPARC Enterprise T5140, Product Notes

Page: 124 / 138

114 SPARC Enterprise T5140 and T5240 Servers Product Notes • November 2012
Fixed in System Firmware 7.1.3.d or Later
6676561 When Solaris OS is started, BAD TRAP might occur
and the Solaris OS might panic.
Message Example:
panic[cpu12]/thread=300044434c0: BAD
TRAP: type=31 rp=2a101c83320 addr=8
mmu_fsr=0 occurred in module "<unknown>"
due to a NULL pointer dereference
Note - Fixed in System Firmware 7.1.6.d or later.
None.
6596503 The output of the
prtpicl
command used with the
-v
option might show CPU cores or strands with an
OperationalStatus of
enabled
when, in fact, they do
not exist.
Note - Fixed in System Firmware 7.1.6.d or later.
Use the output from the
prtdiag
or
prtpicl -c
cpu commands, which do show the
correct information.
TABLE A-12
Issues Fixed in System Firmware 7.1.3.d or Later
CR ID Description Workaround
6667409 A rounding error caused by frequency calculations in
the Solaris OS leads to short-term discrepancies in
timekeeping. These discrepancies are corrected by
NTP (if enabled) or by the system TOD clock (if
NTP is not enabled). One symptom is an erroneous
value reported by
prtdiag
for CPU frequency
(1162MHz instead of 1167MHz). Another symptom
of these discrepancies is the logging of numerous
time reset
messages by NTP.
Note - Fixed in System Firmware 7.1.3.d or later.
The NTP
time reset
messages can safely be
ignored.
6660496 Fault Management diagnosis of I/O devices and CPU
devices in a Logical Domains environment might not
work correctly.
Fault diagnosis reports can become stalled in a
communications queue. If the fault diagnosis report
stalls, all subsequent diagnosis reports are
undeliverable. Note - Fixed in System Firmware 7.1.3.d or later.
Clear the queue by power cycling the primary control
domain.
6660192 In certain configurations, portions of
prtdiag
output can be incomplete or incorrect. If a XAUI card
does not occupy the first IO slot,
prtdiag
can
report that XAUI is the name of the first network
interface. Further, the location of the LSI controller
might be reported as
MB
instead of
MB/SASHBA.
Note - Fixed in System Firmware 7.1.3.d or later.
6656072 POST failure messages can specify the wrong CPU. Note - Fixed in System Firmware 7.1.3.d or later.
TABLE A-11
Issues Fixed in System Firmware 7.1.6.d or Later (Continued)
CR ID Description Workaround